Outage recap · Runway

Runway outage — November 2, 2026

On November 2, 2026, Runway had a reported incident on Runway's official status page. Below is what was reported — impact, timing, and the AI services the same upstream outage could affect.

Kling video generations failing or delayed

minor
Started
Nov 2, 11:53 AM EST
Resolved
Nov 2, 7:59 PM EST
Duration
8h 7m

Runway's updates (4)

  1. investigating · Nov 2, 11:53 AM EST

    We're seeing degraded performance for Kling 4.0 and 3.0 tasks.

  2. identified · Nov 2, 12:36 PM EST

    Since about 15:00 UTC, most video generations with Kling models are failing or taking much longer than usual. This affects Kling 4.0, Kling 3.0 (Standard, Pro, Turbo, 4K and Motion Control) and Kling O3 (Standard, Pro and 4K). Other video models are not affected. The cause is an issue with our upstream provider. We're working with them on a fix. Some generations have started completing again, but we don't expect normal performance yet. Until then, we recommend using a different video model. Generations that are still pending may complete late or fail.

  3. monitoring · Nov 2, 5:17 PM EST

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

  4. resolved · Nov 2, 7:59 PM EST

    This incident has now been resolved.

What our checks recorded

We checked Runway 97 times from Runway's start time to its resolution, once every five minutes. Every one of them reached Runway's site, so this incident did not show up as a failed page load. Our check loads the public site; it cannot see an API error or a broken feature. Median response time was 732 ms, against 788 ms over the 24 hours before. Runway posted the incident at Nov 2, 11:53 AM EST.

Updates are Runway's own words from its status page (status: resolved); we never add an inferred cause. The vendor's incident page ↗

AIDownCheck is not affiliated with Runway. This recap summarizes incidents published on Runway's official status page.