crates.io: Increased errors while connecting to crates.io
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.…”
Swipe sideways to see the whole diagram.
Mermaid source
flowchart LR
root["Heroku<br/>own incident not archived"]:::inferred
h1["Within an hour<br/>4 vendors, 4 blamed Heroku<br/>RevenueCat, Substack, Bitrise, crates.io"]:::blames
root --> h1
h4["1 to 4 hours later<br/>1 vendor, 1 blamed Heroku<br/>RevenueCat"]:::blames
root --> h4
me["crates.io (this incident)<br/>posted +30 min"]:::me
h1 --- 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
- monitoring
Due to a outage affecting our infrastructure provider, in the past hour we experienced an increased number of errors while connecting to 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
- resolved
This incident has been resolved.
Changes Rewindex caught on this incident
Impact, status and times are the vendor’s own, as last archived. View on stspg.io (opens in new tab).