Runway: We've identified an issue with Veo 3.1 generations and are working on fixing it
Affected components: AppBackendPublic API
Timeline of updates
- investigating
We're experiencing elevated failure rates for Veo 3.1 generations. We're working on a fix.
- resolved
The issue has been resolved.
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
a7b2edc5ceac89ea…
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-06-01 21:15 UTC, resolved after 21 min, 2 update(s).
- Title
- We've identified an issue with Veo 3.1 generations and are working on fixing it
- Vendor
- Runway
- Date
- URL
- https://rewindex.com/company/runway/incidents/smzblf6xk4lk
Runway profileRecent Runway incidentsAll outages on June 1, 2026Runway in June 2026MarkdownJSON