Skip to main content
crates.io

Degraded performance

Degraded Lasted 42m · started · crates.io's page

Level
confirmed
Worst impact
Degraded
Components
crates.io
Down Index
27of 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 42m it lasted.

    Anything that failed between 2019-08-18 13:13 UTC and 2019-08-18 13:55 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

  1. investigating

    We are currently seeing degraded performance across all endpoints on crates.io

    provider

  2. monitoring

    A fix has been implemented and we are monitoring the results.

    provider

  3. resolved

    This incident has been 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-5e05f2ca13

Is crates.io still down?

No, this incident was resolved 2019-08-18 13:55 UTC. For crates.io's live state, see https://down.guide/crates-io.

How long did it last?

42m, from 2019-08-18 13:13 UTC to 2019-08-18 13:55 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.