Changes / Runway / Issues with Seedance 2.0 generations
Runway: Major incident: Issues with Seedance 2.0 generations
Summary
Runway reported a major incident affecting Seedance 2.0 generations across App, Backend, and Public API, with increased generation failures. It started at 2026-04-22 20:41 UTC and was marked resolved at 2026-04-22 22:23 UTC, lasting 1 h 41 min. Runway escalated to a third party; no cause or fix was stated.
Machine-written from the diff below (Sol; type: incident outage). Check the diff before relying on it.
What changed
Before: not present
After: Issues with Seedance 2.0 generations
Before: not present
After: major
Before: not present
After: resolved
Before: not present
After: 2026-04-22 20:41 UTC
Before: not present
After: 2026-04-22 22:23 UTC
Before: not present
After: App, Backend, Public API
Before: not present
After: We're seeing an increased failure rate of Seedance 2.0 generations. We have escalated to the relevant third party and will share an update as soon as we have it.
Before: not present
After: We've spotted that something has gone wrong. We're currently investigating the issue, and will provide an update soon.
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: Issues with Seedance 2.0 generations (this change) Runway reported a major incident affecting Seedance 2.0 generations across App, Backend, and Public API, with increased generation failures. It started at 2026-04-22 20:41 UTC and was marked resolved at 2026-04-22 22:23 UTC, lasting 1 h 41 min. Runway escalated to a third party; no cause or fix was stated. | Major incident |