Live  /  Runway  /  Incident

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

Runway · runwayml.comMinor incidentResolved2026-04-14 04:03 UTC
Public — what happened

Summary

Runway said it was looking into an issue with assets that was affecting users, starting at 01:21 UTC on April 14, 2026, and rated it minor. At 03:52 UTC the company reported it had deployed a fix, that queued requests would begin going through, and that users could resubmit anything that had failed earlier. Runway did not describe a cause. It marked the incident resolved at 04:03 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.