Skip to main content
RunPod

Maintenance: [Planned Maintenance] Network Performance Upgrades - EUR-NO-2

Maintenance Lasted 0m · started · RunPod's page

Level
confirmed
Worst impact
Maintenance

What to do

  • Check whether your product depends on RunPod. Check your stack

    Paste a package.json, lockfile, Terraform or a list of domains at down.guide/stack to see every provider you depend on.
  • Check that everything you run on RunPod came back after the window closed 2026-04-02 20:06 UTC.

  • Subscribe to RunPod's feed to hear about the next one first. RSS feed

    https://down.guide/feed?provider=runpod works in Slack (/feed subscribe), Discord feed bots and any RSS reader.

Updates from RunPod 1

  1. resolved

    Maintenance Notice We will be performing scheduled network maintenance at our EUR-NO-2 data center. This work is required to optimize traffic flow and ensure the continued stability of our infrastructure. Details Location: EUR-NO-2 Start Time: April 9, 2026, at 11:00 UTC End Time: April 9, 2026, at 11:30 UTC Summary of Work This maintenance is focused on infrastructure improvements to enhance TCP performance on IPv4 and resolve existing performance degradation with non-TCP protocols across both IPv4 and IPv6. Service Impact Connectivity: All systems within the EUR-NO-2 region will experience a brief interruption. Expected Downtime: Approximately 5 minutes during the maintenance window. Note: Our team will be monitoring the systems closely throughout the process to ensure services are restored as quickly as possible. We appreciate your understanding and apologize for any inconvenience this may cause as we work to provide a better experience.

    provider

Reports count in aggregate; nothing about you is shown.

Corrections

None so far.

Something wrong on this page? Report an error or send us a note. Every fix is listed here.

Questions about DWN-74c0a4b899

Is this RunPod maintenance still going on?

No, it ended 2026-04-02 20:06 UTC.

How long did it last?

0m, from 2026-04-02 20:06 UTC to 2026-04-02 20:06 UTC, by the times RunPod posted.

What caused it?

RunPod hasn't published a root cause. If it does, it shows here.

Where does this come from?

RunPod's official status page, https://uptime.runpod.io, quoted verbatim. down.guide's own probes, reports and social counts are labeled as ours.