R
Outage recap · RunPod

RunPod outage — September 29, 2026

On September 29, 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 Network Maintenance EUR-NO-2

resolved
Started
Sep 29, 10:00 AM EDT
Resolved
Sep 29, 1:00 PM EDT
Duration
3h

RunPod's updates (2)

  1. update · Sep 29, 10:00 AM EDT

    Planned Network Maintenance EUR-NO-2 Core Router Upgrade: When: September 29th 2026, from 14:00–17:00 UTC. Please be advised that scheduled network maintenance will take place at the EUR-NO-2 Datacenter. We will be migrating the core routing infrastructure to new routers. The migration will be completed in phases, with redundancy maintained throughout. Expected Impact: Customers may experience brief upstream connectivity interruptions during individual cut-over phases. No impact is expected outside of these short windows.

  2. update · Sep 29, 1:00 PM EDT

    Maintenance ended

What our checks recorded

We checked RunPod 35 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 91 ms, against 114 ms over the 24 hours before. RunPod posted the incident at Sep 29, 10:00 AM EDT.

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

EUR-NO-2 Network Storage Issue

resolved
Started
Sep 29, 1:00 PM EDT
Resolved
Sep 29, 4:30 PM EDT
Duration
3h 30m

RunPod's updates (2)

  1. update · Sep 29, 1:00 PM EDT

    We are experiencing Network Storage issue in EUR-NO-2 DC. We are working to resolve it.

  2. resolved · Sep 29, 4:30 PM EDT

    Network storage issue in EUR-NO-2 is resolved and operating normally.

What our checks recorded

We checked RunPod 42 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 124 ms, against 109 ms over the 24 hours before. RunPod posted the incident at Sep 29, 1:00 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.