Skip to main content
RunPod

Maintenance: Planned Maintenance: Redundancy Upgrade – 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-02-09 20:00 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

    Activity: Redundancy upgrade Location: EUR-NO-2 - Lefdal Urgency: High Priority Description of Change This maintenance covers critical redundancy upgrades to the infrastructure at EUR-NO-2, aimed at improving system resilience and operational stability. Reason for Change To increase redundancy and overall infrastructure stability within the facility. Expected Service Impact Downtime: A service downtime of approximately 3 hours is expected during the maintenance window. Storage Status: Local storage across all GPU nodes will be in read-only mode. All services and compute tasks will be shut down to ensure data integrity during the infrastructure upgrade. System Integrity: To avoid data inconsistency and ensure system integrity, all affected services and devices at the site will be shut down prior to the maintenance start. Restoration: Full service restoration will commence once the maintenance is successfully completed.

    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-a614cc7b83

Is this RunPod maintenance still going on?

No, it ended 2026-02-09 20:00 UTC.

How long did it last?

0m, from 2026-02-09 20:00 UTC to 2026-02-09 20:00 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.