Live  /  Runway  /  Incident

Runway: Issues with Seedance 2.0 generations

Runway · runwayml.comMajor incidentResolved2026-04-22 22:23 UTC
Public — what happened

Summary

Runway reported a major incident on April 22, 2026, starting at 20:41 UTC, in which a higher-than-normal share of Seedance 2.0 generations were failing. The company said it had raised the problem with an outside provider involved in the service. Runway marked the incident resolved at 22:23 UTC, though its final update did not explain a cause or describe what was done to fix it.

Affected

App, Backend, Public API

As listed on Runway’s status page.

Timeline

Source of record: provider status page. Summary written by SquidGrid from the provider’s published updates; times in UTC.

Independent path health

The status page is the symptom. SquidGrid measures the paths that reach Runway against their own baselines — whether the routes carrying your traffic degraded, at which handoff, and who owns that stretch.

🔒 Sign in to see
Customers get the live Provider Assessment Report for Runway: its full incident track record, what tends to break, and recent public reports of problems.

Included with any paid plan.

Open the Runway report →

More from Runway

The full archive is on the Runway status & history page.

Related: Runway status & history. SquidGrid is not affiliated with Runway.