Live  /  Runway  /  Incident

Runway: Issues with Seedance and Seedream generations

Runway · runwayml.comMajor incidentResolved2026-06-03 08:23 UTC
Public — what happened

Summary

Runway said that generations using its Seedance and Seedream models were failing more often than usual starting at 08:04 UTC on June 3, 2026, and it rated the problem as major. The company began looking into the errors right away but did not say what caused them. By 08:18 UTC, Runway reported that tasks on both models were coming back to normal, and it marked the incident resolved at 08:23 UTC.

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.