Live / Runway / Incident
Runway: We've identified a problem with Veo 3.1 generations and are working on a fix
Runway · runwayml.comMinor incidentResolved2026-05-28 10:32 UTC
Public — what happened
Summary
Runway reported a minor issue on May 28, 2026, in which video generations made with the Veo 3.1 model were not working as expected. The company said its engineers began looking into the problem at 09:53 UTC, and it did not name a cause. At 10:32 UTC, Runway marked the incident resolved, saying it believed the impact had ended.
Affected
App, Backend, Public API
Timeline
- Started — 2026-05-28 09:53 UTC
- Investigating — 2026-05-28 09:53 UTC
- Resolved — 2026-05-28 10:32 UTC · 39 min 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