crates.io experienced a major incident on February 14, 2024 affecting crates.io, lasting 7h 13m. The incident has been resolved; the full update timeline is below.
Affected components
Update timeline
- investigating Feb 14, 2024, 07:30 PM UTC
Some crates.io endpoints are timing out at present, including the summary route that drives the crates.io home page. We are investigating.
- investigating Feb 14, 2024, 07:30 PM UTC
(If this looks suspiciously similar to https://status.crates.io/incidents/t49v2pfpv0vl, the same issue reappeared on the summary endpoint literally within seconds of resolving that incident. C'est la vie.)
- identified Feb 14, 2024, 10:13 PM UTC
We believe this issue is being caused by excess database load related to a bug fix deployed earlier today around download counting. This bug fix has caused the normal background processing of per-crate download count totals to take significantly longer and require more resources than usual. We will shortly be temporarily disabling the summary endpoint to alleviate some of the load on the database.
- monitoring Feb 15, 2024, 12:12 AM UTC
The long running background job has completed, and response times for the summary endpoint have returned to normal. The next invocation of the relevant background job will be at 00:30 UTC (so in just under 20 minutes); we will be monitoring that closely to see if any problems resurface at that point.
- monitoring Feb 15, 2024, 12:12 AM UTC
We are continuing to monitor for any further issues.
- resolved Feb 15, 2024, 02:43 AM UTC
crates.io has returned to normal service with the processing of the download count backlog from earlier and the completion of the long running background jobs. Investigations will continue during normal hours for the crates.io team to ascertain what is causing elevated database load.