- Level
- confirmed
- Worst impact
- Partial outage
- Components
- crates.io
- Down Index
- 33of 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 7m it lasted.
Anything that failed between 2025-05-13 07:37 UTC and 2025-05-13 07:44 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
Since approximately 05:20 UTC, index entries in the Git and sparse crate indexes have not been published. We are investigating.
provider
- identified
Background workers have been restarted.
provider
- monitoring
Indexes are up to date, and we are monitoring the background workers to ensure they continue to pick up new jobs.
provider
- resolved
Crates published since the background workers were restarted are now appearing in the index, and the backlog of background jobs has been processed successfully.
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-c1847a6863
Is crates.io still down?
No, this incident was resolved 2025-05-13 07:44 UTC. For crates.io's live state, see https://down.guide/crates-io.
How long did it last?
7m, from 2025-05-13 07:37 UTC to 2025-05-13 07:44 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.