Looking for an update now? Check the current status, or follow Runway for future changes.
94.7%of 57 verified observed days had no reported provider issue
90-Day Trend
Dashed calendar markers below identify legacy observations whose source-at-observation was not recorded.
Monthly Status Summary
Month
Issue-free days
Days Tracked
Days with issues
September 2026
100%
30
0
This percentage summarizes normalized provider-status observations by calendar day. It is not duration-based, component-weighted, or contractual uptime. See the methodology and limitations.
Recorded Daily Status (Last 91 Days)
Jul 23Today
Legacy observation Operational Degraded Partial Outage Major Outage Maintenance No Data
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 that something has gone wrong. We're currently investigating the issue, and will provide an update soon.
monitoring
We've spotted that something has gone wrong. We're currently investigating the issue, and will provide an update soon.
monitoring
We have detected elevated failures for Seedance generations with inputs that include human faces. We are working with the Seedance team to diagnose the issue.
September 2026
We've identified a problem and are working on a fix
We've spotted that something has gone wrong with Alelph 2 generations, causing degraded performance. 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.
We are rolling out a fix for delayed Aleph generations
investigating
We are investigating delayed start to Aleph generations
Legacy Incident Archive
25 archived records restored. These records predate source-at-observation attestation. They are shown as historical ServiceAlert records only and do not establish a provider-reported incident, resolution, duration, or current active state.
June 2026
We've identified an issue with Veo 3.1 generations and are working on fixing it
minorSource not attested
Last archived state: resolved
View archived record details
investigating
We're experiencing elevated failure rates for Veo 3.1 generations. We're working on a fix.
May 2026
We've identified a problem with Veo 3.1 generations and are working on a fix
minorSource not attested
Last archived state: resolved
View archived record details
investigating
Our engineering team is investigating a problem affecting Veo 3.1 generations. We're aware of the problem and are working towards a solution. We will provide an update soon.
We've identified a problem with Seedance and working on a fix
minorSource not attested
Last archived state: resolved
View archived record details
investigating
Our engineering team is investigating a problem affecting Seedance generations. 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
majorSource not attested
Last archived state: resolved
View archived record details
investigating
Our engineering team is investigating a problem with Aleph 2 affecting users. We are working towards a solution. We will provide an update soon.
Issues with GPT Image 2 image generation
minorSource not attested
Last archived state: resolved
View archived record details
investigating
We are aware of issues affecting image generation with GPT Image 2. Users may experience failures when generating images. We are working to resolve this.
We are aware of issues affecting video generation with Veo 3.1
minorSource not attested
Last archived state: resolved
View archived record details
investigating
We are experiencing elevated failure rates for Veo 3.1 video generation. We are investigating with our infrastructure provider
We've identified a problem and are working on a fix
majorSource not attested
Last archived state: resolved
View archived record details
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.
identified
We've spotted that something has gone wrong. We're currently working on a fix, and will provide an update soon.
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
minorSource not attested
Last archived state: resolved
View archived record details
investigating
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.
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
majorSource not attested
Last archived state: resolved
View archived record details
monitoring
We are working with our third party providers to resolve Kling 3.0 and Seedance 2 long generation times
investigating
We've spotted that something has gone wrong. We're currently investigating the issue, and will provide an update soon.
investigating
We've spotted that something has gone wrong. We're currently investigating the issue, and will provide an update soon.
April 2026
Issues with Seedance 2.0 generations
majorSource not attested
Last archived state: resolved
View archived record details
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.
