Live / Runway / Incident
Runway: We've identified a problem and are working on a fix
Runway · runwayml.comResolved2026-10-30 19:56 UTC
Public — what happened
Summary
Runway said it had found the root cause of a problem affecting its service for all users, starting at 19:16 UTC on 2026-10-30. About five minutes later it reported releasing a fix, saying delayed requests should begin processing and that submissions which had failed earlier could be tried again. Runway marked the incident resolved at 19:56 UTC after monitoring the fix.
Affected
App, Backend, Public API
Timeline
- Started — 2026-10-30 19:16 UTC
- Investigating — 2026-10-30 19:16 UTC
- Monitoring — 2026-10-30 19:21 UTC
- Resolved — 2026-10-30 19:56 UTC · 40 min 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
Covered in The Squid’s Ink, Week 45, 2026, our weekly internet health report.