Live

Elevated Seedance 2.5 generation failures

0

Seedance 2.5 generation failures are elevated on the App, Backend, and Public API. Runway reports that the incident is in monitoring and that it is working with its model provider. The incident started 15 minutes ago.

State

Monitoring

Started

Ongoing for

20 min

Worst impact

Degraded

Timeline

1 update
16:2716:3216:3716:4216:47
DegradedUpdate postedTimes in UTC

Monitoring

20 min 100%

Updates

Times in UTC

As posted by Runway

Monitoring

We are seeing elevated failure rates for Seedance 2.5 flash generations and are working with our model provider to resolve this issue.

Affected components

3
AppBackendPublic API

Runway in the last 90 days

Full history
90 days agoToday

Incidents in 90 days

10

Days with an incident

11

Median duration

2 h 21 min

This incident

86% shorter than the median

How long each incident lasted, on the day it started. The outlined bar is this incident.

8 h 7 min
median 2 h 21 min
90 days agoToday

Other Runway incidents

All incidents

Follow Runway

Your coding agent knows when Runway is down, and tells you when a failure is theirs, not yours. You can also get Runway incidents in a feed reader or in Slack.

Prompt
Install the outages.live MCP server, so that when something breaks you can tell if the cause is a provider we depend on and not my code. It reads the official status pages of cloud, AI, payment and developer providers and gives you their incidents as MCP tools.

Add it as a remote MCP server named "outages" at https://outages.live/mcp (Streamable HTTP, no authentication), with your CLI command or your MCP config file.

Then:
1. Make sure it connects and shows the tools get_provider, list_feed and send_feedback.
2. Call get_provider with "runway" and tell me if Runway has a problem right now.
3. From now on, when a call to a third-party service fails or becomes slow, call get_provider for that service before you change my code.

Paste this into any coding agent. It adds the server with its own MCP setup.

RSS
https://outages.live/feed.xml?providers=runway
Slack
/feed subscribe https://outages.live/feed.xml?providers=runway

FAQ

Go from tracking outages to fixing production issues with Polylane.

Try Polylane