Runway

Affected: App, Backend, Billing, Support, Public API

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. identified 2026-10-17 18:55 UTC

   Scheduled maintenance is in progress and affects all users. We’ll provide an update once it’s complete.

2. monitoring 2026-10-17 19:14 UTC

   Scheduled maintenance is complete. We’re monitoring system performance to ensure everything is running smoothly.

3. resolved 2026-10-17 21:18 UTC

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

Excerpts are shortened. Read the full incident on Runway's status page.

Affected: App, Backend, Public API

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-10-09 22:44 UTC

   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.

2. resolved 2026-10-09 23:10 UTC

   This incident has now been resolved.

Excerpts are shortened. Read the full incident on Runway's status page.

Affected: App, Backend, Public API

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. monitoring 2026-10-06 18:52 UTC

   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.

2. monitoring 2026-10-06 18:55 UTC

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

3. monitoring 2026-10-06 18:58 UTC

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

4. resolved 2026-10-06 20:22 UTC

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

Excerpts are shortened. Read the full incident on Runway's status page.

Affected: App, Backend, Public API

Failure mode: AI model returned degraded, wrong or empty output (not errors or timeouts). Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-09-29 19:59 UTC

   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.

2. investigating 2026-09-29 20:16 UTC

   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.

3. resolved 2026-09-29 22:20 UTC

   This incident has now been resolved.

Excerpts are shortened. Read the full incident on Runway's status page.

Affected: App, Backend, Public API

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-08-28 16:07 UTC

   We are investigating delayed start to Aleph generations

2. monitoring 2026-08-28 17:19 UTC

   We are rolling out a fix for delayed Aleph generations

3. resolved 2026-08-28 17:31 UTC

   Aleph generations are no longer delayed.

Excerpts are shortened. Read the full incident on Runway's status page.

Affected: App, Backend, Public API

Failure mode: AI model returned degraded, wrong or empty output (not errors or timeouts). Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. monitoring 2026-08-19 17:43 UTC

   We've released a fix and expect tasks to begin running again soon.

2. resolved 2026-08-19 18:44 UTC

   We have resolved the issue.

Excerpts are shortened. Read the full incident on Runway's status page.

Affected: App, Backend, Public API

Failure mode: AI model returned degraded, wrong or empty output (not errors or timeouts). Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-08-19 16:57 UTC

   We're experiencing an issue with Seedance generations that may lead to an increased number of rejected generations. The team is actively investigating this issue.

2. resolved 2026-08-19 18:04 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Runway's status page.

Affected: App, Backend, Public API

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-08-13 03:26 UTC

   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.

2. resolved 2026-08-13 03:39 UTC

   This incident has now been resolved.

Excerpts are shortened. Read the full incident on Runway's status page.

Affected: App, Backend, Public API

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-07-10 16:42 UTC

   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.

2. monitoring 2026-07-10 16:48 UTC

   We've released a fix and are seeing improvements. We're monitoring closely to ensure the fix fully resolves the issue for everyone.

3. resolved 2026-07-10 17:42 UTC

   This incident has now been resolved.

Excerpts are shortened. Read the full incident on Runway's status page.

Affected: App, Backend, Public API

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-07-08 20:39 UTC

   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.

2. resolved 2026-07-08 21:02 UTC

   This incident has now been resolved.

Excerpts are shortened. Read the full incident on Runway's status page.

Affected: App, Backend, Public API

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-06-05 09:30 UTC

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

2. resolved 2026-06-05 13:30 UTC

   This incident has now been resolved.

Excerpts are shortened. Read the full incident on Runway's status page.

Affected: Backend, Public API

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. monitoring 2026-06-04 19:36 UTC

   We're experiencing elevated GPT Image errors due to a third party. We're monitoring the situation and will provide an update soon.

2. resolved 2026-06-04 19:42 UTC

   We're seeing recovery following a third party fix.

Excerpts are shortened. Read the full incident on Runway's status page.

Affected: Backend

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-06-04 08:28 UTC

   Some Veo 3.1 video generation requests are currently failing. We are investigating. We will provide updates as more information becomes available.

2. resolved 2026-06-04 14:28 UTC

   The issue affecting Veo 3.1 video generation has been resolved. We apologize for any inconvenience.

Excerpts are shortened. Read the full incident on Runway's status page.

Affected: App, Backend, Public API

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-06-03 13:31 UTC

   We have identified the root cause of the problem and are working towards a solution to restore the service for all users.

2. investigating 2026-06-03 13:40 UTC

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

3. monitoring 2026-06-03 14:50 UTC

   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.

4. resolved 2026-06-03 15:02 UTC

   This incident has now been resolved.

Excerpts are shortened. Read the full incident on Runway's status page.

Affected: App, Backend, Public API

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-06-03 08:04 UTC

   We're seeing an increased error rate across Seedance and Seedream models. We're conducting an investigation and will share an update as soon as we can.

2. monitoring 2026-06-03 08:18 UTC

   We're seeing that both Seedance and Seedream tasks are recovering and we continue to monitor.

3. resolved 2026-06-03 08:23 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Runway's status page.

Affected: App, Backend, Public API

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-06-01 21:15 UTC

   We're experiencing elevated failure rates for Veo 3.1 generations. We're working on a fix.

2. resolved 2026-06-01 21:36 UTC

   The issue has been resolved.

Excerpts are shortened. Read the full incident on Runway's status page.

Affected: App, Backend, Public API

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-05-28 09:53 UTC

   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.

2. resolved 2026-05-28 10:32 UTC

   We think the impact from the issue is over.

Excerpts are shortened. Read the full incident on Runway's status page.

Affected: App, Backend, Public API

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-05-27 09:36 UTC

   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.

2. resolved 2026-05-27 10:09 UTC

   We think the impact from the issue is over.

Excerpts are shortened. Read the full incident on Runway's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. resolved 2026-05-26 19:30 UTC

   We identified and resolved an issue impacting Aleph 2.0 generations. The incident lasted for approximately 2 hours.

Excerpts are shortened. Read the full incident on Runway's status page.

Affected: App

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-05-25 12:52 UTC

   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.

2. resolved 2026-05-25 13:22 UTC

   The issue affecting GPT Image 2 generations has been resolved. All image generation requests are now processing normally. We apologize for any inconvenience.

Excerpts are shortened. Read the full incident on Runway's status page.

Affected: App, Backend, Public API

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-05-25 12:17 UTC

   We are experiencing elevated failure rates for Veo 3.1 video generation. We are investigating with our infrastructure provider

2. resolved 2026-05-25 15:05 UTC

   Veo 3.1 error rates have returned to normal levels.

Excerpts are shortened. Read the full incident on Runway's status page.

Affected: App, Backend, Public API

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-05-13 09:11 UTC

   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.

2. identified 2026-05-13 10:24 UTC

   We've spotted that something has gone wrong. We're currently working on a fix, and will provide an update soon.

3. monitoring 2026-05-13 12:29 UTC

   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.

4. resolved 2026-05-13 13:32 UTC

   This incident has now been resolved.

Excerpts are shortened. Read the full incident on Runway's status page.

Affected: App, Backend, Public API

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-05-13 08:11 UTC

   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.

2. investigating 2026-05-13 08:19 UTC

   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.

3. resolved 2026-05-13 09:06 UTC

   We think the impact from the issue is over.

Excerpts are shortened. Read the full incident on Runway's status page.

Affected: App, Public API

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-05-11 09:52 UTC

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

2. investigating 2026-05-11 10:08 UTC

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

3. monitoring 2026-05-11 11:57 UTC

   We are working with our third party providers to resolve Kling 3.0 and Seedance 2 long generation times

4. resolved 2026-05-11 15:49 UTC

   We think the impact from the issue is over.

Excerpts are shortened. Read the full incident on Runway's status page.

Affected: App, Backend, Public API

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-04-22 20:41 UTC

   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.

2. resolved 2026-04-22 22:23 UTC

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

Excerpts are shortened. Read the full incident on Runway's status page.

Affected: App, Backend, Public API

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-04-21 20:08 UTC

   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.

2. investigating 2026-04-21 20:17 UTC

   Gen4.5 is experiencing an issue. We are evaluating a solution.

3. resolved 2026-04-21 20:49 UTC

   We have released a fix, restoring service to Gen4.5.

Excerpts are shortened. Read the full incident on Runway's status page.

Affected: App, Backend, Public API

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-04-14 01:21 UTC

   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.

2. monitoring 2026-04-14 03:52 UTC

   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.

3. resolved 2026-04-14 04:03 UTC

   This incident has now been resolved.

Excerpts are shortened. Read the full incident on Runway's status page.

Affected: App, Backend, Public API

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-04-13 15:43 UTC

   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.

2. resolved 2026-04-13 17:13 UTC

   This incident has now been resolved.

Excerpts are shortened. Read the full incident on Runway's status page.

Affected: App, Backend, Public API

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-04-03 15:31 UTC

   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.

2. investigating 2026-04-03 15:45 UTC

   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.

3. resolved 2026-04-03 17:04 UTC

   This incident has now been resolved.

Excerpts are shortened. Read the full incident on Runway's status page.

Affected: App, Backend, Public API

Failure mode: Exhausted memory, disk, CPU, queues, connection pools or quotas. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-03-17 10:22 UTC

   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.

2. monitoring 2026-03-17 11:11 UTC

   We've taken action and queue wait times have improved significantly. We're continuing to monitor the situation.

3. resolved 2026-03-17 12:42 UTC

   This incident has now been resolved.

Excerpts are shortened. Read the full incident on Runway's status page.

Affected: App, Backend, Public API

Failure mode: Exhausted memory, disk, CPU, queues, connection pools or quotas. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-02-26 19:42 UTC

   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.

2. resolved 2026-02-26 19:56 UTC

   This issue has been resolved. Gen3 Alpha Turbo generations queue wait times are normal again.

Excerpts are shortened. Read the full incident on Runway's status page.

Affected: App, Backend, Public API

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-02-25 20:41 UTC

   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.

2. resolved 2026-02-25 21:22 UTC

   This incident has now been resolved.

Excerpts are shortened. Read the full incident on Runway's status page.

Affected: App, Backend, Public API

Failure mode: Exhausted memory, disk, CPU, queues, connection pools or quotas. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-02-25 19:43 UTC

   We are seeing increased queue wait times and issues submitting generations. We are investigating the problem and working on a solution.

2. monitoring 2026-02-25 20:01 UTC

   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.

3. resolved 2026-02-25 20:16 UTC

   This incident has now been resolved.

Excerpts are shortened. Read the full incident on Runway's status page.

Affected: App, Backend, Public API

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-02-18 14:01 UTC

   We're seeing issues affecting a certain percentage of Gemini 3 Pro Image (Nano Banana Pro) generations. We'll provide an update as soon as possible. In the meantime we recommend retrying Nano Banana Pro generations or trying a different model.

2. resolved 2026-02-18 19:06 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Runway's status page.

Affected: App, Backend, Public API

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-02-16 16:24 UTC

   We have identified the root cause of the problem and are working towards a solution to restore the service for all users.

2. investigating 2026-02-16 16:28 UTC

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

3. investigating 2026-02-16 16:29 UTC

   We are testing a potential fix to the issue.

4. monitoring 2026-02-16 16:53 UTC

   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.

5. monitoring 2026-02-16 16:53 UTC

   We see signals that the fix succeeded and has restored functionality to all services.

6. monitoring 2026-02-16 16:59 UTC

   All systems are fully operational.

7. resolved 2026-02-16 17:11 UTC

   This incident has now been resolved.

Excerpts are shortened. Read the full incident on Runway's status page.

Affected: App, Backend, Public API

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-02-10 13:26 UTC

   We're seeing an increased failure rate of Nano Banana Pro generations. We'll provide an update as soon as the issue is resolved.

2. resolved 2026-02-10 15:46 UTC

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

Excerpts are shortened. Read the full incident on Runway's status page.

Affected: App, Backend, Public API

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-02-09 15:39 UTC

   We're seeing an increased error rate in Nano Banana Pro generations. We will provide an update as soon as the issue is resolved.

2. resolved 2026-02-09 17:57 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Runway's status page.

Affected: Backend

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-02-09 10:52 UTC

   We're seeing an increased error rate of Gemini 3 Pro (Nano Banana Pro) generations. We'll share an update as soon as we have it.

2. resolved 2026-02-09 12:11 UTC

   We are no longer seeing high error rates for this model.

Excerpts are shortened. Read the full incident on Runway's status page.

Affected: App, Backend, Public API

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-01-28 17:33 UTC

   We are seeing highly increased error rates in Veo 3 and Veo 3.1 generations and are working closely with Google to resolve them. We will share an update as soon as we can.

2. resolved 2026-01-28 18:25 UTC

   This incident is now resolved.

Excerpts are shortened. Read the full incident on Runway's status page.

Affected: App, Backend, Public API

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-01-21 15:53 UTC

   We've identified issues with Gemini 3 Pro image generations and are working to resolve them. Will provide an update as soon as we have it.

2. resolved 2026-01-21 18:26 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Runway's status page.

Affected: App, Backend, Public API

Failure mode: Exhausted memory, disk, CPU, queues, connection pools or quotas. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-01-18 10:42 UTC

   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.

2. resolved 2026-01-18 12:30 UTC

   This incident has now been resolved.

Excerpts are shortened. Read the full incident on Runway's status page.

Affected: App, Backend, Public API

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-01-02 06:04 UTC

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

2. identified 2026-01-02 08:14 UTC

   We have identified the root cause of the problem affecting video upscaling and are working towards a solution to restore the service for all users.

3. monitoring 2026-01-02 16:33 UTC

   A fix for the issue is rolling out, users should see successful video upscales shortly.

4. resolved 2026-01-02 16:56 UTC

   This incident has now been resolved.

Excerpts are shortened. Read the full incident on Runway's status page.

Affected: App, Backend, Public API

Failure mode: A code release introduced the failure. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2025-12-23 17:06 UTC

   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.

2. monitoring 2025-12-23 17:10 UTC

   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.

3. resolved 2025-12-23 17:17 UTC

   This incident has now been resolved.

Excerpts are shortened. Read the full incident on Runway's status page.

Affected: App, Backend, Public API

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2025-12-12 10:40 UTC

   We are seeing issues with Aleph generations that may affect API customers. We're working on investigating and resolving this issue ASAP.

2. identified 2025-12-12 12:28 UTC

   We have identified the root cause of the problem and are working towards a solution to restore the service for all users.

3. resolved 2025-12-12 13:18 UTC

   This incident has now been resolved.

Excerpts are shortened. Read the full incident on Runway's status page.

Affected: App, Backend, Public API

Failure mode: Exhausted memory, disk, CPU, queues, connection pools or quotas. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2025-12-05 02:35 UTC

   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.

2. investigating 2025-12-05 02:57 UTC

   We're aware that some users are experiencing significant delays in generations and are actively investigating the issue. We'll provide updates as we learn more.

3. investigating 2025-12-05 03:12 UTC

   We're continuing to investigate the issue. A significant number of generations are currently failing to process.

4. monitoring 2025-12-05 03:27 UTC

   We've identified the root cause of the generation delays and have rolled out a fix. Generations should now be processing normally. We'll continue monitoring to ensure stability.

5. monitoring 2025-12-05 03:45 UTC

   All systems have recovered and are processing normally. Gen4 Turbo is experiencing elevated queue wait times due to backlog, but this should clear soon.

6. resolved 2025-12-05 03:51 UTC

   The issue has been fully resolved and all systems are back to normal operation. We apologize for the disruption.

Excerpts are shortened. Read the full incident on Runway's status page.

Affected: App, Backend, Public API

Failure mode: AI model returned degraded, wrong or empty output (not errors or timeouts). Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2025-11-20 11:20 UTC

   We are seeing issues affecting Veo 3.1 generations where the output is sometimes fully black with no audio. We are investigating this issue and will provide an update as soon as we can.

2. investigating 2025-11-21 10:24 UTC

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

3. resolved 2025-11-21 10:25 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Runway's status page.

Affected: App, Backend, Public API

Failure mode: AI model returned degraded, wrong or empty output (not errors or timeouts). Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2025-11-12 16:20 UTC

   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.

2. monitoring 2025-11-12 17:08 UTC

   Generations are processing normally again. We will continue to monitor the situation.

3. resolved 2025-11-12 19:38 UTC

   The issue has been resolved.

Excerpts are shortened. Read the full incident on Runway's status page.

Affected: App, Backend, Public API

Failure mode: Exhausted memory, disk, CPU, queues, connection pools or quotas. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2025-10-20 21:14 UTC

   We're observing longer than normal queue wait times. 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.

2. identified 2025-10-20 21:35 UTC

   We're starting to see improved queue wait times, especially for Runway Dev API platform generations. We're still working through a large backlog of generations.

3. monitoring 2025-10-20 23:17 UTC

   We've rolled out a fix and are seeing errors and generation throughput normalize. We are working through a backlog of generations so queue wait times are still likely to be elevated for some time. We will post another update when wait times have normalized.

4. resolved 2025-10-20 23:33 UTC

   This incident has now been resolved.

Excerpts are shortened. Read the full incident on Runway's status page.

Affected: App, Backend, Public API

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. investigating 2025-10-20 07:36 UTC

   Runway is experiencing an outage due to 3rd party cloud provider. We are working on a solution and will provide updates as soon as possible.

2. monitoring 2025-10-20 10:12 UTC

   We are seeing significant signs of recovery. We continue to monitor the incident.

3. resolved 2025-10-20 10:17 UTC

   Runway has fully recovered, both image and video generations work properly.

Excerpts are shortened. Read the full incident on Runway's status page.

Affected: Public API

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2025-10-13 15:09 UTC

   We're seeing issues that may cause Runway API generations to fail, we're currently investigating the root cause and will provide an update shortly.

2. resolved 2025-10-13 17:07 UTC

   This incident is resolved now.

Excerpts are shortened. Read the full incident on Runway's status page.