- Detected by Pingoru
- Apr 29, 2026, 10:45 PM UTC
- Resolved
- Apr 29, 2026, 10:45 PM UTC
- Duration
- —
Timeline · 1 update
-
investigating Apr 29, 2026, 09:44 PM UTC
US-CA-2 went down
Read the full incident report →
- Detected by Pingoru
- Apr 28, 2026, 09:26 AM UTC
- Resolved
- Apr 28, 2026, 09:26 AM UTC
- Duration
- —
Timeline · 1 update
-
investigating Apr 28, 2026, 04:51 AM UTC
CA-MTL-1 went down
Read the full incident report →
- Detected by Pingoru
- Apr 28, 2026, 05:55 AM UTC
- Resolved
- Apr 28, 2026, 05:55 AM UTC
- Duration
- —
Timeline · 1 update
-
investigating Apr 28, 2026, 04:55 AM UTC
CA-MTL-3 went down
Read the full incident report →
- 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
-
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.
Read the full incident report →
- Detected by Pingoru
- Apr 21, 2026, 05:03 PM UTC
- Resolved
- Apr 21, 2026, 05:03 PM UTC
- Duration
- —
Timeline · 1 update
-
resolved Apr 21, 2026, 05:03 PM UTC
CA-MTL-4 recovered
Read the full incident report →
- Detected by Pingoru
- Apr 14, 2026, 08:09 PM UTC
- Resolved
- Apr 14, 2026, 08:41 PM UTC
- Duration
- 32m
Affected: GPU Cloud (Upstream Systems)
Timeline · 2 updates
-
investigating Apr 14, 2026, 08:09 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.
-
resolved Apr 14, 2026, 08:41 PM UTC
Issue with runpod.io website has been resolved. We are continuing to monitor for issues.
Read the full incident report →
- Detected by Pingoru
- Apr 07, 2026, 11:22 AM UTC
- Resolved
- Apr 07, 2026, 11:22 AM UTC
- Duration
- —
Timeline · 1 update
-
resolved Apr 07, 2026, 11:22 AM UTC
EUR-IS-2 recovered
Read the full incident report →
- 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
-
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 →
- Detected by Pingoru
- Mar 31, 2026, 03:47 PM UTC
- Resolved
- Mar 31, 2026, 03:47 PM UTC
- Duration
- —
Timeline · 1 update
-
resolved Mar 31, 2026, 03:47 PM UTC
Upstream Systems recovered
Read the full incident report →
- Detected by Pingoru
- Mar 31, 2026, 02:41 AM UTC
- Resolved
- Mar 31, 2026, 02:41 AM UTC
- Duration
- —
Timeline · 1 update
-
resolved Mar 31, 2026, 02:41 AM UTC
EU-FR-1 recovered
Read the full incident report →
- Detected by Pingoru
- Mar 31, 2026, 01:11 AM UTC
- Resolved
- Mar 31, 2026, 08:39 AM UTC
- Duration
- 7h 28m
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.
Read the full incident report →
- Detected by Pingoru
- Mar 25, 2026, 04:18 AM UTC
- Resolved
- Mar 25, 2026, 04:48 AM UTC
- Duration
- 30m
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.
Read the full incident report →
- Detected by Pingoru
- Mar 17, 2026, 04:23 PM UTC
- Resolved
- Mar 18, 2026, 11:55 AM UTC
- Duration
- 19h 32m
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.
Read the full incident report →
- Detected by Pingoru
- Mar 16, 2026, 09:43 PM UTC
- Resolved
- Mar 17, 2026, 01:45 AM UTC
- Duration
- 4h 2m
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.
Read the full incident report →
- Detected by Pingoru
- Mar 14, 2026, 01:36 AM UTC
- Resolved
- Mar 14, 2026, 02:21 AM UTC
- Duration
- 45m
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.
Read the full incident report →
- Detected by Pingoru
- Mar 11, 2026, 03:45 PM UTC
- Resolved
- Mar 11, 2026, 07:15 PM UTC
- Duration
- 3h 30m
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.
Read the full incident report →
- Detected by Pingoru
- Mar 10, 2026, 10:40 PM UTC
- Resolved
- Mar 10, 2026, 11:24 PM UTC
- Duration
- 44m
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.
Read the full incident report →
- Detected by Pingoru
- Mar 10, 2026, 04:21 PM UTC
- Resolved
- Mar 10, 2026, 04:21 PM UTC
- Duration
- —
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.
Read the full incident report →
- Detected by Pingoru
- Mar 07, 2026, 08:08 AM UTC
- Resolved
- Mar 07, 2026, 11:06 AM UTC
- Duration
- 2h 58m
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.
Read the full incident report →
- Detected by Pingoru
- Mar 03, 2026, 06:01 PM UTC
- Resolved
- Mar 03, 2026, 06:01 PM UTC
- Duration
- —
Affected: GPU Cloud (graphql: api.runpod.io)
Timeline · 2 updates
-
resolved Mar 03, 2026, 06:01 PM UTC
We are currently experiencing issues with a downstream service provider, which is impacting Billing Explorer queries. downstream service provider is back to normal
-
resolved Mar 03, 2026, 06:01 PM UTC
We are currently experiencing issues with a downstream service provider, which is impacting Billing Explorer queries. ---- downstream service provider is back to normal
Read the full incident report →
- Detected by Pingoru
- Feb 21, 2026, 04:14 AM UTC
- Resolved
- Feb 21, 2026, 04:14 AM UTC
- Duration
- —
Timeline · 1 update
-
resolved Feb 21, 2026, 04:14 AM UTC
On Saturday February 22nd at approximately 3:15AM UTC our datacenter provider at the US-TX-4 suffered an unexpected network outage. Network engineers resolved the issue and network stability returned at 3:36AM UTC. The datacenter is performing a maintenance on Feb 22nd that will address this issue and correct it long term.
Read the full incident report →
- Detected by Pingoru
- Feb 21, 2026, 03:35 AM UTC
- Resolved
- Feb 21, 2026, 03:35 AM UTC
- Duration
- —
Timeline · 1 update
-
resolved Feb 21, 2026, 03:35 AM UTC
US-TX-4 recovered
Read the full incident report →