crates.io incident

crates.io slowness

Resolved after 33 minutes, affecting crates.io, on June 14, 2026.

resolved Jun 14, 2026, 01:53 AM UTC

The primary source of the load appears to have been a scraper abusing our API. We have blocked the scraper and the replica database has returned to its normal heavily loaded state instead of being overloaded.

Started
Jun 14, 2026, 01:20 AM UTC
Resolved
Jun 14, 2026, 01:53 AM UTC
Duration
33m
Detected by Pingoru
Jun 14, 2026, 01:20 AM UTC

Affected components

crates.io

Update timeline

  1. investigating Jun 14, 2026, 01:20 AM UTC

    crates.io responses are unusually slow due to database issues, with occasional 500s due to database timeouts. We are investigating.

  2. identified Jun 14, 2026, 01:37 AM UTC

    The read-only replica database used for many of our common queries is under heavy load. We are evaluating options to deal with this.

  3. resolved Jun 14, 2026, 01:53 AM UTC

    The primary source of the load appears to have been a scraper abusing our API. We have blocked the scraper and the replica database has returned to its normal heavily loaded state instead of being overloaded.

Your product runs on more than crates.io

Add the vendors you depend on and get one message when any of them reports trouble. Free for 3 vendors, no card.

Add your stack →