Maintenance: Emergency Network Maintenance for US-NC-2

What to do

• Check whether you use RunPod in us. 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-21 00:03 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. resolvedFeb 21, 2026, 12:03 AM UTC

   **Date & Time:** Saturday, February 21, 2026 at 21:30 UTC **Estimated Duration:** Up to 30 minutes **Affected Region:** US-NC-2 (North Carolina) **Summary:** RunPod's data center partner will be deploying a dedicated NAT Gateway for the US-NC-2 region to address network latency and packet processing issues. This upgrade is intended to improve long-term network stability and performance for all pods in this region. **Expected Impact:** Pods in US-NC-2 may experience intermittent network connectivity disruptions during the cutover window. Active connections — including SSH sessions, API calls, and data transfers — may be dropped and will need to re-establish. Pod compute resources will remain online; only network connectivity is affected. **Recommended Actions:** - Pause or checkpoint any network-sensitive workloads prior to 21:30 UTC on 2/21 if possible - Expect to re-establish SSH sessions or restart network-dependent processes after the maintenance window - Monitor your pods for connectivity restoration following the cutover

   provider

Corrections

None so far.

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