RunPod outage history

We hold 49 RunPod incidents from RunPod's status page, the newest from Nov 18, 2026. 44 of the 49 listed carry RunPod's own update timeline. Each one links to a page with the vendor's updates and what our five-minute checks recorded while it was open.

Uptime & history

Tracking since Jun 22, 2026
Currently up for 13d 11h since the last recorded problem.
Operational · 24h
49.31%
1 incident · no downtime
288 checks
Operational · 7d
72.56%
2 incidents · no downtime
2015 checks
Operational · 30d
66.95%
16 incidents · ≈6d 20h degraded
8638 checks
Operational · since Jun 22, 2026
86.41%
44 incidents · ≈14d 21h degraded
41682 checks

% of our checks that found RunPod fully operational — a degraded check counts against it, because a slow or partly-broken service is not a working one. Down and degraded time are counted at our 5-minute check resolution, so both are approximate. Longer windows fill in as data accrues — we never show uptime we haven't measured.

Recent checks
oldernow
Past incidents

How RunPod fails

Since Jun 27, 2026, RunPod's status page has marked 25 RunPod components as impaired, across 4,982 of our five-minute readings. CA-MTL-1 accounts for the most: 1,528 readings (about 127 hours) on 6 days, 1,236 of them marked as an outage rather than degraded, most recently on Nov 19, 2026. Next is EUR-IS-1, with 872 readings on 11 days. We hold 49 RunPod incidents from RunPod's status page, the earliest from Apr 4, 2026. Of the 47 that RunPod closed with an end time, the median lasted 2 h 31 min.

ComponentOutageDegradedMaint.DaysLast
CA-MTL-112362925536Nov 19, 2026
EUR-IS-13084255311Nov 19, 2026
US-IL-173888215Nov 19, 2026
Upstream Systems16520—6Oct 30, 2026
EU-SE-1503—5773Nov 19, 2026
EUR-IS-3182—6974Nov 19, 2026
EUR-IS-271015534Nov 19, 2026
EUR-NO-227448053Nov 19, 2026

Incidents by month: Apr 2026: 4 · May 2026: 1 · Aug 2026: 6 · Sep 2026: 15 · Oct 2026: 17 · Nov 2026: 6

Counts are five-minute readings of RunPod's own component statuses, recorded only when a component is not operational. Hours are readings times five minutes, so a gap in our recording would undercount, never overcount.

Every recorded incident

November 2026 · 6

October 2026 · 17

September 2026 · 15

August 2026 · 6

May 2026 · 1

April 2026 · 4

Incidents and their updates are RunPod's own words from its status page, recorded every five minutes; we never add an inferred cause. AIDownCheck is independent and not affiliated with RunPod.