Runway reported "Magnific upscalers unavailable" on its status page at 2026-10-24 09:15 UTC.

Runway lists these components: App, Backend, Public API.

When did the incident start and end?

It started at 2026-10-24 09:15 UTC and ended at 2026-10-24 13:29 UTC. It lasted 4 h 14 min.

How do I get alerts for Runway?

Subscribe to the Runway live feed over RSS or in Slack, or add the outages.live MCP server to your coding agent.

Where does this information come from?

From the official status page of Runway. outages.live reads it every few minutes and keeps every update.

RunwayIncident · 2026-10-24 09:15 UTC

Magnific upscalers unavailable

ResolvedOfficial update

This incident has been resolved. Magnific upscaling is working normally again

The latest update from Runway.

State

Resolved

Started

9 d ago

2026-10-24 09:15 UTC

Lasted

4 h 14 min

until 2026-10-24 13:29 UTC

Worst impact

Degraded

Timeline

3 updates

09:1510:1811:2212:2513:29

DegradedUpdate postedTimes in UTC

Investigating

3 h 6 min 73%

Monitoring

1 h 8 min 27%

Updates

Times in UTC

As posted by Runway

Resolved2026-10-24 13:29 UTC

This incident has been resolved. Magnific upscaling is working normally again

Monitoring2026-10-24 12:21 UTC

We've applied a fix and Magnific upscaling is working again. We're monitoring to make sure everything stays stable

Investigating2026-10-24 09:15 UTC

Magnific upscaling is currently failing. We've identified the cause and are working with our provider to restore service

Affected components

AppBackendPublic API

Runway in the last 90 days

Full history

90 days agoToday

Incidents in 90 days

Days with an incident

Median duration

1 h 15 min

This incident

3.4× the median

How long each incident lasted, on the day it started. The outlined bar is this incident.

4 h 14 min

median 1 h 15 min

90 days agoToday

Other Runway incidents

All incidents

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

This incident has been resolved.

Resolvedresolved 2 d ago

Runway·Scheduled Maintenance

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

Resolvedresolved 15 d ago

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

This incident has now been resolved.

Resolvedresolved 23 d ago

Runway·Elevated Seedance moderation errors

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

Resolvedresolved 26 d ago

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

This incident has now been resolved.

Resolvedresolved 33 d ago

Follow Runway

Your coding agent knows when Runway is down, and tells you when a failure is theirs, not yours. You can also get Runway incidents in a feed reader or in Slack.

Prompt

Install the outages.live MCP server, so that when something breaks you can tell if the cause is a provider we depend on and not my code. It reads the official status pages of cloud, AI, payment and developer providers and gives you their incidents as MCP tools.

Add it as a remote MCP server named "outages" at https://outages.cc/mcp (Streamable HTTP, no authentication), with your CLI command or your MCP config file.

Then:
1. Make sure it connects and shows the tools get_provider, list_feed and send_feedback.
2. Call get_provider with "runway" and tell me if Runway has a problem right now.
3. From now on, when a call to a third-party service fails or becomes slow, call get_provider for that service before you change my code.

Paste this into any coding agent. It adds the server with its own MCP setup.

RSS

https://outages.cc/feed.xml?providers=runway

Slack

/feed subscribe https://outages.cc/feed.xml?providers=runway

FAQ

Go from tracking outages to fixing production issues with Polylane.

Try Polylane