- Level
- confirmed
- Worst impact
- Major outage
- Components
- crates.io
- Down Index
- 52of 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 2h 46m it lasted.
Anything that failed between 2023-12-27 14:24 UTC and 2023-12-27 17:11 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 4
- investigating
We are currently investigating this issue.
provider
- monitoring
Download traffic has been temporarily redirected and the system is recovering. We are monitoring the situation.
provider
- monitoring
Download traffic is being treated and counted regularly again. We are continuing to monitor for any further issues.
provider
- resolved
The incident has been resolved. Traffic and error rates are back to normal levels. The root cause has been identified and we are assessing solutions to avoid it from happening again in the future.
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-522844258c
Is crates.io still down?
No, this incident was resolved 2023-12-27 17:11 UTC. For crates.io's live state, see https://down.guide/crates-io.
How long did it last?
2h 46m, from 2023-12-27 14:24 UTC to 2023-12-27 17:11 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.