outages.live
Live
R

RunPod

RunPod is reporting major outage

Checked 2 min ago Major outage

CA-MTL-1 DC is Unavailable

RunPod reports that CA-MTL-1 and EU-SE-1 are unavailable. RunPod is working to resolve the issue. The outage started on 31 October 2026 and continues.

Major outageupdated 23 h ago

History

90 days agoToday

Incidents in 90 days

1

Days with an incident

2

Median duration

No data

Longest incident

No data

Components

42

Serverless

serverless api: api.runpod.ai Operational
90 days agoNo incidentsToday
serverless: queue engine Operational
90 days agoNo incidentsToday
Serverless: CPU workers Operational
90 days agoNo incidentsToday

GPU Cloud

graphql: api.runpod.io Operational
90 days agoNo incidentsToday
log/metrics api: hapi.runpod.net Operational
90 days agoNo incidentsToday
pod proxy: proxy.runpod.net Operational
90 days agoNo incidentsToday
graphql: transactional data store Operational
90 days agoNo incidentsToday
ui: runpod.io/console Operational
90 days agoNo incidentsToday
Upstream Systems Operational
90 days agoNo incidentsToday
CPU Cloud Operational
90 days agoNo incidentsToday

Regional Health

AP-IN-1 Operational
90 days agoNo incidentsToday
AP-JP-1 Operational
90 days agoNo incidentsToday
CA-MTL-1 Major outage
90 days ago2 days with an incidentToday
CA-MTL-3 Operational
90 days agoNo incidentsToday
CA-MTL-4 Unknown
90 days agoNo incidentsToday
EU-CZ-1 Unknown
90 days agoNo incidentsToday
EU-FR-1 Operational
90 days agoNo incidentsToday
EU-NL-1 Operational
90 days agoNo incidentsToday
EU-RO-1 Operational
90 days agoNo incidentsToday
EU-SE-1 Major outage
90 days ago2 days with an incidentToday
EUR-IS-1 Operational
90 days agoNo incidentsToday
EUR-IS-2 Unknown
90 days agoNo incidentsToday
EUR-IS-3 Operational
90 days agoNo incidentsToday
EUR-IS-4 Operational
90 days agoNo incidentsToday

Past incidents

Provider status pageTimes in UTC

No incident in the last 90 days.

Maintenance

Planned Power Maintenance EUR-IS-3 & EUR-IS-4

Planned Power Maintenance for EUR-IS-3 and EUR-IS-4 Maintenance Time The maintenance will take place on Thursday, November 5, 2026 Iceland Time (GMT/UTC): 06:00 – 17:40 To ensure the long-term safety, thermal stability, and electrical protection of customer GPU nodes, the data center building owner and the power company will perform critical preventative infrastructure maintenance on November 5, 2026. Customers should back up and save all active jobs beforehand so they can seamlessly resume work once services are systematically restored. Scope: Full-site power outage. All EUR-IS-3 and EUR-IS-4 devices will be shut down and taken offline during the maintenance window.

Maintenancestarts in 3 d

Affected components

8
  • CA-MTL-1Regional HealthMajor outage
  • CA-MTL-4Regional HealthUnknown
  • EU-CZ-1Regional HealthUnknown
  • EU-SE-1Regional HealthMajor outage
  • EUR-IS-2Regional HealthUnknown
  • US-IL-1Regional HealthUnknown
  • US-TX-1Regional HealthUnknown
  • US-TX-3Regional HealthUnknown

Follow RunPod

Your coding agent knows when RunPod is down, and tells you when a failure is theirs, not yours. You can also get RunPod 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 "runpod" and tell me if RunPod 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=runpod
Slack
/feed subscribe https://outages.cc/feed.xml?providers=runpod

Go from tracking outages to fixing production issues with Polylane.

Try Polylane