Live / Runway / Incident
Runway: Elevated Seedance moderation errors
Runway · runwayml.comResolved2026-10-06 20:22 UTC
Public — what happened
Summary
Runway said that on 2026-10-06 at 18:52 UTC it noticed a higher-than-usual number of failed Seedance generations when the input contained human faces, an issue it labeled as moderation errors. The company said it was working with the Seedance team to figure out what was happening, and its later updates only repeated that it was still looking into it. No cause was given, and Runway marked the incident resolved at 20:22 UTC the same day.
Affected
App, Backend, Public API
Timeline
- Started — 2026-10-06 18:52 UTC
- Monitoring — 2026-10-06 18:52 UTC (3 updates)
- Resolved — 2026-10-06 20:22 UTC · 1h 30m after it started
With SquidGrid — where it starts on the route
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 seeCustomers 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
Covered in The Squid’s Ink, Week 42, 2026, our weekly internet health report.