CA-MTL-1 recovered
Timeline · 1 update
- investigating Jun 02, 2026, 10:56 PM UTC
CA-MTL-1 went down
RunPod Outage History
RunPod is up right nowRunPod had 28 outages in the last 2 years totaling 369h 24m of downtime — averaging 1.2 incidents per month.
There were 28 RunPod outages since February 21, 2026 totaling 369h 24m of downtime. Each is summarised below — incident details, duration, and resolution information.
EU-SE-1 recovered
Timeline · 1 update
- investigating Jun 01, 2026, 07:42 AM UTC
EU-SE-1 went down
Upstream authentication pro...
Affected: GPU Cloud (ui: runpod.io/console)
Timeline · 1 update
- investigating May 26, 2026, 09:57 PM UTC
We are investigating an upstream services issue that is affecting user signup and account switching.
Upstream issue - Elevated i...
Affected: GPU Cloud (Upstream Systems)
Timeline · 3 updates
Runpod.io website is unavai...
Affected: GPU Cloud (Upstream Systems)
Timeline · 1 update
- 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.
EU-FR-1 went down
Timeline · 1 update
- investigating May 15, 2026, 02:22 PM UTC
EU-FR-1 went down
CA-MTL-3 Network Issue
Affected: Regional Health (CA-MTL-3)
Timeline · 2 updates
- investigating May 14, 2026, 08:24 PM UTC
We are experiencing network connectivity issues in CA-MTL-3. We are working to resolve it.
- resolved May 14, 2026, 09:49 PM UTC
Network issue is resolved and operating normally.
Upstream Systems recovered
Timeline · 1 update
- investigating May 08, 2026, 07:28 PM UTC
Upstream Systems went down
Console: Delayed Pod starts...
Affected: GPU Cloud (log/metrics api: hapi.runpod.net)GPU Cloud (ui: runpod.io/console)
Timeline · 2 updates
- 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.
- 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.
US-CA-2 recovered
Timeline · 1 update
- investigating May 08, 2026, 01:23 AM UTC
US-CA-2 went down
CA-MTL-3 recovered
Timeline · 1 update
- investigating Apr 28, 2026, 04:55 AM UTC
CA-MTL-3 went down
CA-MTL-1 and CA-MTL-3 Netwo...
Affected: Regional Health (CA-MTL-1)Regional Health (CA-MTL-3)
Timeline · 3 updates
- 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.
- 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.
- resolved Apr 28, 2026, 08:12 AM UTC
Network connectivity to CA-MTL-1 DC has been restored.
CA-MTL-4 recovered
Timeline · 1 update
- resolved Apr 21, 2026, 05:03 PM UTC
CA-MTL-4 recovered
EUR-IS-2 recovered
Timeline · 1 update
- resolved Apr 07, 2026, 11:22 AM UTC
EUR-IS-2 recovered
Incident Notice: Power Serv...
Affected: Regional Health (US-NC-1)
Timeline · 1 update
- 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.
EU-FR-1 recovered
Timeline · 1 update
- resolved Mar 31, 2026, 02:41 AM UTC
EU-FR-1 recovered
EU-FR-1 Network Issue
Affected: Regional Health (EU-FR-1)
Timeline · 2 updates
- investigating Mar 31, 2026, 01:11 AM UTC
We are experiencing network connectivity issues in EU-FR-1. We are working to resolve it.
- resolved Mar 31, 2026, 08:39 AM UTC
Issue has been resolved and the network in EU-FR-1 DC is operating normally.
US-NC-1 Network Issue
Affected: Regional Health (US-NC-1)
Timeline · 2 updates
- investigating Mar 25, 2026, 04:18 AM UTC
We are experiencing network connectivity issues in US-NC-1. We are working to resolve it.
- resolved Mar 25, 2026, 04:48 AM UTC
Issue has been resolved and the network in US-NC-1 DC is operating normally.
US-NE-1 internet network sp...
Affected: Regional Health (US-NE-1)
Timeline · 2 updates
- investigating Mar 17, 2026, 04:23 PM UTC
US-NE-1 DC is experiencing slower internet connectivity. We are working on resolving this issue.
- resolved Mar 18, 2026, 11:55 AM UTC
Issue with internet network speeds in US-NE-1 DC has been resolved and is now operating normally.
CA-MTL-1 Connectivity issue...
Affected: Regional Health (CA-MTL-1)
Timeline · 3 updates
- investigating Mar 16, 2026, 09:43 PM UTC
There are network connectivity issues in CA-MTL-1 DC. We are working to resolve the issue.
- resolved Mar 17, 2026, 01:45 AM UTC
Network connectivity has been restored and is operating normally.
- resolved Mar 17, 2026, 01:45 AM UTC
Network connectivity has been restored and is operating normally.
Issue with creating new sto...
Affected: Serverless (serverless api: api.runpod.ai)GPU Cloud (ui: runpod.io/console)
Timeline · 2 updates
- investigating Mar 14, 2026, 01:36 AM UTC
We are experiencing an issue with creating new storage volumes in EU-RO-1 DC. Existing storage volumes continue to operate as normal. We are working on resolving this issue.
- resolved Mar 14, 2026, 02:21 AM UTC
The issue has been resolved. New network volume creations for EU-RO-1 DC is now operating normally.
EUR-NO-1 - Network storage ...
Affected: Regional Health (EUR-NO-1)
Timeline · 2 updates
- investigating Mar 11, 2026, 03:45 PM UTC
EUR-NO-1's network storage array performance is degraded. We're working on restoring performance.
- resolved Mar 11, 2026, 07:15 PM UTC
Network storage performance has been resolved and is operating normally.
US-CA-2 Network Storage con...
Affected: Regional Health (US-CA-2)
Timeline · 2 updates
- investigating Mar 10, 2026, 10:40 PM UTC
There are network connectivity issues using the network storage volumes in US-CA-2 DC.
- resolved Mar 10, 2026, 11:24 PM UTC
Connectivity to the network storage volumes in US-CA-2 has been resolved.
Console Login Issues
Affected: GPU Cloud (ui: runpod.io/console)
Timeline · 1 update
- investigating Mar 10, 2026, 04:21 PM UTC
We are currently monitoring issues with an upstream authentication provider that may cause console logins to be slow or fail for some users. Our team is investigating and working with the provider to resolve the issue.
US-CA-2 networking is degraded
Affected: Regional Health (US-CA-2)
Timeline · 2 updates
- investigating Mar 07, 2026, 08:08 AM UTC
US-CA-2 networking is degraded which is impacting ability to connect to pods within the datacenter. Runpod engineering is investigating in coordination with on-site staff.
- investigating Mar 07, 2026, 11:06 AM UTC
All telemetry is returning nominal levels and the ISP is preparing a post mortem report.