crates.io: static.crates.io not resolving
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)
Swipe sideways to see the whole diagram.
Mermaid source
flowchart LR
root["Azure<br/>own incident not archived"]:::inferred
h1["Within an hour<br/>1 vendor, 1 blamed Azure<br/>MongoDB Atlas"]:::blames
root --> h1
h4["1 to 4 hours later<br/>3 vendors, 2 blamed Azure<br/>Grafana Cloud, Retool, InfluxData (InfluxDB Cloud)"]:::blames
root --> h4
me["crates.io (this incident)<br/>posted +2 h 40 min"]:::me
root -.->|"same window"| meFull event: timeline, evidence and all vendors →
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.
Affected components: crates.io
Timeline of updates
- identified
Due to an infrastructure change, the DNS record for static.crates.io, the CDN serving crate releases, stopped resolving. The new records are propagating, the problem should be fixed soon.
- monitoring
Traffic to static.crates.io is returning to normal levels and we're monitoring the situation.
- resolved
Traffic returned to normal levels.
Changes Rewindex caught on this incident
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.
First version captured 17:33 UTC
In the 2026-10-19 checkpoint, timestamped by FreeTSA and DigiCert on Oct 20, 00:41 UTC. Record hash
7d8964de3ef9ef35…
Impact, status and times are the vendor’s own, as last archived. View on stspg.io (opens in new tab).