- Level
- confirmed
- Worst impact
- Partial outage
- Components
- crates.io
- Down Index
- 34of 100
What to do
Check whether you use crates.io crates.io. Check your stack
Paste a package.json, lockfile, Terraform or a list of domains at down.guide/stack to see every provider you depend on.Confirm your retries, queues and scheduled jobs caught up after the 13m it lasted.
Anything that failed between 2020-03-16 16:53 UTC and 2020-03-16 17:06 UTC may need a replay.Subscribe to crates.io's feed to hear about the next one first. RSS feed
https://down.guide/feed?provider=crates-io works in Slack (/feed subscribe), Discord feed bots and any RSS reader.
Updates from crates.io 2
- 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
provider
- resolved
This incident has been resolved.
provider
Reports count in aggregate; nothing about you is shown.
Corrections
None so far.
Something wrong on this page? Report an error or send us a note. Every fix is listed here.
Questions about DWN-d39976f36f
Is crates.io still down?
No, this incident was resolved 2020-03-16 17:06 UTC. For crates.io's live state, see https://down.guide/crates-io.
How long did it last?
13m, from 2020-03-16 16:53 UTC to 2020-03-16 17:06 UTC, by the times crates.io posted.
What was affected?
crates.io named crates.io.
What caused it?
crates.io hasn't published a root cause. If it does, it shows here.
Where does this come from?
crates.io's official status page, https://status.crates.io, quoted verbatim. down.guide's own probes, reports and social counts are labeled as ours.