Changes / Runway / Increased error rate in Veo 3 and Veo 3,.1 generations
Runway: Major incident: Increased error rate in Veo 3 and Veo 3,.1 generations
Summary
Runway reported a major incident with highly increased error rates in Veo 3 and Veo 3.1 generations, affecting App, Backend, and Public API. It started at 2026-01-28 17:33 UTC and was resolved at 2026-01-28 18:25 UTC, lasting 52 min; Runway said it was working closely with Google but stated no cause or specific fix.
Machine-written from the diff below (Sol; type: incident degradation). Check the diff before relying on it.
What changed
Before: not present
After: Increased error rate in Veo 3 and Veo 3,.1 generations
Before: not present
After: major
Before: not present
After: resolved
Before: not present
After: 2026-01-28 17:33 UTC
Before: not present
After: 2026-01-28 18:25 UTC
Before: not present
After: App, Backend, Public API
Before: not present
After: We are seeing highly increased error rates in Veo 3 and Veo 3.1 generations and are working closely with Google to resolve them. We will share an update as soon as we can.
Before: not present
After: This incident is now resolved.
First version of this incident archived by Rewindex. View the live incident (opens in new tab).
History of this incident
| When (UTC) | Change | Kind |
|---|---|---|
| Major incident: Increased error rate in Veo 3 and Veo 3,.1 generations (this change) Runway reported a major incident with highly increased error rates in Veo 3 and Veo 3.1 generations, affecting App, Backend, and Public API. It started at 2026-01-28 17:33 UTC and was resolved at 2026-01-28 18:25 UTC, lasting 52 min; Runway said it was working closely with Google but stated no cause or specific fix. | Major incident |