Live  /  Runway  /  Incident

Runway: We've identified a problem and are working on a fix

Runway · runwayml.comMajor incidentResolved2026-05-13 13:32 UTC
Public — what happened

Summary

Runway reported a major problem with Kling tasks that was affecting users, beginning at 09:11 UTC on May 13, 2026. By 10:24 UTC the company said it had found that something was wrong and was working on a fix, though it did not describe a specific cause. A fix was rolled out at 12:29 UTC, after which Runway said earlier failed submissions could be tried again, and it marked the incident resolved at 13:32 UTC.

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

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

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