Live  /  Runway  /  Incident

Runway: We've identified a problem and are working on a fix

Runway · runwayml.comMinor incidentResolved2026-05-13 09:06 UTC
Public — what happened

Summary

Runway reported a minor incident beginning at 08:11 UTC on 2026-05-13, initially describing only an unspecified issue impacting users. By 08:19 UTC the company had narrowed it down to trouble with nano banana generations, while its engineers kept looking into it. Runway did not share a cause, and at 09:06 UTC it marked the incident resolved, saying it believed the effects had ended.

Affected

App, Backend, Public API

As listed on Runway’s status page.

Timeline

Source of record: provider status page. Summary written by SquidGrid from the provider’s published updates; times in UTC.

Independent path health

The status page is the symptom. SquidGrid measures the paths that reach Runway against their own baselines — whether the routes carrying your traffic degraded, at which handoff, and who owns that stretch.

🔒 Sign in to see
Customers get the live Provider Assessment Report for Runway: its full incident track record, what tends to break, and recent public reports of problems.

Included with any paid plan.

Open the Runway report →

More from Runway

The full archive is on the Runway status & history page.

Related: Runway status & history. SquidGrid is not affiliated with Runway.