- Level
- confirmed
- Worst impact
- Major outage
- Components
- crates.io
- Down Index
- 48of 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 38m it lasted.
Anything that failed between 2023-01-25 09:40 UTC and 2023-01-25 10:18 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 an infrastructure change, the DNS record for static.crates.io, the CDN serving crate releases, stopped resolving. The new records are propagating, the problem should be fixed soon.
provider
- monitoring
Traffic to static.crates.io is returning to normal levels and we're monitoring the situation.
provider
- resolved
Traffic returned to normal levels.
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-713278c63d
Is crates.io still down?
No, this incident was resolved 2023-01-25 10:18 UTC. For crates.io's live state, see https://down.guide/crates-io.
How long did it last?
38m, from 2023-01-25 09:40 UTC to 2023-01-25 10:18 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.