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

As listed on Runway’s status page.

Timeline

Source of record: provider status page. Summary written by SquidGrid from the provider’s published updates; times in UTC.

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 see
Customers 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.

The full archive is on the Runway status & history page.

Related: Runway status & history. SquidGrid is not affiliated with Runway.