R
Outage recap · RunPod

RunPod outage — October 31, 2026

On October 31, 2026, RunPod had a reported incident on RunPod's official status page. Below is what was reported — impact, timing, and the AI services the same upstream outage could affect.

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

resolved
Started
Oct 31, 4:30 PM EDT
Resolved
Nov 5, 11:22 PM EST
Duration
127h 53m

RunPod's updates (6)

  1. update · Oct 31, 4:30 PM EDT

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

  2. update · Nov 2, 12:34 PM EST

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

  3. update · Nov 2, 10:04 PM EST

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

  4. update · Nov 3, 9:57 PM EST

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

  5. update · Nov 4, 11:06 PM EST

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

  6. resolved · Nov 5, 11:22 PM EST

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

What our checks recorded

We checked RunPod 576 times from RunPod's start time to its resolution, once every five minutes. Every one of them reached RunPod's site, so this incident did not show up as a failed page load. Our check loads the public site; it cannot see an API error or a broken feature. Median response time was 333 ms, against 315 ms over the 24 hours before. RunPod posted the incident at Oct 31, 4:30 PM EDT.

Updates are RunPod's own words from its status page (status: resolved); we never add an inferred cause.

AIDownCheck is not affiliated with RunPod. This recap summarizes incidents published on RunPod's official status page.