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

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.