Resolved after 1 hour 45 minutes, affecting next.frame.io (V4) and app.frame.io (LEGACY) and 1 more, on June 25, 2025.
The issue appears to have been fixed. We're actively monitoring the situation.
Affected components
next.frame.io (V4)app.frame.io (LEGACY)Developer PlatformMedia Processing
Update timeline
- investigating Jun 25, 2025, 08:41 PM UTC
User settings are currently inaccessible. Our team is working to identify the root cause and implement a fix.
- investigating Jun 25, 2025, 09:09 PM UTC
We haven't clearly identified the root cause of the issue and are continuing to investigate it.
- identified Jun 25, 2025, 09:40 PM UTC
We have found the root cause of the issue and have implemented a fix.
- monitoring Jun 25, 2025, 09:47 PM UTC
The issue appears to have been fixed. We're actively monitoring the situation.
- resolved Jun 25, 2025, 10:26 PM UTC
This incident has been resolved.
Your product runs on more than Frame.io
Add the vendors you depend on and get one message when any of them reports trouble. Free for 3 vendors, no card.
Amazon Web Services