- Level
- confirmed
- Worst impact
- Partial outage
- Components
- docs.rs
- Down Index
- 37of 100
What to do
Check whether you use crates.io docs.rs. 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 44m it lasted.
Anything that failed between 2020-06-06 10:51 UTC and 2020-06-06 11:35 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 4
- investigating
docs.rs is failing to build new releases, and we're investigating the problem.
provider
- identified
We have identified a possible cause of the issue and we're working on a fix.
provider
- monitoring
We have deployed a fix and we're monitoring recovery.
provider
- resolved
We confirmed the fix worked and we re-enabled builds. Build delays will be experienced for the next few hours as the server works through the backlog. The build queue is available at https://docs.rs/releases/queue.
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-10d5784306
Is crates.io still down?
No, this incident was resolved 2020-06-06 11:35 UTC. For crates.io's live state, see https://down.guide/crates-io.
How long did it last?
44m, from 2020-06-06 10:51 UTC to 2020-06-06 11:35 UTC, by the times crates.io posted.
What was affected?
crates.io named docs.rs.
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.