- 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 39m it lasted.
Anything that failed between 2022-12-05 21:06 UTC and 2022-12-05 21:45 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
We're investigating a high number of jobs in our background worker queue, slowing down crate uploads.
provider
- identified
We have identified the root cause and applied measures to reduce the length of the background job queue.
provider
- resolved
All pending background jobs have been executed, and the queue is back to a normal state. This incident is now resolved.
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-39c55d4d4c
Is crates.io still down?
No, this incident was resolved 2022-12-05 21:45 UTC. For crates.io's live state, see https://down.guide/crates-io.
How long did it last?
39m, from 2022-12-05 21:06 UTC to 2022-12-05 21:45 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.