outages.live
Live
RunwayIncident ·

Seedance video generations failing or delayed

DegradedOfficial update
0

Seedance video generations fail or are slow on the App, Backend, and Public API. Runway reports that a fix is in place and monitoring continues. The incident started 35 minutes ago.

State

Monitoring

Started

Ongoing for

2 h 43 min

Worst impact

Degraded

Timeline

3 updates
23:4900:3001:1001:5102:32
DegradedNoticeUpdate postedTimes in UTC

Investigating

35 min 21%

Monitoring

2 h 8 min 79%

Updates

Times in UTC

As posted by Runway

Monitoring

A fix has been implemented and we are monitoring the results.

Investigating

We've spotted that something has gone wrong. We're currently investigating the issue, and will provide an update soon.

Investigating

Our engineering team is investigating a problem affecting users. We're aware of the problem and are working towards a solution. We will provide an update soon.

Affected components

3
AppBackendPublic API

Runway in the last 90 days

Full history
90 days agoToday

Incidents in 90 days

12

Days with an incident

12

Median duration

1 h 24 min

This incident

1.9× the median

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

8 h 7 min
median 1 h 24 min
90 days agoToday

Other Runway incidents

All incidents

Runway·Kling video generations failing or delayed

Kling video generations failed or were delayed on the App and Backend. This affected Kling 4.0, Kling 3.0 and Kling O3 models. Runway resolved the incident after about 8 hours and 7 minutes.

Resolved

Runway·We've identified a problem and are working on a fix

This incident has been resolved.

Resolved

Runway·Magnific upscalers unavailable

This incident has been resolved. Magnific upscaling is working normally again

Resolved

Runway·Scheduled Maintenance

Scheduled maintenance is complete, and all systems are operating normally.

Resolved

Runway·We've identified a problem and are working on a fix

This incident has now been resolved.

Resolved

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.cc/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.cc/feed.xml?providers=runway
Slack
/feed subscribe https://outages.cc/feed.xml?providers=runway

FAQ

Go from tracking outages to fixing production issues with Polylane.

Try Polylane