R
Outage recap · RunPod

RunPod outage — October 24, 2026

On October 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.

EUR-IS-3 Network Issue

resolved
Started
Oct 24, 1:51 PM EDT
Resolved
Oct 24, 2:18 PM EDT
Duration
27 min

RunPod's updates (4)

  1. update · Oct 24, 1:51 PM EDT

    We are experiencing network connectivity issues in EUR-IS-3. We are working to resolve it.

  2. resolved · Oct 24, 2:18 PM EDT

    Issue has been resolved and the network in EUR-IS-3 DC is operating normally.

  3. update · Oct 24, 4:20 PM EDT

    We are experiencing network connectivity issues in EUR-IS-3. We are working to resolve it.

  4. resolved · Oct 24, 7:05 PM EDT

    Issue has been resolved and the network in EUR-IS-3 DC is operating normally.

What our checks recorded

We checked RunPod 5 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 176 ms, against 109 ms over the 24 hours before. RunPod posted the incident at Oct 24, 1:51 PM EDT.

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

Planned Network & UFM Maintenance AP-IN region

resolved
Started
Oct 24, 2:30 PM EDT
Resolved
Oct 24, 5:30 PM EDT
Duration
3h

RunPod's updates (2)

  1. update · Oct 24, 2:30 PM EDT

    Please be advised that scheduled network maintenance will take place during the following window. This maintenance involves two separate, independent activities grouped together to minimize the overall number of maintenance events. Maintenance Window PDT: October 24, 2026 | 11:30 AM – 2:30 PM IST: October 25, 2026 | 12:00 AM – 3:00 AM Scope: All machines in AP-IN region Planned Activities & Expected Impact 1. DC Internet Traffic Optimization Impact: Users may experience minor network fluctuations, jitter, or latency for approximately 15 minutes during the maintenance window. 2. Enable SHARP on UFM Impact: Running GPU jobs may be impacted or interrupted for up to 120 minutes during this activity. Unaffected Services: H100 accessibility and standard Ethernet/CPU workloads will remain fully operational and unaffected. User Action Required GPU Workloads: Please be aware that active GPU jobs may be interrupted during this maintenance window. In the event of a GPU workload failure or interruption, the affected job will need to be re-initiated by the respective user once the activity is complete. General Network: No action is required for the Internet Traffic Optimization, but please plan accordingly for the brief period of expected network latency.

  2. update · Oct 24, 5:30 PM EDT

    Maintenance ended

What our checks recorded

We checked RunPod 36 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 103 ms, against 109 ms over the 24 hours before. RunPod posted the incident at Oct 24, 2: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.