outages.live
Live
RunPodMaintenance ·

US-IL-1 Server Relocation

ResolvedOfficial update

Our datacenter partner has informed us that server relocation is taking the team longer than expected. We expect to have service fully restored by 7AM/CST on 11/7/2026

The latest update from RunPod.

State

Resolved

Started

Lasted

16 h 2 min

Worst impact

Maintenance

Timeline

2 updates
23:0103:0107:0211:0215:03
MaintenanceUpdate postedTimes in UTC

Maintenance

16 h 2 min 100%

Updates

Times in UTC

As posted by RunPod

Resolved
Maintenance

Our datacenter partner has informed us that server relocation is taking the team longer than expected. We expect to have service fully restored by 7AM/CST on 11/7/2026

Affected components

1
US-IL-1

RunPod in the last 90 days

Full history
90 days agoToday

Incidents in 90 days

24

Days with an incident

30

Median duration

1 h 39 min

This incident

Not comparable

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

5 days
median 1 h 39 min
90 days agoToday

Other RunPod incidents

All incidents

RunPod·EUR-IS-3 Network Issue

RunPod reported a network connectivity problem in the EUR-IS-3 data center. RunPod stated that the issue is resolved and that the network in EUR-IS-3 operates normally. The outage lasted about 13 hours and 33 minutes.

Resolved

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

RunPod reported a major outage in the CA-MTL-1 and EU-SE-1 data centers. RunPod says the issue is resolved and both data centers operate normally. The outage lasted from 31 October 2026 to 6 November 2026.

Resolved

RunPod·US-KS-2 Network Issue

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

Resolved

RunPod·US-WA-1 Network Issue

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

Resolved

RunPod·EUR-IS-3 Network Issue

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

Resolved

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.cc/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.cc/feed.xml?providers=runpod
Slack
/feed subscribe https://outages.cc/feed.xml?providers=runpod

FAQ

Go from tracking outages to fixing production issues with Polylane.

Try Polylane