RunPod Outage History

RunPod is up right now

Pingoru has recorded 77 incidents for RunPod: 77 in the last 12 months and 25 in the last 90 days.

Source: uptime.runpod.io

77incidents recorded
77last 12 months
25last 90 days
6 hourstypical duration
Incidents per month
01020AprMayJunJulAugSepOct7
Share of hours with an open incident, any severity
0%50%100%AprMayJunJulAugSepOct2%
Pingoru began tracking RunPod in April 2026, so earlier months are not shown. Hover a bar for its value.
Show as a table
MonthIncidentsHours with an open incident
April 202694 of 720 (1%)
May 20269139 of 744 (19%)
June 20264189 of 720 (26%)
July 2026936 of 744 (5%)
August 2026636 of 744 (5%)
September 20261233 of 720 (5%)
October 2026714 of 587 (2%)

Incidents, newest first

Minor July 9, 2026 US-TX-3 Network Storage Issue 10h 26m section-192137 (US-TX-3), section-192137 (US-TX-3)

Started Jul 09, 2026, 06:24 AM UTC· resolved Jul 09, 2026, 04:50 PM UTC

  1. investigating Jul 09, 2026, 06:24 AM UTC

    We are experiencing Network Storage issue in US-TX-3 DC. We are working to resolve it.

Read the full incident report →

Minor July 8, 2026 US-GA-2 Networking is Degraded 1h 56m section-192137 (US-GA-2), section-192137 (US-GA-2)

Started Jul 08, 2026, 08:16 PM UTC· resolved Jul 08, 2026, 10:12 PM UTC

No vendor updates were posted for this incident.

Read the full incident report →

Minor July 7, 2026 CA-MTL-3 Network Storage Issue 12h 36m section-192137 (CA-MTL-3), section-192137 (CA-MTL-3)

Started Jul 07, 2026, 09:20 PM UTC· resolved Jul 08, 2026, 09:56 AM UTC

No vendor updates were posted for this incident.

Read the full incident report →

Minor June 26, 2026 US-PA-1 Network Inbound Issue – section-192137 (US-GA-2), section-192137 (US-PA-1)

Started Jun 26, 2026, 02:00 PM UTC· resolved Jun 26, 2026, 02:00 PM UTC

No vendor updates were posted for this incident.

Read the full incident report →

Minor June 2, 2026 CA-MTL-1 recovered –

Started Jun 02, 2026, 11:29 PM UTC· resolved Jun 02, 2026, 11:29 PM UTC

No vendor updates were posted for this incident.

Read the full incident report →

Minor June 1, 2026 EU-SE-1 recovered –

Started Jun 01, 2026, 09:48 PM UTC· resolved Jun 01, 2026, 09:48 PM UTC

No vendor updates were posted for this incident.

Read the full incident report →

Minor May 26, 2026 Upstream authentication pro... – section-163103 (ui: runpod.io/console)

Started May 26, 2026, 09:57 PM UTC· resolved May 26, 2026, 09:57 PM UTC

No vendor updates were posted for this incident.

Read the full incident report →

Minor May 26, 2026 Upstream issue - Elevated i... 13d 7h section-163103 (Upstream Systems)

Started May 26, 2026, 12:00 PM UTC· resolved Jun 08, 2026, 07:52 PM UTC

  1. investigating May 26, 2026, 12:00 PM UTC

    We're observing increased error rates in downloading images from Dockerhub. We've notified their team and we are awaiting further detail. We will provide additional information as we receive it. Docker added Cloudfront to DockerHub's distribution network on 2026-05-20, since that time, we've seen a growing level of errors for image pulls when distributed over Cloudfront. The Docker team is looking into the issue. Runpod is not able to control the selection of which CDN is used and has confirmed that it's not a Runpod specific issue. At this point, it's believed that images with layers larger than 50GB cause Cloudfront to have different cache behavior, resulting in an error. As Docker remediates the issue, we advise using an alternate image distribution network or reduce layer sizes below 50GB. This results in error messages in the console similar to: ERROR: The request could not be satisfied ERROR The request could not be satisfied. Generated Wed, 03 Jun 2026 23:35:36 GMT Request ID: yFjsOWdc6NZVG8D5l5omQzXCD4vMBR-4h_JE5gmXP06Y3vxx3M9thw==

Read the full incident report →

Minor May 22, 2026 Runpod.io website is unavai... – section-163103 (Upstream Systems)

Started May 22, 2026, 05:40 PM UTC· resolved May 22, 2026, 05:40 PM UTC

No vendor updates were posted for this incident.

Read the full incident report →

Major May 15, 2026 EU-FR-1 went down 37m

Started May 15, 2026, 02:22 PM UTC· resolved May 15, 2026, 02:59 PM UTC

No vendor updates were posted for this incident.

Read the full incident report →

Minor May 14, 2026 CA-MTL-3 Network Issue 1h 25m section-192137 (CA-MTL-3)

Started May 14, 2026, 08:24 PM UTC· resolved May 14, 2026, 09:49 PM UTC

No vendor updates were posted for this incident.

Read the full incident report →

Minor May 8, 2026 Upstream Systems recovered –

Started May 08, 2026, 08:02 PM UTC· resolved May 08, 2026, 08:02 PM UTC

No vendor updates were posted for this incident.

Read the full incident report →

Minor May 8, 2026 Console: Delayed Pod starts... 4h 41m section-163103 (log/metrics api: hapi.runpod.net), section-163103 (ui: runpod.io/console)

Started May 08, 2026, 05:08 PM UTC· resolved May 08, 2026, 09:49 PM UTC

No vendor updates were posted for this incident.

Read the full incident report →

Minor May 8, 2026 US-CA-2 recovered –

Started May 08, 2026, 01:46 AM UTC· resolved May 08, 2026, 01:46 AM UTC

No vendor updates were posted for this incident.

Read the full incident report →

Minor April 28, 2026 CA-MTL-3 recovered –

Started Apr 28, 2026, 05:55 AM UTC· resolved Apr 28, 2026, 05:55 AM UTC

No vendor updates were posted for this incident.

Read the full incident report →

Minor April 28, 2026 CA-MTL-1 and CA-MTL-3 Netwo... 3h 20m section-192137 (CA-MTL-1), section-192137 (CA-MTL-3)

Started Apr 28, 2026, 04:52 AM UTC· resolved Apr 28, 2026, 08:12 AM UTC

  1. 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.

Read the full incident report →

Minor April 21, 2026 CA-MTL-4 recovered –

Started Apr 21, 2026, 05:03 PM UTC· resolved Apr 21, 2026, 05:03 PM UTC

No vendor updates were posted for this incident.

Read the full incident report →

Minor April 7, 2026 EUR-IS-2 recovered –

Started Apr 07, 2026, 11:22 AM UTC· resolved Apr 07, 2026, 11:22 AM UTC

No vendor updates were posted for this incident.

Read the full incident report →

Minor April 4, 2026 Incident Notice: Power Serv... – section-192137 (US-NC-1)

Started Apr 04, 2026, 05:58 PM UTC· resolved Apr 04, 2026, 05:58 PM UTC

No vendor updates were posted for this incident.

Read the full incident report →

Minor March 31, 2026 EU-FR-1 recovered –

Started Mar 31, 2026, 02:41 AM UTC· resolved Mar 31, 2026, 02:41 AM UTC

No vendor updates were posted for this incident.

Read the full incident report →

Minor March 31, 2026 EU-FR-1 Network Issue 7h 28m section-192137 (EU-FR-1)

Started Mar 31, 2026, 01:11 AM UTC· resolved Mar 31, 2026, 08:39 AM UTC

  1. investigating Mar 31, 2026, 01:11 AM UTC

    We are experiencing network connectivity issues in EU-FR-1. We are working to resolve it.

Read the full incident report →

Minor March 25, 2026 US-NC-1 Network Issue 30m section-192137 (US-NC-1)

Started Mar 25, 2026, 04:18 AM UTC· resolved Mar 25, 2026, 04:48 AM UTC

  1. investigating Mar 25, 2026, 04:18 AM UTC

    We are experiencing network connectivity issues in US-NC-1. We are working to resolve it.

Read the full incident report →

Minor March 17, 2026 US-NE-1 internet network sp... 19h 32m section-192137 (US-NE-1)

Started Mar 17, 2026, 04:23 PM UTC· resolved Mar 18, 2026, 11:55 AM UTC

  1. investigating Mar 17, 2026, 04:23 PM UTC

    US-NE-1 DC is experiencing slower internet connectivity. We are working on resolving this issue.

Read the full incident report →

Minor March 16, 2026 CA-MTL-1 Connectivity issue... 4h 2m section-192137 (CA-MTL-1)

Started Mar 16, 2026, 09:43 PM UTC· resolved Mar 17, 2026, 01:45 AM UTC

  1. 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.

Read the full incident report →

Minor March 14, 2026 Issue with creating new sto... 45m section-163088 (serverless api: api.runpod.ai), section-163103 (ui: runpod.io/console)

Started Mar 14, 2026, 01:36 AM UTC· resolved Mar 14, 2026, 02:21 AM UTC

  1. 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.

Read the full incident report →