Is Runway Down?
Real-time status check for runwayml.com
Checking status...
About Runway Status
BlueMonitor checks Runway (runwayml.com) by sending automated requests to its servers. If the service responds within a normal timeframe and returns a successful status code, it's marked as operational. Response times over 3 seconds indicate the service is slow, and connection failures or server errors indicate the service may be down.
Recent Incidents
We've identified a problem and are working on a fix
May 13 , 13:32 UTC Resolved - This incident has now been resolved. May 13 , 12:29 UTC Monitoring - We've released a fix and are seeing improvements. Previously failed submissions can now be retried. We're monitoring closely to ensure the fix fully resolves the issue for everyone. May 13 , 10:24 UTC Identified - We've spotted that something has gone wrong. We're currently working on a fix, and will provide an update soon. May 13 , 09:11 UTC Investigating - Our engineering team is investigating a problem with Kling tasks affecting users. We're aware of the problem and are working towards a solution. We will provide an update soon.
We've identified a problem and are working on a fix
May 13 , 09:06 UTC Resolved - We think the impact from the issue is over. May 13 , 08:19 UTC Update - Our engineering team is investigating a problem with nano banana generations. We're aware of the problem and are working towards a solution. We will provide an update soon. May 13 , 08:11 UTC 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.
Seedance 2 and Kling generations are delayed
May 11 , 15:49 UTC Resolved - We think the impact from the issue is over. May 11 , 11:57 UTC Monitoring - We are working with our third party providers to resolve Kling 3.0 and Seedance 2 long generation times May 11 , 10:08 UTC Update - We've spotted that something has gone wrong. We're currently investigating the issue, and will provide an update soon. May 11 , 09:52 UTC Investigating - We've spotted that something has gone wrong. We're currently investigating the issue, and will provide an update soon.
Issues with Seedance 2.0 generations
Apr 22 , 22:23 UTC Resolved - We've spotted that something has gone wrong. We're currently investigating the issue, and will provide an update soon. Apr 22 , 20:41 UTC Investigating - We're seeing an increased failure rate of Seedance 2.0 generations. We have escalated to the relevant third party and will share an update as soon as we have it.
We have released a fix.
Apr 21 , 20:49 UTC Resolved - We have released a fix, restoring service to Gen4.5. Apr 21 , 20:17 UTC Update - Gen4.5 is experiencing an issue. We are evaluating a solution. Apr 21 , 20:08 UTC 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.
We've identified a problem and are working on a fix
Apr 14 , 04:03 UTC Resolved - This incident has now been resolved. Apr 14 , 03:52 UTC Monitoring - We've released a fix and are seeing improvements. Delayed requests should start processing soon. Previously failed submissions can now be retried. We're monitoring closely to ensure the fix fully resolves the issue for everyone. Apr 14 , 01:21 UTC Investigating - Our engineering team is investigating a problem with assets affecting users. We're aware of the problem and are working towards a solution. We will provide an update soon.
We've identified a problem and are working on a fix
Apr 13 , 17:13 UTC Resolved - This incident has now been resolved. Apr 13 , 15:43 UTC 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.
We've spotted an issue with the Gemini Nano Banana Pro image model
Apr 3 , 17:04 UTC Resolved - This incident has now been resolved. Apr 3 , 15:45 UTC Update - We've spotted that something has gone wrong with the Gemini Nano Banana Pro image model. We're currently investigating the issue, and will provide an update soon. Apr 3 , 15:31 UTC 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.
High queue wait times for Gen 4.5 image-to-video
Mar 17 , 12:42 UTC Resolved - This incident has now been resolved. Mar 17 , 11:11 UTC Monitoring - We've taken action and queue wait times have improved significantly. We're continuing to monitor the situation. Mar 17 , 10:22 UTC 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.
Gen3 Alpha Turbo generations are taking longer than normal
Feb 26 , 19:56 UTC Resolved - This issue has been resolved. Gen3 Alpha Turbo generations queue wait times are normal again. Feb 26 , 19:42 UTC Investigating - Our engineering team is investigating a problem affecting high queue wait times for Gen3 Alpha Turbo generations. We're aware of the problem and are working towards a solution. We will provide an update soon.
Frequently Asked Questions
Is Runway down right now?
This page shows the real-time status of Runway. The status is checked automatically by pinging Runway's servers. If the status shows "Down", it means Runway is currently experiencing issues.
Why is Runway not working?
Runway may not be working due to server outages, scheduled maintenance, network issues, or high traffic. Check the current status above for real-time information.
How do I check if Runway is down for everyone?
BlueMonitor checks Runway's servers from our monitoring infrastructure. If the status shows "Down" here, it's likely down for everyone. If it shows "Up" but you can't access it, the issue may be on your end.
What should I do if Runway is down?
If Runway is down, you can: wait a few minutes and try again, check their official social media for updates, clear your browser cache, or try using a different network connection.