Question 1

What is RunPod's uptime?

Accepted Answer

Over the last 90 days, RunPod reported 98.86% uptime on its official status page. That figure is calculated from the public incident timeline at https://uptime.runpod.io, each minute of degraded, partial-outage, or major-outage status counts against the total. Sign up to Pingoru free to see RunPod's uptime history rolling forward in real time.

Question 2

Has RunPod had outages in 2026?

Accepted Answer

Yes, RunPod has had 29 incidents reported on its official status page so far in 2026. The full timeline (start times, durations, components affected) is shown above on this page. Pingoru re-checks the status page every 5 minutes so the count stays current.

Question 3

When was the last RunPod outage?

Accepted Answer

The most recent RunPod incident was "Elevated errors REST v2 APIs", which started on October 21, 2026 and was resolved on October 21, 2026. Pingoru captured this directly from https://uptime.runpod.io. See the full incident card above for affected components and the update timeline.

Question 4

How often does RunPod have outages?

Accepted Answer

Based on the last 90 days, RunPod averages 9.7 reported incidents per month on its official status page. Pingoru tracks each one with start time, duration, severity, and affected components: so you can see the pattern at a glance instead of digging through the vendor's archive.

Question 5

Where is RunPod's status page?

Accepted Answer

RunPod's official status page is https://uptime.runpod.io. Pingoru polls it every 5 minutes and renders the same data here, alongside every other cloud or SaaS provider you depend on, so you can spot multi-vendor incidents (e.g. AWS + Stripe + Cloudflare degrading at the same minute) without flipping between tabs.

Question 6

Is RunPod down right now?

Accepted Answer

RunPod has degraded performance. Pingoru checks the official status page every 5 minutes and flips this headline the moment RunPod reports a change. Current status is based on 45 tracked services.

Question 7

How does Pingoru know if RunPod is down?

Accepted Answer

We read https://uptime.runpod.io directly, using RunPod's own status page. If the vendor reports an incident, you see it within one check cycle, not after someone manually marks the page as down.

Question 8

Where can I get notified when RunPod has an outage?

Accepted Answer

Create a free Pingoru account and add RunPod as a monitor. You can filter to specific services, pick severity thresholds, and route alerts via email, Slack, Discord, or a webhook.

Question 9

RunPod's status page says the service is up, but I'm having issues. What's wrong?

Accepted Answer

Three common reasons:

• A real RunPod incident that hasn't been acknowledged on their public status page yet, vendor status pages are updated manually and typically lag the first customer reports by 10–30 minutes.
• A regional or account-scoped issue affecting a subset of customers. These rarely trigger a global status-page change.
• A local problem: ISP / DNS / your own software. Try reproducing from a mobile data connection and from a different network to isolate.

If you suspect a real RunPod issue that isn't reflected yet, contact their support to escalate. Subscribing here means you get the alert the moment they do post an update.

Question 10

Where does Pingoru get the official RunPod status?

Accepted Answer

We use RunPod's own status page at https://uptime.runpod.io. Nothing is read in a way the vendor hasn't explicitly made public. We use the same data their own dashboard uses. So our data is as accurate as what you'd see loading the status page yourself, but rolled into one dashboard alongside every other service you depend on.

Question 11

What does "Degraded" mean?

Accepted Answer

RunPod is reporting degraded performance. Services are up but slower than usual, or a subset of requests is failing.

Is RunPod down?

Active incident 1

Recent outages & incidents

See the full RunPod outage history

Incident record

Most affected components, last 12 months

Latest incidents

Outage history