Changes / Runway / Issues with Seedance and Seedream generations
Runway: Major incident: Issues with Seedance and Seedream generations
Summary
Runway reported a major incident with increased error rates for Seedance and Seedream generations across App, Backend, and Public API. It started at 2026-06-03 08:04 UTC and was resolved at 2026-06-03 08:23 UTC; the computed duration was 18 min. Tasks were recovering by 08:18 UTC; 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 and Seedream generations
Before: not present
After: major
Before: not present
After: resolved
Before: not present
After: 2026-06-03 08:04 UTC
Before: not present
After: 2026-06-03 08:23 UTC
Before: not present
After: App, Backend, Public API
Before: not present
After: We're seeing an increased error rate across Seedance and Seedream models. We're conducting an investigation and will share an update as soon as we can.
Before: not present
After: We're seeing that both Seedance and Seedream tasks are recovering and we continue to monitor.
Before: not present
After: This incident has been 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: Issues with Seedance and Seedream generations (this change) Runway reported a major incident with increased error rates for Seedance and Seedream generations across App, Backend, and Public API. It started at 2026-06-03 08:04 UTC and was resolved at 2026-06-03 08:23 UTC; the computed duration was 18 min. Tasks were recovering by 08:18 UTC; no cause or fix was stated. | Major incident |