RunPod Outage History

26 incidents recorded over the last 365 days, 26 of them resolved. Durations are measured from when PulsAPI first saw the problem to when it cleared, which is usually longer than the vendor's own figure.

Live RunPod status17.31% uptime history

Every Recorded RunPod Incident

RunPod incidents, newest first, with date, duration and status.
DateIncidentDurationStatus
Aug 19, 2026EU-CZ-1 Network Issue109h 58mResolved
Aug 19, 2026EUR-NO-2 Network Issue111h 1mResolved
Aug 17, 2026EUR-IS-1 Network Issue162h 37mResolved
Aug 14, 2026US-IL-1 DC is Unavailable228h 37mResolved
Aug 13, 2026EUR-IS-1 Network Issue263h 20mResolved
Aug 6, 2026EUR-NO-1 Network Storage Issue428h 20mResolved
Jul 24, 2026Planned Network Switch Firmware Upgrade (EUR-NO-2)8h 0mResolved
Jul 21, 2026EUR-IS-1 Network Issue803h 32mResolved
Jul 11, 2026Planned Network Upgrade - Infiniband Switches & UFM8h 0mResolved
Jul 10, 2026EUR-IS-4 Network Issue1069h 43mResolved
Jul 10, 2026EUR-IS-1 Networking is Degraded1080h 7mResolved
Jul 9, 2026US-TX-3 Network Storage Issue1107h 43mResolved
Jul 8, 2026US-GA-2 Networking is Degraded1117h 51mResolved
Jul 8, 2026EUR-NO-1 Network Storage Issue1128h 15mResolved
Jul 7, 2026CA-MTL-3 Network Storage Issue1140h 47mResolved
Jul 5, 2026Planned Network Hardware Capacity Upgrade in AP-IN-1 6h 30mResolved
Jun 26, 2026US-PA-1 Network Inbound Issue1412h 7mResolved
Jun 20, 2026Planned Network Maintenance in AP-IN-15h 0mResolved
Jun 19, 2026EUR-IS-1 Network Issue1580h 21mResolved
Jun 6, 2026Planned Network Maintenance - AP-IN-18h 0mResolved
May 27, 2026Planned Network Maintenance - US-NE-12h 0mResolved
May 26, 2026Upstream authentication provider is experiencing an issue.1585h 48mResolved
May 26, 2026Upstream issue - Elevated image pull error rates from DockerHub Cloudfront1595h 45mResolved
May 14, 2026CA-MTL-3 Network Issue1875h 21mResolved
May 8, 2026Planned Network Maintenance AP-IN-16h 0mResolved
May 8, 2026Console: Delayed Pod starts and Empty Console Logs2022h 37mResolved

How to Read This RunPod Incident Log

Each row is an incident PulsAPI observed, not a summary written afterwards. The duration is wall-clock time between the first failing check and the first clean one, so it includes the window before RunPod acknowledged anything. Vendor post-mortems typically measure from acknowledgement, which is why their numbers are usually shorter.

Incidents still open have no duration yet and are listed as ongoing rather than being given a running total. The archive covers the last 365 days; anything older has aged out of the window rather than never having happened.

The longest single RunPod outage in this window ran 84d 6h, against a mean recovery of 30d 5h. If you depend on RunPod in a customer-facing path, the longest figure is the one to design around. The mean is what happens on a normal bad day; the maximum is what happens on the worst one.