ChangesRunPodPlanned Server relocation
RunPod: Incident updated: Planned Server relocation
Summary pending. The diff below shows exactly what changed.
Incident page: the full timeline of updates
What changed
Struck in red is what RunPod removed; blue is what they added. Muted text is unchanged context.
Compared with the previous archived version of this incident (10 to 30-minute polling).
Archive proof
Rewindex commits each version of an incident it captures to a daily checkpoint, chains it to the day before, and has the checkpoint timestamped by FreeTSA and DigiCert. That proves these records existed by then and have not been changed since, by anyone, Rewindex included.
How the archive is checked, and what it cannot prove.
Before captured
In the 2026-11-06 checkpoint, timestamped by FreeTSA and DigiCert on . Record hash
c72a657c5385367e…After captured
In the 2026-11-06 checkpoint, timestamped by FreeTSA and DigiCert on . Record hash
818a4cad8900e150…
History of this incident
Friday, November 6
1 rewrite, 2 incident changes
- Normal progressIncident
Incident updatePlanned Server relocationthis change
- Normal progressEdited by the vendor
RunPod reopened the planned US-IL-1 server relocation maintenance from resolved to in progress and removed the “Maintenance ended” update. Maintenance began November 6, 2026 at 11:00 UTC, originally scheduled through 15:00 UTC, and remained open when archived at 20:43 UTC. Its data center partner reported the relocation was taking longer than planned, extending downtime for affected customers.
- Normal progressIncident
Incident updatePlanned Server relocation
Cite this
Incident updated: Planned Server relocation on RunPod’s status page, changed 2026-11-06 23:03 UTC (change 3 of 3).
- Title
- Incident updated: Planned Server relocation
- Vendor
- RunPod
- Date
- URL
- https://rewindex.com/change/rdbc8dd00923ad5