Skip to main content
RunPod

Maintenance: Planned Network Hardware Capacity Upgrade in AP-IN-1

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-07-01 13: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

    Planned Network Hardware Capacity Upgrade in AP-IN-1 Expected Downtime: Brief service interruptions or network fluctuations. Details: During the upcoming network upgrade, you may experience temporary network fluctuations caused by minor packet drops (approximately 3 to 4 packets). Full service will normalize immediately upon the successful completion of the maintenance. Please be assured that all configurations and data stored on your infrastructure will remain completely safe and unaffected throughout this process.

    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-5b9c9dac9e

Is this RunPod maintenance still going on?

No, it ended 2026-07-01 13:06 UTC.

How long did it last?

0m, from 2026-07-01 13:06 UTC to 2026-07-01 13: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.