Scheduled Maintenance
OutageScheduled maintenance is complete, and all systems are operating normally.
Runway is up and running. Runway generates and edits video with AI models.
Worked out from the incidents Runway reported, so it is an estimate and not a measurement.
Last incident: “Scheduled Maintenance”, 6 days ago.
Scheduled maintenance is complete, and all systems are operating normally.
This incident has now been resolved.
We've spotted that something has gone wrong. We're currently investigating the issue, and will provide an update soon.
This incident has now been resolved.
Aleph generations are no longer delayed.
Runway’s official status page says: All Systems Operational. This page checks it again when you load it, at most every 5 minutes.
The most recent incident Runway reported was “Scheduled Maintenance”, 6 days ago (2026-10-17 18:55 UTC). Its last full outage started 6 days ago.
Runway reports 5 components on its status page, including App, Backend, Billing, Support, Public API. Each is checked again whenever this page refreshes.
Retry with exponential backoff, fall back to another model or provider if your product allows it, and avoid hammering the API while it recovers.
Runway lists App, Backend and Public API as separate components — the API row can degrade while the web app stays usable.
Wait for the Backend row to go green first; jobs queued during an incident generally resume rather than being lost, and resubmitting just adds duplicates.
If the status above is operational but Runway still fails for you, the cause is probably on your side: try another network, clear the cache, or check your own connection. If it shows a degradation or an outage, others are affected too.
OpenUptime checks your site every minute and sends an alert to Slack, Telegram, email or a webhook the moment it stops responding. It is open source and free to start.