crates.io: Degraded performance on crates.io
Affected components: crates.io
Timeline of updates
- investigating
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.
- identified
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.
- monitoring
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.
- resolved
Everything continues to look stable, so we can consider this resolved.
Archive proof
Rewindex commits each version of an incident it captures to a daily checkpoint, chains it to the day before, and has the checkpoint timestamped by FreeTSA and DigiCert. That proves this record existed by then and has not been changed since, by anyone, Rewindex included.
How the archive is checked, and what it cannot prove.
First version captured 17:33 UTC
In the 2026-10-19 checkpoint, timestamped by FreeTSA and DigiCert on Oct 20, 00:41 UTC. Record hash
76d4ddbe063726c3…
Impact, status and times are the vendor’s own, as last archived. View on stspg.io (opens in new tab).