RunPod Outage History

47 incidents recorded over the last 365 days, 46 of them resolved, 1 still open. 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 status97.86% uptime history

Every Recorded RunPod Incident

RunPod incidents, newest first, with date, duration and status.
DateIncidentDurationStatus
Oct 27, 2026Planned Network Maintenance - EU-FR-159 minResolved
Oct 20, 2026Planned Network Maintenance - EU-FR-159 minResolved
Oct 11, 2026EU-RO-1 Network Storage Issue—Investigating
Oct 9, 2026US-CA-2 Network Storage Issue32h 50mResolved
Oct 9, 2026Emergency Network Maintenance - EUR-NO-29h 30mResolved
Oct 7, 2026US-CA-2 Networking is Degraded76h 32mResolved
Sep 29, 2026EUR-NO-2 Network Storage Issue272h 21mResolved
Sep 29, 2026Planned Network Maintenance EUR-NO-22h 59mResolved
Sep 24, 2026EU-SE-1 Network Issue388h 9mResolved
Sep 24, 2026Emergency Network Maintenance for CA-MTL-4 4h 0mResolved
Sep 22, 2026EUR-IS-2 DC is Degraded441h 15mResolved
Sep 20, 2026US-IL-1 Network Issue485h 17mResolved
Sep 18, 2026EUR-IS-2 Network Issue540h 31mResolved
Sep 17, 2026Elevated errors on the GraphQL and REST v2 APIs563h 17mResolved
Sep 17, 2026EU-NL-1 Network Issue573h 40mResolved
Sep 16, 2026EUR-IS-2 Network Issue583h 55mResolved
Sep 12, 2026EUR-IS-1 Network Issue681h 13mResolved
Sep 9, 2026CA-MTL-4 Network Issue748h 25mResolved
Sep 8, 2026Planned PDU maintenance: US-WA-1 & US-WA-23h 0mResolved
Sep 6, 2026SSH Proxy and Serverless are experiencing elevated error rates822h 16mResolved
Sep 1, 2026US-NC-2 Networking is Degraded956h 41mResolved
Aug 19, 2026EU-CZ-1 Network Issue1253h 12mResolved
Aug 19, 2026EUR-NO-2 Network Issue1254h 15mResolved
Aug 17, 2026EUR-IS-1 Network Issue1305h 51mResolved
Aug 14, 2026US-IL-1 DC is Unavailable1371h 51mResolved
Aug 13, 2026EUR-IS-1 Network Issue1406h 34mResolved
Aug 6, 2026EUR-NO-1 Network Storage Issue1571h 34mResolved
Jul 24, 2026Planned Network Switch Firmware Upgrade (EUR-NO-2)8h 0mResolved
Jul 21, 2026EUR-IS-1 Network Issue1705h 25mResolved
Jul 11, 2026Planned Network Upgrade - Infiniband Switches & UFM8h 0mResolved
Jul 10, 2026EUR-IS-4 Network Issue1971h 36mResolved
Jul 10, 2026EUR-IS-1 Networking is Degraded1982h 0mResolved
Jul 9, 2026US-TX-3 Network Storage Issue2009h 36mResolved
Jul 8, 2026US-GA-2 Networking is Degraded2019h 44mResolved
Jul 8, 2026EUR-NO-1 Network Storage Issue2030h 8mResolved
Jul 7, 2026CA-MTL-3 Network Storage Issue2042h 40mResolved
Jul 5, 2026Planned Network Hardware Capacity Upgrade in AP-IN-1 6h 30mResolved
Jun 26, 2026US-PA-1 Network Inbound Issue1593h 59mResolved
Jun 20, 2026Planned Network Maintenance in AP-IN-15h 0mResolved
Jun 19, 2026EUR-IS-1 Network Issue1762h 13mResolved
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

Hear about the next one while it is open

Everything above is a record written after the fact. We can email you when the next RunPod incident opens instead, at the point where knowing still changes what you do.

Free, no password, no card. Unsubscribe in one click.

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 85d 2h, against a mean recovery of 35d 20h. 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.