Live / Runway / Incident
Runway: Kling video generations failing or delayed
Runway · runwayml.comMinor incidentResolved2026-11-03 00:59 UTC
Public — what happened
Summary
Runway said video creation with its Kling models was failing or running much slower than normal, starting around 15:00 UTC on 2026-11-02, with the first status post at 16:53 UTC. The company said this covered several Kling 4.0, 3.0 and O3 versions, while its other video models were not affected. Runway said the cause was a problem with an upstream provider, that it was working with them on a fix, and it suggested people use a different video model in the meantime. It reported the incident resolved at 00:59 UTC on 2026-11-03.
Affected
App, Backend, Public API
Timeline
- Started — 2026-11-02 16:53 UTC
- Investigating — 2026-11-02 16:53 UTC
- Identified — 2026-11-02 17:36 UTC
- Monitoring — 2026-11-02 22:17 UTC
- Resolved — 2026-11-03 00:59 UTC · 8h 07m 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 46, 2026, our weekly internet health report.