Runway Outage History
Recent incidents Runway has published, newest first, with how long each one lasted.
Showing 40 published incidents back to 21 Jan 2026.
- Minor3 Nov 20265h 6m
Seedance video generations failing or delayed
- Minor2 Nov 20268h 7m
Kling video generations failing or delayed
- Informational30 Oct 202640 min
We've identified a problem and are working on a fix
- Minor24 Oct 20264h 14m
Magnific upscalers unavailable
- Critical17 Oct 20262h 24m
Scheduled Maintenance
- Major9 Oct 202627 min
We've identified a problem and are working on a fix
- Informational6 Oct 20261h 30m
Elevated Seedance moderation errors
- Minor29 Sep 20262h 21m
We've identified a problem and are working on a fix
- Minor28 Aug 20261h 24m
Aleph delayed generations
- Minor19 Aug 20261h
Gen4.5 Image to Video is Degraded
- Minor19 Aug 20261h 7m
Increased ratio of Seedance safety system false positives
- Minor13 Aug 202613 min
We've identified a problem and are working on a fix
- Critical10 Jul 20261h
We've identified a problem and are working on a fix
- Informational8 Jul 202623 min
Aleph 2.0 delayed generations
- Minor5 Jun 20264h
We've identified a problem with Nano Banana generations and are working on a fix
- Minor3 Jun 20261h 31m
We've identified a problem with generations and are working on a fix
- Major3 Jun 202619 min
Issues with Seedance and Seedream generations
- Minor1 Jun 202621 min
We've identified an issue with Veo 3.1 generations and are working on fixing it
- Minor28 May 202639 min
We've identified a problem with Veo 3.1 generations and are working on a fix
- Minor27 May 202633 min
We've identified a problem with Seedance and working on a fix
- Minor25 May 202630 min
Issues with GPT Image 2 image generation
- Minor25 May 20262h 48m
We are aware of issues affecting video generation with Veo 3.1
- Major13 May 20264h 21m
We've identified a problem and are working on a fix
- Minor13 May 202655 min
We've identified a problem and are working on a fix
- Informational11 May 20265h 57m
Seedance 2 and Kling generations are delayed
- Major22 Apr 20261h 42m
Issues with Seedance 2.0 generations
- Major21 Apr 202641 min
We have released a fix.
- Minor14 Apr 20262h 43m
We've identified a problem and are working on a fix
- Minor13 Apr 20261h 30m
We've identified a problem and are working on a fix
- Minor3 Apr 20261h 33m
We've spotted an issue with the Gemini Nano Banana Pro image model
- Minor17 Mar 20262h 20m
High queue wait times for Gen 4.5 image-to-video
- Minor26 Feb 202614 min
Gen3 Alpha Turbo generations are taking longer than normal
- Minor25 Feb 202642 min
We've identified a problem and are working on a fix
- Major25 Feb 202633 min
We've identified a problem and are working on a fix
- Minor18 Feb 20265h 5m
Issues with Gemini 3 Pro (Nano Banana Pro) generations
- Critical16 Feb 202647 min
Tasks cannot be created
- Major10 Feb 20262h 20m
Issues with Nano Banana Pro generations
- Major9 Feb 20262h 17m
Issues with Nano Banana Pro generations
- Major28 Jan 202653 min
Increased error rate in Veo 3 and Veo 3,.1 generations
- Major21 Jan 20262h 33m
Issues with Gemini 3 Pro image generations
What this record shows
Runway reports separately on the app, the backend that runs generations, billing and the public API, so an entry below usually names one of those rather than describing a total outage.
As with any generative video tool, this list will not capture the complaint users have most often. A generation stuck in the queue is capacity doing its job, not a fault, and it is never recorded as downtime.
Billing entries are worth reading separately from the rest. Credit problems do not resolve when an outage clears, because nothing was broken in the first place.
How to read the durations
Each entry runs from when Video AI opened the incident to when it was marked resolved. That is a generous measure: an incident is usually opened once the problem is confirmed and closed after it has been stable for a while, so the window is wider than the period in which most people were actually affected.
Severity comes from the provider. Only major and critical entries count against the uptime figure on the Runway status page, because a minor incident normally means degraded performance for some users rather than the service being unavailable.
This list is limited to what the provider has published and still exposes. Providers cap how far their public feed reaches, so an empty stretch further back means the record has aged out, not that nothing happened.
🔗 Keep checking