">
sevanalysis

RunPod

Infrastructure. Source: RunPod status page.

History starts 2026-08-06 13:47 UTC, the oldest incident this status page still shows. Figures for the last 90 days cover only the part since then.

Incidents, last 90 days
23+
Median duration
1h 31m
p95 duration
23h 3m
Naming an upstream provider
0%
With a postmortem on the status page
0%

What failed, last 90 days

Network, DNS, routing or connectivity failure14
A zone, region or data center became unavailable4
Hardware, power, cooling or another physical failure2
The text does not say enough to tell2
A provider or third-party service this vendor depends on failed1

Tagged by claude-haiku-5-5 from each incident's updates. See the methodology.

Incidents per month

Hatched months are before the recorded history starts.

All recorded incidents

EUR-IS-1 Network Issue major 2026-10-20 17:36 UTC 1h 24m

Affected: EUR-IS-1

Failure mode: Network, DNS, routing or connectivity failure. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

  1. degraded

    We are experiencing network connectivity issues in a portion of servers in EUR-IS-1. We are working to resolve it.

  2. downtime

    We're experiencing network connectivity issues in EUR-IS-1.

  3. resolved

    Issue has been resolved and the network in EUR-IS-1 DC is operating normally.

Excerpts are shortened. Read the full incident on RunPod's status page.

Maintenance minor 2026-10-19 17:05 UTC 38h 9m

Affected: Upstream Systems

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A human mistake during operations. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

  1. degraded

    We are performing proactive maintenance on the Runpod Secure Cloud fleet. This may disrupt user workloads as pods are restarted

  2. resolved

    Systems are operating normally.

Excerpts are shortened. Read the full incident on RunPod's status page.

EU-RO-1 Network Storage Issue minor 2026-10-11 00:27 UTC 1h 30m

Affected: EU-RO-1

Failure mode: A zone, region or data center became unavailable. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

  1. degraded

    We are experiencing Network Storage issue in EU-RO-1 DC. We are working to resolve it.

  2. resolved

    Network storage issue in EU-RO-1 is resolved and operating normally.

Excerpts are shortened. Read the full incident on RunPod's status page.

US-CA-2 Network Storage Issue major 2026-10-09 16:31 UTC 1h 31m

Affected: US-CA-2

Failure mode: A zone, region or data center became unavailable. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

  1. downtime

    We are experiencing Network Storage issue in US-CA-2 DC. We are working to resolve it.

  2. resolved

    Network storage issue in US-CA-2 is resolved and operating normally.

Excerpts are shortened. Read the full incident on RunPod's status page.

US-CA-2 Networking is Degraded minor 2026-10-07 20:30 UTC 31m

Affected: US-CA-2

Failure mode: Network, DNS, routing or connectivity failure. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

  1. degraded

    Network connectivity for some machines in US-CA-2 DC is degraded. We are working on resolving the issue.

  2. resolved

    Issue has been resolved and the network in US-CA-2 DC is operating normally.

Excerpts are shortened. Read the full incident on RunPod's status page.

EUR-NO-2 Network Storage Issue minor 2026-09-29 17:00 UTC 3h 30m

Affected: EUR-NO-2

Failure mode: A zone, region or data center became unavailable. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

  1. degraded

    We are experiencing Network Storage issue in EUR-NO-2 DC. We are working to resolve it.

  2. resolved

    Network storage issue in EUR-NO-2 is resolved and operating normally.

Excerpts are shortened. Read the full incident on RunPod's status page.

EU-SE-1 Network Issue major 2026-09-24 21:12 UTC 33m

Affected: EU-SE-1

Failure mode: Network, DNS, routing or connectivity failure. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

  1. downtime

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

  2. resolved

    Issue has been resolved and the network in EU-SE-1 DC is operating normally.

Excerpts are shortened. Read the full incident on RunPod's status page.

EUR-IS-2 DC is Degraded minor 2026-09-22 16:06 UTC 5h 23m

Affected: EUR-IS-2

Failure mode: Hardware, power, cooling or another physical failure. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

  1. degraded

    We are experiencing power issues in a portion of servers in EUR-IS-2. We are working to resolve it.

  2. resolved

    Issue has been resolved and EUR-IS-2 DC is operating normally.

Excerpts are shortened. Read the full incident on RunPod's status page.

US-IL-1 Network Issue major 2026-09-20 20:04 UTC 14m

Affected: US-IL-1

Failure mode: Network, DNS, routing or connectivity failure. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

  1. downtime

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

  2. resolved

    Issue has been resolved and the network in US-IL-1 DC is operating normally.

Excerpts are shortened. Read the full incident on RunPod's status page.

EUR-IS-2 Network Issue minor 2026-09-18 12:50 UTC 2h

Affected: EUR-IS-2

Failure mode: Network, DNS, routing or connectivity failure. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

  1. degraded

    We are experiencing network connectivity issues in a portion of servers in EUR-IS-2. We are working to resolve it.

  2. resolved

    Issue has been resolved and the network in EUR-IS-2 DC is operating normally.

Excerpts are shortened. Read the full incident on RunPod's status page.

Elevated errors on the GraphQL and REST v2 APIs minor 2026-09-17 14:04 UTC 1h

Affected: graphql: api.runpod.io

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

  1. degraded

    Error rates on the GraphQL API (api.runpod.io/graphql) and REST v2 API (api.runpod.io/v2) have returned to normal as of 14:10 UTC. Requests are no longer being rejected. We are continuing to monitor while we complete the underlying fix.

  2. resolved

    We've resolved the issue and services are operating normally.

Excerpts are shortened. Read the full incident on RunPod's status page.

EU-NL-1 Network Issue major 2026-09-17 03:41 UTC 1h 59m

Affected: EU-NL-1

Failure mode: Network, DNS, routing or connectivity failure. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

  1. downtime

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

  2. resolved

    Issue has been resolved and the network in EU-NL-1 DC is operating normally.

Excerpts are shortened. Read the full incident on RunPod's status page.

EUR-IS-2 Network Issue minor 2026-09-16 17:26 UTC 1h 8m

Affected: EUR-IS-2

Failure mode: Network, DNS, routing or connectivity failure. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

  1. degraded

    We are experiencing network connectivity issues in a portion of servers in EUR-IS-2. We are working to resolve it.

  2. resolved

    Issue has been resolved and the network in EUR-IS-2 DC is operating normally.

Excerpts are shortened. Read the full incident on RunPod's status page.

EUR-IS-1 Network Issue minor 2026-09-12 16:08 UTC 13h 25m

Affected: EUR-IS-1

Failure mode: Network, DNS, routing or connectivity failure. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

  1. degraded

    We are experiencing network connectivity issues to certain internet endpoints in a portion of servers in EUR-IS-1. We are working to resolve it.

  2. resolved

    Issue has been resolved and the network in EUR-IS-1 DC is operating normally.

  3. degraded

    Issue has resurfaced with network connectivity issues to certain internet endpoints in a portion of servers in EUR-IS-1. We are working to resolve it.

  4. resolved

    Issue has been resolved and the network in EUR-IS-1 DC is operating normally.

Excerpts are shortened. Read the full incident on RunPod's status page.

CA-MTL-4 Network Issue major 2026-09-09 20:56 UTC 28m

Affected: CA-MTL-4

Failure mode: Network, DNS, routing or connectivity failure. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

  1. downtime

    We are experiencing network connectivity issues in CA-MTL-4. We are working to resolve it.

  2. resolved

    Issue has been resolved and the network in CA-MTL-4 DC is operating normally.

Excerpts are shortened. Read the full incident on RunPod's status page.

SSH Proxy and Serverless are experiencing elevated error rates minor 2026-09-06 19:05 UTC 1h 25m

Affected: serverless api: api.runpod.ai, pod proxy: proxy.runpod.net

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

  1. degraded

    12:43 PDT Update: Engineers are continuing to work towards resolution. 12:05 PDT Update: We are investigating on resolving the issue.

  2. resolved

    We've resolved the issue and services are operating normally.

Excerpts are shortened. Read the full incident on RunPod's status page.

US-NC-2 Networking is Degraded minor 2026-09-01 04:40 UTC 1h 46m

Affected: US-NC-2

Failure mode: Network, DNS, routing or connectivity failure. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

  1. degraded

    Network connectivity to some endpoints is unreachable for machines in US-NC-2 DC. We are working on resolving the issue.

  2. resolved

    Issue has been resolved and the network in US-NC-2 DC is operating normally.

Excerpts are shortened. Read the full incident on RunPod's status page.

EU-CZ-1 Network Issue minor 2026-08-19 20:09 UTC 1h 12m

Affected: EU-CZ-1

Failure mode: Network, DNS, routing or connectivity failure. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

  1. degraded

    We are experiencing network connectivity issues in a portion of servers in EU-CZ-1. We are working to resolve it.

  2. resolved

    Issue has been resolved and the network in EU-CZ-1 DC is operating normally.

Excerpts are shortened. Read the full incident on RunPod's status page.

EUR-NO-2 Network Issue major 2026-08-19 19:06 UTC 48m

Affected: EUR-NO-2

Failure mode: Network, DNS, routing or connectivity failure. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

  1. downtime

    We are experiencing network connectivity issues in EUR-NO-2. We are working to resolve it.

  2. resolved

    Issue has been resolved and the network in EUR-NO-2 DC is operating normally.

Excerpts are shortened. Read the full incident on RunPod's status page.

EUR-IS-1 Network Issue minor 2026-08-17 15:30 UTC 3h

Affected: EUR-IS-1

Failure mode: Network, DNS, routing or connectivity failure. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

  1. degraded

    We are experiencing network connectivity issues in a portion of servers in EUR-IS-1. We are working to resolve it.

  2. resolved

    Issue has been resolved and the network in EUR-IS-1 DC is operating normally.

Excerpts are shortened. Read the full incident on RunPod's status page.

US-IL-1 DC is Unavailable major 2026-08-14 21:30 UTC 6h 10m

Affected: US-IL-1

Failure mode: Hardware, power, cooling or another physical failure. Root cause: Hardware or facility. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

  1. downtime

    We are experiencing a power outage in US-IL-1. We are working to resolve it.

  2. downtime

    We are continuing to work towards restoring power to US-IL-1 DC.

  3. degraded

    We've restored power for most of the servers and working to restore the rest.

  4. resolved

    The power issue in US-IL-1 DC has been resolved, and the datacenter is operating normally.

Excerpts are shortened. Read the full incident on RunPod's status page.

EUR-IS-1 Network Issue minor 2026-08-13 10:47 UTC 23h 3m

Affected: EUR-IS-1

Failure mode: Network, DNS, routing or connectivity failure. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

  1. degraded

    We are experiencing network connectivity issues in a portion of servers in EUR-IS-1. We are working to resolve it.

  2. resolved

    Issue has been resolved and the network in EUR-IS-1 DC is operating normally.

Excerpts are shortened. Read the full incident on RunPod's status page.

EUR-NO-1 Network Storage Issue major 2026-08-06 13:47 UTC 1h 51m

Affected: EUR-NO-1

Failure mode: A zone, region or data center became unavailable. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

  1. downtime

    We are experiencing Network Storage issue in EUR-NO-1 DC. We are working to resolve it.

  2. downtime

    We are still working to resolve the issue and will share another update on progress.

  3. resolved

    Network storage issue in EUR-NO-1 is resolved and operating normally.

Excerpts are shortened. Read the full incident on RunPod's status page.