Changescrates.iostatic.crates.io not resolving
crates.io: Critical incident: static.crates.io not resolving
Summary pending. The diff below shows exactly what changed.
Incident page: the full timeline of updates
Azure outage, Jan 25, 2023 · 14 vendors, 14 incidents
crates.io’s incident started in the same window without naming Azure (timing only, not evidence of a link). (timing only, posted +2 h 40 min vs the first vendor naming Azure)
See the cascade chart and every vendor →
Detected automatically from incidents that started together and named the same provider. A link means one vendor’s incident named another, not a confirmed cause.
What changed
Struck in red is what crates.io removed; blue is what they added. Muted text is unchanged context.
First version of this incident archived by Rewindex. View the live incident (opens in new tab).
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.
How the archive is checked, and what it cannot prove.
Rewindex captured this after the last checkpoint; the next run (00:41 UTC) commits it.
This incident predates live tracking (October 17, 2026). It came from the vendor’s own published history, which is not covered by checkpoints.
History of this incident
Wednesday, January 25, 2023
1 incident change
- CriticalCritical incident
static.crates.io not resolvingthis change