- Level
- confirmed
- Worst impact
- Partial outage
- Components
- crates.io
- Down Index
- 39of 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 1h 59m it lasted.
Anything that failed between 2023-07-20 12:17 UTC and 2023-07-20 14:15 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
After a deployment we noticed an elevated number of download requests, that were caused by crates.io generating broken download URLs and cargo retrying those downloads again and again. We have rolled back the deployment to fix the issue in production. The bug is already identified and we are working on a long-term fix.
provider
- resolved
The bugfix has been merged and deployed to production. We have adjusted our test suite to reduce the chances of this issue appearing 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-912100dcf6
Is crates.io still down?
No, this incident was resolved 2023-07-20 14:15 UTC. For crates.io's live state, see https://down.guide/crates-io.
How long did it last?
1h 59m, from 2023-07-20 12:17 UTC to 2023-07-20 14:15 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.