Skip to main content
RunPod

CA-MTL-1 and EU-SE-1 DC is Unavailable

Degraded Lasted 5d 7h · started · RunPod's page

Level
confirmed
Worst impact
Degraded
Components
EU-SE-1, CA-MTL-1
Regions
eu
Down Index
37of 100

Summary

RunPod says its CA-MTL-1 and EU-SE-1 data centers were unavailable starting October 31, 2026. It says EU-SE-1 was resolved and operating normally on November 3, and CA-MTL-1 was resolved and operating normally on November 6. The incident is marked resolved.

Written by anthropic/claude-haiku-5.5 from RunPod's own updates.

What to do

  • Check whether you use RunPod EU-SE-1, CA-MTL-1 in eu. Check your stack

    Paste a package.json, lockfile, Terraform or a list of domains at down.guide/stack to see every provider you depend on.
  • Confirm your retries, queues and scheduled jobs caught up after the 5d 7h it lasted.

    Anything that failed between 2026-10-31 20:30 UTC and 2026-11-06 04:22 UTC may need a replay.
  • Subscribe to RunPod's feed to hear about the next one first. RSS feed

    https://down.guide/feed?provider=runpod works in Slack (/feed subscribe), Discord feed bots and any RSS reader.

Updates from RunPod 6

  1. downtime

    We are experiencing an issue in CA-MTL-1 and EU-SE-1. We are working to resolve it.

    provider

  2. downtime

    We are continuing to work on resolving the issue in CA-MTL-1 and EU-SE-1 DCs.

    provider

  3. resolved

    Issue has been resolved in EU-SE-1 DC and it is operating normally. We are continuing to work on CA-MTL-1 DC.

    provider

  4. resolved

    We are continuing to work on resolving the issue in CA-MTL-1 DC.

    provider

  5. resolved

    We are continuing to work on resolving the remaining machines in CA-MTL-1 DC.

    provider

  6. resolved

    Issue has been resolved and CA-MTL-1 DC is operating normally.

    provider

Reports count in aggregate; nothing about you is shown.

Corrections

None so far.

Something wrong on this page? Report an error or send us a note. Every fix is listed here.

Questions about DWN-c5712eeb6f

Is RunPod still down?

No, this incident was resolved 2026-11-06 04:22 UTC. For RunPod's live state, see https://down.guide/runpod.

How long did it last?

5d 7h, from 2026-10-31 20:30 UTC to 2026-11-06 04:22 UTC, by the times RunPod posted.

What was affected?

RunPod named EU-SE-1, CA-MTL-1 in eu.

What caused it?

RunPod hasn't published a root cause. If it does, it shows here.

Where does this come from?

RunPod's official status page, https://uptime.runpod.io, quoted verbatim. down.guide's own probes, reports and social counts are labeled as ours.