CA-MTL-1 and EU-SE-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.
State
Downtime
Started
1 d ago
2026-10-31 20:30 UTC
Ongoing for
27 h 35 min
Worst impact
Major outage
Timeline
1 updateDowntime
27 h 35 min 100%
Updates
Times in UTCAs posted by RunPod
We are experiencing an issue in CA-MTL-1 and EU-SE-1. We are working to resolve it.
Affected components
2RunPod in the last 90 days
Full historyIncidents in 90 days
1
Days with an incident
3
Median duration
Not enough data
This incident
Not comparable
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.
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.
https://outages.cc/feed.xml?providers=runpod/feed subscribe https://outages.cc/feed.xml?providers=runpodFAQ
Go from tracking outages to fixing production issues with Polylane.
Try Polylane