Runway logo

Is Runway Down?

SaaSLive status, outages, and incident history

No. Runway is up right now.

Every monitored Runway system is operational as of November 9, 2026. PulsAPI did not find an outage in its latest check of the official status feed.

OperationalChecked just nowLive · every 60s

Know the moment Runway breaks

Runway is healthy right now. We keep checking (every 60 seconds) and email you when that changes.

Free, no password, no card. Unsubscribe in one click.

Official Runway status page
How we know: the official Runway status page, PulsAPI's own check (every 60 seconds), and outage reports from engineers. How PulsAPI monitoring works

Status report

Runway Status Summary

As of 20:48 UTC on 9 November 2026, Runway is operational. PulsAPI checked Runway's official status page and found 5 of 5 components operational, with no active incidents. Over the last 30 days PulsAPI measured 99.97% uptime for Runway, counting degraded performance as up. The latest incident, "Seedance video generations failing or delayed", was on Nov 3, 2026 and lasted 5h 6m.

Cite as: PulsAPI, “Runway status”, checked 9 November 2026, 20:48 UTC. https://www.pulsapi.com/services/runway

Runway Component Status

The main Runway systems on this page. All 5 are operational right now.

5operational
App
Operational
Backend
Operational
Billing
Operational

2 more components tracked

Their status is in the bar above. Free accounts see every component by name.

Also tracking Public API, Support.

See all of them free

Component statuses may change independently during partial outages.

Recent Runway Outages & Incidents

Incident history from the official Runway status page, including resolution updates.

Seedance video generations failing or delayedResolved Nov 3, 2026 · 5h 6mResolved

This incident has now been resolved. --- [2026-11-04T00:21:06.057Z] (monitoring) A fix has been implemented and we are monitoring the results. --- [2026-11-03T23:55:26.299Z] (investigating) We've spotted that something has gone wrong. We're currently investigating the issue, and will provide an update soon. --- [2026-11-03T23:49:21.187Z] (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.

Kling video generations failing or delayedResolved Nov 2, 2026 · 8h 6mResolved

This incident has now been resolved. --- [2026-11-02T22:17:33.689Z] (monitoring) We've spotted that something has gone wrong. We're currently investigating the issue, and will provide an update soon. --- [2026-11-02T17:36:30.675Z] (identified) 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. --- [2026-11-02T16:53:06.837Z] (investigating) We're seeing degraded performance for Kling 4.0 and 3.0 tasks.

We've identified a problem and are working on a fixResolved Oct 30, 2026 · 40 minResolved

This incident has been resolved. --- [2026-10-30T19:21:58.909Z] (monitoring) 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. --- [2026-10-30T19:16:02.138Z] (investigating) We have identified the root cause of the problem and are working towards a solution to restore the service for all users.

Runway Uptime History

Daily uptime recorded by PulsAPI over the last 90 days, with the days that carried a Runway incident marked. Each day is measured from our own checks, so the record continues even when the vendor publishes nothing.

Uptime history91 days observed
Aug 11100.00% average · 7 days with incidentsNov 9

Going further back: Runway uptime by month and every recorded Runway outage.

Live Runway Outage Reports

Problems reported by engineers using Runway. Reports often appear 10 to 20 minutes before the official status page moves, and stay on this page for 90 days.

Reports, last 24 hours0 total
24h agoNothing reportednow

No Runway problems reported yet.

Something wrong with Runway on your end?

Reports are anonymous, take about ten seconds, and help the next engineer who checks.

About Runway

Runway publishes a public status page at status.runwayml.com covering 5 components, including App, Backend and Billing. PulsAPI tracks Runway outages, degraded performance and incident history in real time, alongside the rest of your SaaS stack.

Over the past 30 days, PulsAPI has measured Runway uptime at 99.97%. Response times, incident history, and SLA tracking for Runway are available on the PulsAPI dashboard.

Runway Status FAQ

Is Runway down right now?

The verdict at the top of this page comes from the latest poll of the official Runway status feed and refreshes automatically, so you are not looking at a stale cached answer. PulsAPI re-checks it every 60 seconds.

What should I do if Runway is not working?

Check the component list on this page first to see if your failure matches a known outage. If it does, you can report the issue for other engineers, follow the incident timeline for vendor updates, and run any fallback your app supports until Runway recovers.

How do I check Runway uptime history?

PulsAPI tracks Runway uptime over 30, 60, and 90-day rolling windows. The current 30-day uptime is 99.97%. The 90-day uptime strip on this page is public: no account needed. A free account adds alerts whenever Runway changes state, plus 15 days of incident detail; Pro extends that to 90 days and Business to 13 months.

How fast does PulsAPI detect Runway outages?

PulsAPI reads the official Runway status page. PulsAPI re-checks it every 60 seconds. Alerts reach Slack, Discord, Microsoft Teams, PagerDuty, or email once a change has held for 5 minutes, so a one-minute blip does not page you.

Does PulsAPI track individual Runway components?

Yes. PulsAPI monitors 5 individual Runway components, so you can see which service or region is affected instead of a generic "service degraded" banner.

Can I get alerts when Runway goes down?

Yes. Create a free account and subscribe to Runway: the free plan covers three services with unlimited email alerts and no monthly notification cap. Paid plans lift the monitor limit entirely (Pro and above do not meter how many vendors you watch) and route the same alerts into Slack, Discord, Microsoft Teams, PagerDuty and webhooks.

How do I report an issue with Runway to the community?

Click "Report an issue" at the top of this page, pick the issue type and severity, and optionally add your region and a short note. Reports are anonymous and help other engineers spot Runway problems early. Official status pages often lag real incidents by 10 to 20 minutes.

Is there a free way to monitor Runway?

Yes. The free plan covers 3 monitored services with unlimited email alerts, permanently, so Runway plus two more costs nothing. Every new account also opens with a 30-day Business trial (unlimited monitors, Slack alerts, SLA reporting) with no credit card.

Track Runway with the rest of your stack

2660+ vendors in one dashboard, and an email the moment any of them changes state. Three free, and no monitor limit at all from $29/mo, unlike the alternatives, which keep charging by the monitor.

Start free, 3 services