- Level
- confirmed
- Worst impact
- Degraded
- Components
- crates.io
- Down Index
- 18of 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 0m it lasted.
Anything that failed between 2019-07-22 16:29 UTC and 2019-07-22 16:29 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 1
- resolved
Crates published to crates.io may experience a delay in appearing in the crates.io index, due to an ongoing issue with GitHub. This means that your crate may appear on crates.io, but cannot yet be used in Cargo.toml. If your crate is affected, it will automatically be published to the index as soon as we are able to. No further action is required from you. You can follow https://www.githubstatus.com/incidents/8x69vj1xyp9v for updates on the underlying incident.
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-8bce1f7336
Is crates.io still down?
No, this incident was resolved 2019-07-22 16:29 UTC. For crates.io's live state, see https://down.guide/crates-io.
How long did it last?
0m, from 2019-07-22 16:29 UTC to 2019-07-22 16:29 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.