- Level
- confirmed
- Worst impact
- Degraded
- Components
- crates.io
- Down Index
- 28of 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 5m it lasted.
Anything that failed between 2026-05-20 15:52 UTC and 2026-05-20 16:57 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
Crates.io is currently under a suspected denial of service effecting the web frontend. The reverse dependency endpoint has been disabled. You will not be able to browse reverse dependencies on crates.io for the duration of the incident. All other operations, publishes and the index are operating normally.
provider
- resolved
All endpoints are now operational and available again.
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-7892e8e97e
Is crates.io still down?
No, this incident was resolved 2026-05-20 16:57 UTC. For crates.io's live state, see https://down.guide/crates-io.
How long did it last?
1h 5m, from 2026-05-20 15:52 UTC to 2026-05-20 16:57 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.