Runpod status
GPU cloud, serverless API and listed platform resources.
Is Runpod down right now?
The saved report does not establish Runpod's overall availability. Provider report: operational. 42 published resources collected. 6 resources have unknown or unmonitored status. Collected 06 Oct 2026, 17:36:27 UTC (0 min ago). No unresolved incidents were included in this saved report.
Runpod's published platform resources and current or upcoming reports. These are provider reports, not independent checks of any model, account or region.
Official status
Provider reportProvider report: operational. 42 published resources collected. 6 resources have unknown or unmonitored status.
Runpod's published platform resources and current or upcoming reports. These are provider reports, not independent checks of any model, account or region.
| Component | Reported status |
|---|---|
| serverless api: api.runpod.ai | Operational |
| graphql: api.runpod.io | Operational |
| AP-IN-1 | Operational |
| serverless: queue engine | Operational |
| log/metrics api: hapi.runpod.net | Operational |
| AP-JP-1 | Operational |
| Serverless: CPU workers | Operational |
| pod proxy: proxy.runpod.net | Operational |
| CA-MTL-1 | Operational |
| graphql: transactional data store | Operational |
| CA-MTL-3 | Operational |
| ui: runpod.io/console | Operational |
| CA-MTL-4 | Unknown |
| Upstream Systems | Operational |
| EU-CZ-1 | Unknown |
| CPU Cloud | Operational |
| EU-FR-1 | Operational |
| EU-NL-1 | Operational |
| EU-RO-1 | Operational |
| EU-SE-1 | Unknown |
| EUR-IS-1 | Operational |
| EUR-IS-2 | Operational |
| EUR-IS-3 | Operational |
| EUR-IS-4 | Operational |
| EUR-NO-1 | Operational |
| EUR-NO-2 | Operational |
| OC-AU-1 | Operational |
| US-CA-2 | Operational |
| US-GA-2 | Operational |
| US-IL-1 | Unknown |
| US-KS-2 | Operational |
| US-MD-1 | Operational |
| US-MO-1 | Operational |
| US-MO-2 | Operational |
| US-NC-1 | Operational |
| US-NC-2 | Operational |
| US-NE-1 | Operational |
| US-TX-1 | Unknown |
| US-TX-3 | Unknown |
| US-TX-4 | Operational |
| US-WA-1 | Operational |
| US-PA-1 | Operational |
Status history
Each point shows the most severe saved state that day, separate from current status. Gaps stay gray; history starts with our first observation.
Regional availability is not independently verified. View coverage.
- Known status coverage
- 0% of the day
- Missing observations
- 24 h 0 min
- Inconclusive observations
- 0 min
- Saved observations
- 0
Durations describe observed reports or saved check states, bounded by freshness limits. They are not measured uptime or exact incident durations. Select a point, or use ← / → within a row.
Regional observations
Independent checksOfficial incidents in the latest report
This does not establish complete incident history or independently confirm recovery.
Scheduled maintenance
Future maintenance is displayed separately and does not change the current status.
Understanding Runpod status
What does the Runpod report cover?
GPU cloud, serverless API and listed platform resources.
How should I interpret a missing or old Runpod report?
Check the collection time and report scope. A missing report establishes no current availability. An expired report describes the last known state. A collection failure does not establish a Runpod outage.
Related service reports
Reports for related products and services in the same category. Each has its own scope and coverage; these links do not establish a dependency or an available alternative.
Did this answer your question?
Help shape this free first version. No account needed.
Status data checked at 06 Oct 2026, 17:37:02 UTC. Refresh reads saved data; it does not request the official source.