Skip to content

Outage tracker / RunPod / In the US

Is RunPod down in the US?

Vendor lists an old incident, not shown as liveWhat RunPod reports

RunPod still lists an incident opened on 2026-10-31, last updated 2026-11-05; it has been open past 72 hours, so we do not show it as live.

As of the last successful poll, 2026-11-05 17:17 UTC.

RunPod's status page

Our regional reading

This is our own reading from outside, shown beside the vendor's statement. It is not counted as a separate outage.

Checks passingin the US, measured from Ashburn and San Jose

All 2 of our probes in the US, in Ashburn and San Jose, read checks passing when they last checked RunPod at Nov 5, 2026, 5:19 PM UTC.

Over the last 24 hours we completed 252 checks from Ashburn and San Jose and 252 answered cleanly, 100.00% availability.

Of the 2 other regions we check RunPod from, all 2 read checks passing right now.

Email me when RunPod reports an incident on its status page, and again when it reports it resolved.

One email when it is reported and one when it is resolved, after you confirm the address. No account, no card.

This is RunPod's own statement from its status page, with our regional reading beside it.

What our Ashburn and San Jose probes measured

AshburnChecks passing142 checks in 24h, 100.00%
San JoseChecks passing110 checks in 24h, 100.00%

Last checked Nov 5, 2026, 5:19 PM UTC.

RunPod from Ashburn and San Jose over the last 30 days

Over the last 30 days, RunPod answered our Ashburn probe in 646 ms on average, and 1 check in 20 took longer than 943 ms.

Over the last 30 days, RunPod answered our San Jose probe in 805 ms on average, and 1 check in 20 took longer than 1,145 ms.

Ranked by average response time across the 4 cities we check RunPod from, Ashburn 2nd, San Jose 3rd; Frankfurt was fastest at 565 ms and Tokyo slowest at 1,373 ms.

From Ashburn and San Jose we ran 785 checks of RunPod in 4 days, and 783 answered cleanly: 99.74% availability.

2 of the 4 days had at least one failed check. The weakest was Nov 2 (UTC), at 99.04% across 105 checks.

In Ashburn local time (EST), RunPod was slowest around 4 PM, at 808 ms on average over the last 14 days, and quickest around 9 PM, at 441 ms.

Day (UTC)ChecksAvailabilityAverage response
Thu, Nov 5182100.00%691 ms
Wed, Nov 4251100.00%652 ms
Tue, Nov 324799.59%753 ms
Mon, Nov 210599.04%825 ms

RunPod outages measured from the US

Our Ashburn and San Jose probes measured no confirmed RunPod outage in the last 90 days.

How the other regions read right now

Of the 2 other regions we check RunPod from, all 2 read checks passing right now.

Probe cityRight nowLast 24h
FrankfurtChecks passing100.00% of 99 checks
TokyoChecks passing100.00% of 60 checks

Other countries we check RunPod from

How we measured this

The US readings on this page come from RealUptime's own Ashburn and San Jose probes against RunPod's public endpoints. They are not user reports, and they are not RunPod's own status page.

See RunPod's full check readings, the 90-day history by region, or the outage tracker methodology.

The US readings here are taken from that country and show the time of the last one, but RunPod has not yet accumulated enough continuous history for us to publish this page to search engines.

Check your own site from Ashburn

This page shows what we see when we check this service, using the same ten regions, for a site you run. RealUptime Monitor watches your own servers from inside your network, and it starts free.

Start monitoring your own servers

Run a service people depend on? Give them a status page on your own domain, checked every minute from six regions, for $9 a month. Get Starter