Degraded performance on crates.io

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 1h 18m it lasted.

  Anything that failed between 2025-11-10 23:56 UTC and 2025-11-11 01:14 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

1. investigatingNov 10, 2025, 11:56 PM UTC

   crates.io is currently experiencing degraded performance on any requests that hit the database (which is basically anything in the API except crate downloads). We are investigating.

   provider

2. identifiedNov 11, 2025, 12:15 AM UTC

   The slowdown is definitely database related, and we are in contact with our upstream provider to see if we can track down what the root cause might be.

   provider

3. monitoringNov 11, 2025, 1:04 AM UTC

   The 2025 version of "it's always DNS" might be "it's always AI scrapers pretending to be other things". Our database provider pointed out an expensive endpoint that was being hit just enough by a single IP to cause the incident, but not enough for our normal monitoring setup to detect it. We have blocked that IP and response times appear to be returning to normal. Continuing to monitor for a few minutes, but this looks good at the moment.

   provider

4. resolvedNov 11, 2025, 1:14 AM UTC

   Everything continues to look stable, so we can consider this resolved.

   provider

Corrections

None so far.

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