outages.live
Live
RunPodMaintenance · 2026-11-05 06:00 UTC

Planned Power Maintenance EUR-IS-3 & EUR-IS-4

MaintenanceOfficial update

Planned Power Maintenance for EUR-IS-3 and EUR-IS-4 Maintenance Time The maintenance will take place on Thursday, November 5, 2026 Iceland Time (GMT/UTC): 06:00 – 17:40 To ensure the long-term safety, thermal stability, and electrical protection of customer GPU nodes, the data center building owner and the power company will perform critical preventative infrastructure maintenance on November 5, 2026. Customers should back up and save all active jobs beforehand so they can seamlessly resume work once services are systematically restored. Scope: Full-site power outage. All EUR-IS-3 and EUR-IS-4 devices will be shut down and taken offline during the maintenance window.

The latest update from RunPod.

State

Maintenance

Starts

in 3 d

2026-11-05 06:00 UTC

Ongoing for

Not started

Worst impact

Maintenance

Updates

Times in UTC

As posted by RunPod

Maintenance2026-11-01 20:03 UTC

Planned Power Maintenance for EUR-IS-3 and EUR-IS-4 Maintenance Time The maintenance will take place on Thursday, November 5, 2026 Iceland Time (GMT/UTC): 06:00 – 17:40 To ensure the long-term safety, thermal stability, and electrical protection of customer GPU nodes, the data center building owner and the power company will perform critical preventative infrastructure maintenance on November 5, 2026. Customers should back up and save all active jobs beforehand so they can seamlessly resume work once services are systematically restored. Scope: Full-site power outage. All EUR-IS-3 and EUR-IS-4 devices will be shut down and taken offline during the maintenance window.

Affected components

2
EUR-IS-3EUR-IS-4

RunPod in the last 90 days

Full history
90 days agoToday

Incidents in 90 days

1

Days with an incident

3

Median duration

Not enough data

This incident

Not comparable

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

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