Runway: We've identified a problem with Seedance and working on a fix
Affected components: AppBackendPublic API
Timeline of updates
- investigating
Our engineering team is investigating a problem affecting Seedance generations. We're aware of the problem and are working towards a solution. We will provide an update soon.
- resolved
We think the impact from the issue is over.
Archive proof
Rewindex commits each version of an incident it captures to a daily checkpoint, chains it to the day before, and has the checkpoint timestamped by FreeTSA and DigiCert. That proves this record existed by then and has not been changed since, by anyone, Rewindex included.
How the archive is checked, and what it cannot prove.
First version captured
In the 2026-10-17 checkpoint, timestamped by FreeTSA and DigiCert on . Record hash
a13138e831bf1f9e…
Impact, status and times are the vendor’s own, as last archived. View on stspg.io (opens in new tab).
Cite this
Status incident (vendor impact label: minor) posted by Runway, started 2026-05-27 09:36 UTC, resolved after 33 min, 2 update(s).
- Title
- We've identified a problem with Seedance and working on a fix
- Vendor
- Runway
- Date
- URL
- https://rewindex.com/company/runway/incidents/5flxznwwnj93
Runway profileRecent Runway incidentsAll outages on May 27, 2026Runway in May 2026MarkdownJSON