Live

Emergency Network Maintenance - CA-MTL-4

MaintenanceOfficial update

As part of our ongoing efforts to strengthen and improve our infrastructure, we will be performing an emergency maintenance at our CA-MTL-4 datacenter during the window outlined below. Maintenance Window Start: Wednesday, November 18th at 06:00 PM EST End: Wednesday, November 18th at 10:00 PM EST This maintenance is intended to enhance the performance and reliability of our internet services. We do not expect any service impact, and this notice is for informational purposes only. While every precaution is being taken to avoid interruptions, there may be brief periods of packet loss during the maintenance window.

The latest update from RunPod.

State

Maintenance

Starts

Ongoing for

Not started

Worst impact

Maintenance

Updates

Times in UTC

As posted by RunPod

Maintenance

As part of our ongoing efforts to strengthen and improve our infrastructure, we will be performing an emergency maintenance at our CA-MTL-4 datacenter during the window outlined below. Maintenance Window Start: Wednesday, November 18th at 06:00 PM EST End: Wednesday, November 18th at 10:00 PM EST This maintenance is intended to enhance the performance and reliability of our internet services. We do not expect any service impact, and this notice is for informational purposes only. While every precaution is being taken to avoid interruptions, there may be brief periods of packet loss during the maintenance window.

Affected components

1
CA-MTL-4

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

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