ChangesRunPodCA-MTL-1 DC is Unavailable
RunPod: Incident silently edited: CA-MTL-1 DC is Unavailable
RunPod expanded its 10-31 20:30 UTC downtime update to include EU-SE-1 alongside CA-MTL-1. The vendor said it was working to resolve the issue; no cause, fix, impact level, start time, or duration was provided.
Machine-written from the diff below (Sol; type: incident edit). Check the diff before relying on it.
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 this record existed by then and has not been changed since, by anyone, Rewindex included.
How the archive is checked, and what it cannot prove.
Before captured
In the 2026-10-31 checkpoint, timestamped by FreeTSA and DigiCert on . Record hash
388fbabb2452e7f9…
Rewindex captured a newer version after the last checkpoint; the next run () commits it.
History of this incident
TodaySunday, November 1Sun, Nov 1
1 rewrite
- EditedEdited by the vendor
CA-MTL-1 DC is Unavailablethis change
RunPod expanded its 10-31 20:30 UTC downtime update to include EU-SE-1 alongside CA-MTL-1. The vendor said it was working to resolve the issue; no cause, fix, impact level, start time, or duration was provided.
YesterdaySaturday, October 31Sat, Oct 31
1 incident change
- OutageCritical incident
RunPod reported a critical outage affecting CA-MTL-1 starting at 2026-10-31 20:30 UTC, leaving the data center unavailable. The incident was still open when archived, with 0 minutes elapsed at the last update; RunPod said it was working to resolve the issue.