Elevated Gemini Omni Flash failures
Runway reports more failures and delays for video generations that use Gemini Omni Flash models. These models are Gemini Omni Flash, Gemini Omni 1.1 Flash and Gemini Omni 1.2 Flash. Runway identified the incident and works with its upstream provider to resolve it.
State
Identified
Started
Ongoing for
4 h 40 min
Worst impact
Notice
Timeline
1 updateIdentified
4 h 40 min 100%
Updates
Times in UTCAs posted by Runway
We're seeing elevated failures and delays for video generations that use Gemini Omni Flash models (Gemini Omni Flash, Gemini Omni 1.1 Flash and Gemini Omni 1.2 Flash). Some generations may fail take longer than usual to complete. We're working with our upstream provider to resolve it. Other video models are not affected.
Affected components
3Runway in the last 90 days
Full historyIncidents in 90 days
11
Days with an incident
12
Median duration
1 h 56 min
This incident
2.4× the median
Other Runway incidents
All incidentsRunway·Elevated Seedance 2.5 generation failures
Seedance 2.5 flash generations have elevated failure rates. The problem affects the App, Backend, and Public API. Runway reports that the incident is resolved. It lasted 47 minutes.
Runway·Seedance video generations failing or delayed
Runway Seedance video generations failed or were delayed. The App, Backend, and Public API were affected. Runway reports that the incident is resolved. It lasted about 5 hours and 6 minutes.
Runway·Kling video generations failing or delayed
Kling video generations failed or took much longer than usual on the App and Backend. Kling 4.0, Kling 3.0, and Kling O3 tasks were affected. Other video models were not affected. Runway reported the issue as resolved. The incident lasted about 8 hours and 7 minutes.
Runway·We've identified a problem and are working on a fix
This incident has been resolved.
Runway·Magnific upscalers unavailable
This incident has been resolved. Magnific upscaling is working normally again
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.
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.
https://outages.live/feed.xml?providers=runway/feed subscribe https://outages.live/feed.xml?providers=runwayFAQ
Go from tracking outages to fixing production issues with Polylane.
Try Polylane