- Level
- confirmed
- Worst impact
- Degraded
- Components
- crates.io
- Down Index
- 26of 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 33m it lasted.
Anything that failed between 2026-06-14 01:20 UTC and 2026-06-14 01:53 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
- investigating
crates.io responses are unusually slow due to database issues, with occasional 500s due to database timeouts. We are investigating.
provider
- identified
The read-only replica database used for many of our common queries is under heavy load. We are evaluating options to deal with this.
provider
- resolved
The primary source of the load appears to have been a scraper abusing our API. We have blocked the scraper and the replica database has returned to its normal heavily loaded state instead of being overloaded.
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-ffaaedd48e
Is crates.io still down?
No, this incident was resolved 2026-06-14 01:53 UTC. For crates.io's live state, see https://down.guide/crates-io.
How long did it last?
33m, from 2026-06-14 01:20 UTC to 2026-06-14 01:53 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.