Live / Frame.io / Incident
Frame.io: Intermittent log in issues
Frame.io · frame.ioMajor incidentResolved2026-10-01 23:57 UTC
Public — what happened
Summary
Frame.io reported a major incident on October 1, 2026, in which some users ran into intermittent problems signing in, beginning at 21:51 UTC. By 22:41 UTC the company said it had found the source of the trouble, though it did not describe what it was, and it had a fix in place by 22:48 UTC. After a period of observation, Frame.io marked the incident resolved at 23:57 UTC.
Timeline
- Started — 2026-10-01 21:51 UTC
- Investigating — 2026-10-01 21:51 UTC
- Identified — 2026-10-01 22:41 UTC
- Monitoring — 2026-10-01 22:48 UTC
- Resolved — 2026-10-01 23:57 UTC · 2h 06m after it started
With SquidGrid — where it starts on the route
Independent path health
The status page is the symptom. SquidGrid measures the paths that reach Frame.io against their own baselines — whether the routes carrying your traffic degraded, at which handoff, and who owns that stretch.
🔒 Sign in to seeCustomers get the live Provider Assessment Report for Frame.io: its full incident track record, what tends to break, and recent public reports of problems.
Included with any paid plan.
Open the Frame.io report →
More from Frame.io
Covered in The Squid’s Ink, Week 41, 2026, our weekly internet health report.