crates.io: crates.io failed to serve requests

What to do

Check whether your product depends on 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 2020-10-29 09:45 UTC and 2020-10-29 09:23 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.

resolvedOct 29, 2020, 9:23 AM UTC
On 2020-10-29 between 9:23 and 9:28 UTC, the crates.io application failed to serve requests due to a wrong configuration change. The team promptly noticed the fallout from the changed and rolled back the application to the previous version.
provider

Reports count in aggregate; nothing about you is shown.

None so far.

Something wrong on this page? Report an error or send us a note. Every fix is listed here.

Is crates.io still down?

No, this incident was resolved 2020-10-29 09:23 UTC. For crates.io's live state, see https://down.guide/crates-io.

How long did it last?

0m, from 2020-10-29 09:45 UTC to 2020-10-29 09:23 UTC, by the times crates.io posted.

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.