Live  /  Runway  /  Incident

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

Runway · runwayml.comMinor incidentResolved2026-06-03 15:02 UTC
Public — what happened

Summary

Runway reported a minor issue affecting generations on its platform beginning at 13:31 UTC on June 3, 2026, saying it had pinpointed the underlying cause and was working to restore service for all users, though it did not say what that cause was. At 14:50 UTC the company said a fix had been deployed, that held-up requests would soon begin going through, and that users could resubmit anything that had failed. Runway marked the incident resolved at 15:02 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.