R
Outage recap · RunPod

RunPod outage — October 9, 2026

On October 9, 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 - EUR-NO-2

resolved
Started
Oct 9, 12:30 PM EDT
Resolved
Oct 9, 10:00 PM EDT
Duration
9h 30m

RunPod's updates (2)

  1. update · Oct 9, 12:30 PM EDT

    Network Engineers have scheduled emergency maintenance on our upstream network infrastructure. Traffic will automatically reroute during this time, so we do not anticipate any interruptions to your services. Maintenance window: 10/09/2026 16:30 - 10/10/2026 02:00 UTC

  2. update · Oct 9, 10:00 PM EDT

    Maintenance ended

What our checks recorded

We checked RunPod 114 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 114 ms, against 109 ms over the 24 hours before. RunPod posted the incident at Oct 9, 12:30 PM EDT.

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

US-CA-2 Network Storage Issue

resolved
Started
Oct 9, 12:31 PM EDT
Resolved
Oct 9, 2:02 PM EDT
Duration
1h 31m

RunPod's updates (2)

  1. update · Oct 9, 12:31 PM EDT

    We are experiencing Network Storage issue in US-CA-2 DC. We are working to resolve it.

  2. resolved · Oct 9, 2:02 PM EDT

    Network storage issue in US-CA-2 is resolved and operating normally.

What our checks recorded

We checked RunPod 18 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 108 ms, against 109 ms over the 24 hours before. RunPod posted the incident at Oct 9, 12:31 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.