R
Outage recap · RunPod

RunPod outage — November 6, 2026

On November 6, 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.

Planned Server relocation

resolved
Started
Nov 6, 6:00 AM EST
Resolved
Nov 6, 6:00 PM EST
Duration
12h

RunPod's updates (3)

  1. update · Nov 6, 6:00 AM EST

    Maintenance Time : Friday, November 6, 2026. Central Time (CST, UTC−6): 05:00 – 09:00 UTC: 11:00 – 15:00 Scope: As part of our data center expansion, US-IL-1 will undergo a four-hour planned maintenance window to safely relocate machines to a new data-hall on the campus. Please back up your active jobs before the downtime begins so you can resume operations seamlessly once power is restored.

  2. update · Nov 6, 10:00 AM EST

    Maintenance ended

  3. update · Nov 6, 6:00 PM EST

    Maintenance ended

What our checks recorded

We checked RunPod 144 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 319 ms, against 321 ms over the 24 hours before. RunPod posted the incident at Nov 6, 6:00 AM EST.

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

US-IL-1 Server Relocation

resolved
Started
Nov 6, 6:01 PM EST
Resolved
Nov 7, 10:01 AM EST
Duration
16h

RunPod's updates (2)

  1. update · Nov 6, 6:01 PM EST

    Our datacenter partner has informed us that server relocation is taking the team longer than expected. We expect to have service fully restored by 7AM/CST on 11/7/2026

  2. update · Nov 7, 10:01 AM EST

    Maintenance ended

What our checks recorded

We checked RunPod 192 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 266 ms, against 321 ms over the 24 hours before. RunPod posted the incident at Nov 6, 6:01 PM EST.

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.