RunPod Outage History

RunPod is up right now

RunPod had 38 outages in the last 2 years totaling 366h 16m of downtime — averaging 1.6 incidents per month.

There were 38 RunPod outages since February 21, 2026 totaling 366h 16m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://uptime.runpod.io

Minor July 21, 2026

EUR-IS-1 Network Issue

Detected by Pingoru
Jul 21, 2026, 10:35 PM UTC
Resolved
Jul 21, 2026, 11:45 PM UTC
Duration
1h 10m
Affected: Regional Health (EUR-IS-1)
Timeline · 2 updates
  1. investigating Jul 21, 2026, 10:35 PM UTC

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

  2. resolved Jul 21, 2026, 11:45 PM UTC

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

Read the full incident report →

Minor July 10, 2026

EUR-IS-4 Network Issue

Detected by Pingoru
Jul 10, 2026, 08:24 PM UTC
Resolved
Jul 10, 2026, 09:02 PM UTC
Duration
38m
Affected: Regional Health (EUR-IS-4)
Timeline · 2 updates
  1. investigating Jul 10, 2026, 08:24 PM UTC

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

  2. resolved Jul 10, 2026, 09:02 PM UTC

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

Read the full incident report →

Minor July 10, 2026

EUR-IS-1 Networking is Degr...

Detected by Pingoru
Jul 10, 2026, 10:00 AM UTC
Resolved
Jul 10, 2026, 07:00 PM UTC
Duration
9h
Affected: Regional Health (EUR-IS-1)
Timeline · 3 updates
  1. investigating Jul 10, 2026, 10:00 AM UTC

    Network performance is degraded in EUR-IS-1. We are working on resolving the issue.

  2. investigating Jul 10, 2026, 06:24 PM UTC

    Network performance is degraded in EUR-IS-1. We are working on resolving the issue.

  3. resolved Jul 10, 2026, 07:00 PM UTC

    Issue has been resolved and is operating normally.

Read the full incident report →

Minor July 9, 2026

US-TX-3 Network Storage Issue

Detected by Pingoru
Jul 09, 2026, 06:24 AM UTC
Resolved
Jul 09, 2026, 04:50 PM UTC
Duration
10h 26m
Affected: Regional Health (US-TX-3)
Timeline · 3 updates
  1. investigating Jul 09, 2026, 06:24 AM UTC

    We are experiencing Network Storage issue in US-TX-3 DC. We are working to resolve it.

  2. investigating Jul 09, 2026, 12:33 PM UTC

    We are experiencing Network Storage issue in US-TX-3 DC. We are working to resolve it.

  3. resolved Jul 09, 2026, 04:50 PM UTC

    Issue has been resolved and is operating normally.

Read the full incident report →

Minor July 8, 2026

US-GA-2 Networking is Degraded

Detected by Pingoru
Jul 08, 2026, 08:16 PM UTC
Resolved
Jul 08, 2026, 10:12 PM UTC
Duration
1h 56m
Affected: Regional Health (US-GA-2)
Timeline · 2 updates
  1. investigating Jul 08, 2026, 08:16 PM UTC

    Network performance is degraded in US-GA-2. We are working on resolving the issue.

  2. resolved Jul 08, 2026, 10:12 PM UTC

    Issue has been resolved and is operating normally.

Read the full incident report →

Minor July 8, 2026

EUR-NO-1 Network Storage Issue

Detected by Pingoru
Jul 08, 2026, 09:52 AM UTC
Resolved
Jul 08, 2026, 10:27 AM UTC
Duration
35m
Affected: Regional Health (EUR-NO-1)
Timeline · 2 updates
  1. investigating Jul 08, 2026, 09:52 AM UTC

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

  2. resolved Jul 08, 2026, 10:27 AM UTC

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

Read the full incident report →

Minor July 7, 2026

CA-MTL-3 Network Storage Issue

Detected by Pingoru
Jul 07, 2026, 09:20 PM UTC
Resolved
Jul 08, 2026, 09:56 AM UTC
Duration
12h 36m
Affected: Regional Health (CA-MTL-3)
Timeline · 2 updates
  1. investigating Jul 07, 2026, 09:20 PM UTC

    We are experiencing Network Storage issue in CA-MTL-3 DC. We are working to resolve it.

  2. resolved Jul 08, 2026, 09:56 AM UTC

    Network storage issue in CA-MTL-3 is resolved and operating normally.

Read the full incident report →

Minor June 26, 2026

US-PA-1 Network Inbound Issue

Detected by Pingoru
Jun 26, 2026, 02:00 PM UTC
Resolved
Jun 26, 2026, 02:00 PM UTC
Duration
Affected: Regional Health (US-GA-2)Regional Health (US-PA-1)
Timeline · 1 update
  1. investigating Jun 26, 2026, 02:00 PM UTC

    Some machines' public IPs and ports are unreachable in US-PA-1, and we're also seeing network interruptions causing the servers to lose connectivity. We are checking with the ISP, and our network engineers are working on getting a full root cause and resolution.

Read the full incident report →

Minor May 26, 2026

Upstream authentication pro...

Detected by Pingoru
May 26, 2026, 09:57 PM UTC
Resolved
May 26, 2026, 09:57 PM UTC
Duration
Affected: GPU Cloud (ui: runpod.io/console)
Timeline · 1 update
  1. investigating May 26, 2026, 09:57 PM UTC

    We are investigating an upstream services issue that is affecting user signup and account switching.

Read the full incident report →

Minor May 22, 2026

Runpod.io website is unavai...

Detected by Pingoru
May 22, 2026, 05:40 PM UTC
Resolved
May 22, 2026, 05:40 PM UTC
Duration
Affected: GPU Cloud (Upstream Systems)
Timeline · 1 update
  1. investigating May 22, 2026, 05:40 PM UTC

    Runpod.io website is experiencing issues but the console and services are operating normally and not impacted. We are actively working with upstream provider to address this issue.

Read the full incident report →

Minor May 14, 2026

CA-MTL-3 Network Issue

Detected by Pingoru
May 14, 2026, 08:24 PM UTC
Resolved
May 14, 2026, 09:49 PM UTC
Duration
1h 25m
Affected: Regional Health (CA-MTL-3)
Timeline · 2 updates
  1. investigating May 14, 2026, 08:24 PM UTC

    We are experiencing network connectivity issues in CA-MTL-3. We are working to resolve it.

  2. resolved May 14, 2026, 09:49 PM UTC

    Network issue is resolved and operating normally.

Read the full incident report →

Minor May 8, 2026

Console: Delayed Pod starts...

Detected by Pingoru
May 08, 2026, 05:08 PM UTC
Resolved
May 08, 2026, 09:49 PM UTC
Duration
4h 41m
Affected: GPU Cloud (log/metrics api: hapi.runpod.net)GPU Cloud (ui: runpod.io/console)
Timeline · 2 updates
  1. investigating May 08, 2026, 05:08 PM UTC

    We are experiencing increased times for Pods to start along with console logs not being displayed. We are investigating the issue and will provide an update once we have more information.

  2. resolved May 08, 2026, 09:49 PM UTC

    The issue has been resolved. Functionality for pod starts and display for logs on the console have returned to normal.

Read the full incident report →

Minor April 28, 2026

CA-MTL-1 and CA-MTL-3 Netwo...

Detected by Pingoru
Apr 28, 2026, 04:52 AM UTC
Resolved
Apr 28, 2026, 08:12 AM UTC
Duration
3h 20m
Affected: Regional Health (CA-MTL-1)Regional Health (CA-MTL-3)
Timeline · 3 updates
  1. investigating Apr 28, 2026, 04:52 AM UTC

    We are experiencing network connectivity issues in CA-MTL-1 and CA-MTL-3. We are working to resolve it.

  2. investigating Apr 28, 2026, 04:52 AM UTC

    We are experiencing network connectivity issues in CA-MTL-1 and CA-MTL-3. We are working to resolve it.

  3. resolved Apr 28, 2026, 08:12 AM UTC

    Network connectivity to CA-MTL-1 DC has been restored.

Read the full incident report →

Minor April 4, 2026

Incident Notice: Power Serv...

Detected by Pingoru
Apr 04, 2026, 05:58 PM UTC
Resolved
Apr 04, 2026, 05:58 PM UTC
Duration
Affected: Regional Health (US-NC-1)
Timeline · 1 update
  1. resolved Apr 04, 2026, 05:58 PM UTC

    Update: At 1:45 PM PT, Power was restored to the site and machines had been started to be powered back on. The datacenter is back on full utility power with UPS backup. Datacenter engineers are continuing to look into why the generator supplied power at a voltage outside of expected range for the UPS which caused the UPS to not switch over. Original issue: Our datacenter US-NC-1 has reported a power failure at the US-NC-1 facility that occurred at approximately 8:00 AM PT on April 4th. This failure has taken down the entire A-side power. The servers currently failing are not N+N Redundant; they are N+1. Typically, in a power outage, UPS and Generators act as backup, however, this failover is not working. Onsite teams are working on providing a Root Cause Analysis (RCA) to find out why the backup power was unable to kick on to run these servers. Updates will be shared as our datacenter partners provide estimated repair times and as more information becomes available.

Read the full incident report →