Frame.io experienced a notice incident on January 27, 2026 affecting next.frame.io (V4) and app.frame.io (LEGACY), lasting 3h 31m. The incident has been resolved; the full update timeline is below.
Affected components
Update timeline
- investigating Jan 27, 2026, 03:36 PM UTC
We are currently investigating this issue.
- investigating Jan 27, 2026, 03:49 PM UTC
We are continuing to investigate this issue.
- investigating Jan 27, 2026, 03:56 PM UTC
We are continuing to investigate this issue.
- investigating Jan 27, 2026, 04:07 PM UTC
We are continuing to investigate this issue.
- investigating Jan 27, 2026, 04:18 PM UTC
We are continuing to investigate this issue.
- investigating Jan 27, 2026, 04:30 PM UTC
We are continuing to investigate this issue.
- investigating Jan 27, 2026, 04:41 PM UTC
We are continuing to investigate this issue.
- investigating Jan 27, 2026, 04:57 PM UTC
We are continuing to investigate this issue
- investigating Jan 27, 2026, 05:13 PM UTC
We are continuing to investigate this issue.
- investigating Jan 27, 2026, 05:39 PM UTC
We are continuing to investigate this issue.
- investigating Jan 27, 2026, 05:55 PM UTC
We are continuing to investigate this issue.
- investigating Jan 27, 2026, 06:25 PM UTC
We are continuing to investigate this issue. We have observed a reduction in the frequency of occurrences.
- investigating Jan 27, 2026, 06:40 PM UTC
We're no longer seeing occurrences. Monitoring continues while we investigate the root cause.
- investigating Jan 27, 2026, 07:07 PM UTC
No further occurrences observed. We're closing the incident and will continue to monitor, investigate the root cause, and evaluate whether additional remediation is needed. For questions, please reach out to our support team through chat or email [email protected].
- resolved Jan 27, 2026, 07:08 PM UTC
This incident has been resolved.