RunPod reported "EU-RO-1 Network Storage Issue" on its status page at 2026-10-11 00:27 UTC.

RunPod lists these components: EU-RO-1.

When did the incident start and end?

It started at 2026-10-11 00:27 UTC and ended at 2026-10-11 01:57 UTC. It lasted 1 h 30 min.

How do I get alerts for RunPod?

Subscribe to the RunPod live feed over RSS or in Slack, or add the outages.live MCP server to your coding agent.

Where does this information come from?

From the official status page of RunPod. outages.live reads it every few minutes and keeps every update.

RunPodIncident · 2026-10-11 00:27 UTC

EU-RO-1 Network Storage Issue

ResolvedOfficial update

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

The latest update from RunPod.

State

Resolved

Started

22 d ago

2026-10-11 00:27 UTC

Lasted

1 h 30 min

until 2026-10-11 01:57 UTC

Worst impact

Degraded

Timeline

2 updates

00:2700:4901:1201:3401:57

DegradedUpdate postedTimes in UTC

Degraded

1 h 30 min 100%

Updates

Times in UTC

As posted by RunPod

Resolved2026-10-11 01:57 UTC

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

Degraded2026-10-11 00:27 UTC

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

Affected components

EU-RO-1

RunPod in the last 90 days

Full history

90 days agoToday

Incidents in 90 days

Days with an incident

Median duration

1 h 31 min

This incident

About the median

How long each incident lasted, on the day it started. The outlined bar is this incident.

38 h 9 min

median 1 h 31 min

90 days agoToday

Other RunPod incidents

All incidents

RunPod·CA-MTL-1 and EU-SE-1 DC is Unavailable

RunPod reports that CA-MTL-1 and EU-SE-1 do not work. The outage is ongoing. RunPod reports that it is working to resolve the issue.

Major outageupdated 1 d ago

RunPod·US-KS-2 Network Issue

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

Resolvedresolved 4 d ago

RunPod·US-WA-1 Network Issue

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

Resolvedresolved 4 d ago

RunPod·EUR-IS-3 Network Issue

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

Resolvedresolved 8 d ago

RunPod·Increased errors for S3 API

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

Resolvedresolved 10 d ago

Follow RunPod

Your coding agent knows when RunPod is down, and tells you when a failure is theirs, not yours. You can also get RunPod incidents in a feed reader or in Slack.

Prompt

Install the outages.live MCP server, so that when something breaks you can tell if the cause is a provider we depend on and not my code. It reads the official status pages of cloud, AI, payment and developer providers and gives you their incidents as MCP tools.

Add it as a remote MCP server named "outages" at https://outages.live/mcp (Streamable HTTP, no authentication), with your CLI command or your MCP config file.

Then:
1. Make sure it connects and shows the tools get_provider, list_feed and send_feedback.
2. Call get_provider with "runpod" and tell me if RunPod has a problem right now.
3. From now on, when a call to a third-party service fails or becomes slow, call get_provider for that service before you change my code.

Paste this into any coding agent. It adds the server with its own MCP setup.

RSS

https://outages.live/feed.xml?providers=runpod

Slack

/feed subscribe https://outages.live/feed.xml?providers=runpod

FAQ

Go from tracking outages to fixing production issues with Polylane.

Try Polylane