Runway: We've identified a problem with Veo 3.1 generations and are working on a fix
Affected components: AppBackendPublic API
Timeline of updates
- investigating
Our engineering team is investigating a problem affecting Veo 3.1 generations. We're aware of the problem and are working towards a solution. We will provide an update soon.
- resolved
We think the impact from the issue is over.
Archive proof
Rewindex commits each version of an incident it captures to a daily checkpoint, chains it to the day before, and has the checkpoint timestamped by FreeTSA and DigiCert. That proves this record existed by then and has not been changed since, by anyone, Rewindex included.
How the archive is checked, and what it cannot prove.
First version captured
In the 2026-10-17 checkpoint, timestamped by FreeTSA and DigiCert on . Record hash
860c3f5dcb60beb2…
Impact, status and times are the vendor’s own, as last archived. View on stspg.io (opens in new tab).
Cite this
Status incident (vendor impact label: minor) posted by Runway, started 2026-05-28 09:53 UTC, resolved after 39 min, 2 update(s).
- Title
- We've identified a problem with Veo 3.1 generations and are working on a fix
- Vendor
- Runway
- Date
- URL
- https://rewindex.com/company/runway/incidents/38q6bh2k75yg
Runway profileRecent Runway incidentsAll outages on May 28, 2026Runway in May 2026MarkdownJSON