Live / Runway / Incident
Runway: We've identified a problem and are working on a fix
Runway · runwayml.comCritical outageResolved2026-07-10 17:42 UTC
Public — what happened
Summary
Runway reported a critical incident beginning at 16:42 UTC on July 10, 2026, saying its engineers were looking into an issue that was impacting users, without specifying which features were involved. By 16:48 UTC the company said a fix had been deployed and conditions were getting better, and it kept watching to confirm the problem was gone for all users. Runway marked the incident resolved at 17:42 UTC and did not share a cause.
Affected
App, Backend, Public API
Timeline
- Started — 2026-07-10 16:42 UTC
- Investigating — 2026-07-10 16:42 UTC
- Monitoring — 2026-07-10 16:48 UTC
- Resolved — 2026-07-10 17:42 UTC · 1h 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 Runway 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 Runway: its full incident track record, what tends to break, and recent public reports of problems.
Included with any paid plan.
Open the Runway report →
More from Runway