R
Outage recap · RunPod

RunPod outage — September 24, 2026

On September 24, 2026, RunPod had 2 reported incidents on RunPod's official status page. Below is what was reported — impact, timing, and the AI services the same upstream outage could affect.

Emergency Network Maintenance for CA-MTL-4

resolved
Started
Sep 24, 12:00 PM EDT
Resolved
Sep 24, 4:00 PM EDT
Duration
4h

RunPod's updates (2)

  1. update · Sep 24, 12:00 PM EDT

    Our datacenter provider has notified us of an emergency network maintenance in the CA-MTL-4 facility. This maintenance is intended to enhance the performance and reliability of our internet services. We do not expect any service impact, and this notice is for informational purposes only. While every precaution is being taken to avoid interruptions, there may be brief periods of packet loss during the maintenance window. Maintenance Window Start: Thursday, September 24th at 12:00 PM EDT End: Thursday, September 24th at 04:00 PM EDT

  2. update · Sep 24, 4:00 PM EDT

    Maintenance ended

What our checks recorded

We checked RunPod 48 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 86 ms, against 94 ms over the 24 hours before. RunPod posted the incident at Sep 24, 12:00 PM EDT.

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

EU-SE-1 Network Issue

resolved
Started
Sep 24, 5:12 PM EDT
Resolved
Sep 24, 5:45 PM EDT
Duration
33 min

RunPod's updates (2)

  1. update · Sep 24, 5:12 PM EDT

    We are experiencing network connectivity issues in EU-SE-1. We are working to resolve it.

  2. resolved · Sep 24, 5:45 PM EDT

    Issue has been resolved and the network in EU-SE-1 DC is operating normally.

What our checks recorded

We checked RunPod 6 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 54 ms, against 95 ms over the 24 hours before. RunPod posted the incident at Sep 24, 5:12 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.