- Level
- confirmed
- Worst impact
- Degraded
- Components
- crates.io
- Down Index
- 31of 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 4h 8m it lasted.
Anything that failed between 2025-08-12 21:47 UTC and 2025-08-13 01:55 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 3
- identified
Due to a large number of crate versions being published in the last few hours, the legacy Git crate index is currently approximately 280 crate versions (or about two hours) behind. The sparse index (which has been the default since Rust 1.70, released in June 2023) is unaffected.
provider
- monitoring
The Git index sync job backlog is slowly burning down, and is anticipated to catch up in a few hours. We will continue to monitor the situation.
provider
- resolved
The Git index has caught up and is now up to date.
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-777890b008
Is crates.io still down?
No, this incident was resolved 2025-08-13 01:55 UTC. For crates.io's live state, see https://down.guide/crates-io.
How long did it last?
4h 8m, from 2025-08-12 21:47 UTC to 2025-08-13 01:55 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.