Live / Runway / Incident
Runway: We've identified a problem and are working on a fix
Runway · runwayml.comMinor incidentResolved2026-09-29 22:20 UTC
Public — what happened
Summary
Runway reported a minor incident on September 29, 2026, beginning at 19:59 UTC, when its engineers began looking into an issue that was affecting users. About 20 minutes later, the company said the trouble involved Alelph 2 generations, which were running with reduced performance. Runway did not share a cause, and it marked the incident as resolved at 22:20 UTC the same day.
Affected
App, Backend, Public API
Timeline
- Started — 2026-09-29 19:59 UTC
- Investigating — 2026-09-29 19:59 UTC (2 updates)
- Resolved — 2026-09-29 22:20 UTC · 2h 21m 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 41, 2026, our weekly internet health report.