Changescrates.ioIncreased errors while connecting to crates.io
crates.io: Major incident: Increased errors while connecting to crates.io
Summary pending. The diff below shows exactly what changed.
Incident page: the full timeline of updates
Heroku outage, Mar 16, 2020 · 8 vendors, 9 incidents
crates.io’s incident blames Heroku as the cause. (hop 1, posted +30 min vs the first vendor naming Heroku)
“…crates.io. We're continuing to monitor the situation, and you can follow the progress on Heroku's status page: https://status.heroku.com/incidents/1973 This incident has been resolved.…”
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
Monday, March 16, 2020
1 incident change
- MajorMajor incident
Increased errors while connecting to crates.iothis change