crates.io incident

Degraded performance on crates.io

Minor Resolved View vendor source →

crates.io experienced a minor incident on November 10, 2025 affecting crates.io, lasting 1h 17m. The incident has been resolved; the full update timeline is below.

Started
Nov 10, 2025, 11:56 PM UTC
Resolved
Nov 11, 2025, 01:14 AM UTC
Duration
1h 17m
Detected by Pingoru
Nov 10, 2025, 11:56 PM UTC

Affected components

crates.io

Update timeline

  1. investigating Nov 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.

  2. identified Nov 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.

  3. monitoring Nov 11, 2025, 01: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.

  4. resolved Nov 11, 2025, 01:14 AM UTC

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