crates.io Outage History

crates.io is up right now

Pingoru has recorded 48 incidents for crates.io: 8 in the last 12 months and 0 in the last 90 days.

Source: status.crates.io

48incidents recorded
8last 12 months
0last 90 days
10 hourstypical duration
Incidents per month
012AprMayJunJulAugSepOct0
Share of hours with an open incident, any severity
0%50%100%AprMayJunJulAugSepOct0%
Pingoru began tracking crates.io in April 2026, so earlier months are not shown. Hover a bar for its value.
Show as a table
MonthIncidentsHours with an open incident
April 202613 of 720 (0%)
May 2026271 of 744 (10%)
June 202611 of 720 (0%)
July 202611 of 744 (0%)
August 202600 of 744 (0%)
September 202600 of 720 (0%)
October 202600 of 524 (0%)

Incidents, newest first

Major July 11, 2026 DoS Attack 1h 19m crates.io

Started Jul 11, 2026, 02:22 PM UTC· resolved Jul 11, 2026, 03:42 PM UTC

  1. investigating Jul 11, 2026, 02:22 PM UTC

    We are experience what looks like a coordinated DoS attack against our API servers. We are monitoring the situation and are assessing our reaction. Crate downloads and dependency resolution through the sparse/git index should not be affected.

  2. investigating Jul 11, 2026, 02:22 PM UTC

    We are continuing to investigate this issue.

  3. monitoring Jul 11, 2026, 03:06 PM UTC

    We have deployed countermeasures and our servers are largely back to normal again. We keep monitoring the situation. If you encounter any issues please let us know!

  4. resolved Jul 11, 2026, 03:42 PM UTC

    This incident has been resolved. Big thanks to Fastly for providing their CDN services and their fast response time!

Read the full incident report →

Minor June 14, 2026 crates.io slowness 33m crates.io

Started Jun 14, 2026, 01:20 AM UTC· resolved Jun 14, 2026, 01:53 AM UTC

  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.

Read the full incident report →

Minor May 23, 2026 Reverse dependency pages unavailable 2d 22h crates.io

Started May 23, 2026, 06:47 PM UTC· resolved May 26, 2026, 05:00 PM UTC

  1. identified May 23, 2026, 06:47 PM UTC

    The reverse dependencies pages are temporarily unavailable. Other crates.io functionality should continue to function normally.

  2. monitoring May 23, 2026, 07:19 PM UTC

    Reverse dependencies remain disabled, but the rest of crates.io is functioning normally.

  3. resolved May 26, 2026, 05:00 PM UTC

    This incident has been resolved.

Read the full incident report →

Notice May 20, 2026 Degraded performance on crates.io 1h 5m crates.io

Started May 20, 2026, 03:52 PM UTC· resolved May 20, 2026, 04:57 PM UTC

  1. monitoring May 20, 2026, 03:52 PM UTC

    Crates.io is currently affected by a suspected denial of service affecting the web frontend. The reverse dependency endpoint has been disabled. You will not be able to browse reverse dependencies on crates.io for the duration of the incident. All other operations, publishes and the index are operating normally.

  2. resolved May 20, 2026, 04:57 PM UTC

    All endpoints are now operational and available again.

Read the full incident report →

Minor April 14, 2026 Git index slow to update 2h 56m crates.io

Started Apr 14, 2026, 08:48 PM UTC· resolved Apr 14, 2026, 11:44 PM UTC

  1. investigating Apr 14, 2026, 08:48 PM UTC

    The crates.io background worker is having a bad morning, and a backlog of Git index updates has accumulated. We have given the worker some coffee and it's catching up, but index updates for newly-published crates are running about an hour behind right now. The sparse index (used by default by all modern Rust versions) is unaffected.

  2. monitoring Apr 14, 2026, 09:08 PM UTC

    The background worker has been told to get itself together. The queue is now trending downwards, but git index updates are still running an hour behind. We are continuing to monitor, but we expect this to resolve over the next few hours.

  3. resolved Apr 14, 2026, 11:44 PM UTC

    The indexes are now back to normal operations.

Read the full incident report →

Minor September 2, 2025 Sparse Index CDN Invalidations Slow to Update 44m crates.io

Started Sep 02, 2025, 10:48 PM UTC· resolved Sep 02, 2025, 11:33 PM UTC

  1. monitoring Sep 02, 2025, 10:48 PM UTC

    A backlog of CDN invalidations is causing a backlog of approximately 350 crate backlog for sparse index updates and CDN updates. We are monitoring as the queue is worked through.

  2. monitoring Sep 02, 2025, 11:08 PM UTC

    The sparse index has synchronized and is now up-to-date. CDN updates are still processing.

  3. monitoring Sep 02, 2025, 11:32 PM UTC

    The backlog has cleared and all queues are nominal.

  4. resolved Sep 02, 2025, 11:33 PM UTC

    This incident has been resolved.

Read the full incident report →

Major May 13, 2025 Crate indexes not updating 7m crates.io

Started May 13, 2025, 07:37 AM UTC· resolved May 13, 2025, 07:44 AM UTC

  1. investigating May 13, 2025, 07:37 AM UTC

    Since approximately 05:20 UTC, index entries in the Git and sparse crate indexes have not been published. We are investigating.

  2. identified May 13, 2025, 07:39 AM UTC

    Background workers have been restarted.

  3. monitoring May 13, 2025, 07:41 AM UTC

    Indexes are up to date, and we are monitoring the background workers to ensure they continue to pick up new jobs.

  4. resolved May 13, 2025, 07:44 AM UTC

    Crates published since the background workers were restarted are now appearing in the index, and the backlog of background jobs has been processed successfully.

Read the full incident report →