crates.io

Affected: crates.io

Failure mode: Traffic surge or denial-of-service attack. Root cause: An external attack. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. investigating 2026-07-11 14:22 UTC

   We are experiencing 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 2026-07-11 14:22 UTC

   We are continuing to investigate this issue.

3. monitoring 2026-07-11 15:06 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 2026-07-11 15:42 UTC

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

Excerpts are shortened. Read the full incident on crates.io's status page.

Affected: crates.io

Failure mode: Traffic surge or denial-of-service attack. Root cause: An external attack. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-06-14 01:20 UTC

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

2. identified 2026-06-14 01:37 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 2026-06-14 01:53 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.

Excerpts are shortened. Read the full incident on crates.io's status page.

Affected: crates.io

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. identified 2026-05-23 18:47 UTC

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

2. monitoring 2026-05-23 19:19 UTC

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

3. resolved 2026-05-26 17:00 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on crates.io's status page.

Affected: crates.io

Failure mode: Traffic surge or denial-of-service attack. Root cause: An external attack. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. monitoring 2026-05-20 15:52 UTC

   Crates.io is currently under a suspected denial of service effecting 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...

2. resolved 2026-05-20 16:57 UTC

   All endpoints are now operational and available again.

Excerpts are shortened. Read the full incident on crates.io's status page.

Affected: crates.io

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-04-14 20:48 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...

2. monitoring 2026-04-14 21:08 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 2026-04-14 23:44 UTC

   The indexes are now back to normal operations.

Excerpts are shortened. Read the full incident on crates.io's status page.

Affected: crates.io

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. identified 2026-02-12 19:36 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...

2. resolved 2026-02-12 19:46 UTC

   The background worker has caught up, and crate publishes are now updating normally in both indexes.

Excerpts are shortened. Read the full incident on crates.io's status page.

Affected: crates.io

Failure mode: Traffic surge or denial-of-service attack. Root cause: An external attack. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2025-11-10 23:56 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 2025-11-11 00:15 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 2025-11-11 01:04 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...

4. resolved 2025-11-11 01:14 UTC

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

Excerpts are shortened. Read the full incident on crates.io's status page.

Affected: crates.io

Failure mode: Traffic surge or denial-of-service attack. Root cause: Not enough capacity for the load. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. monitoring 2025-11-01 03:15 UTC

   Due to a large number of crate versions being published in the last few hours, the legacy Git crate index is currently approximately 245 crate versions (or about two hours) behind. The sparse index (which has been the default since Rust 1.70, released in June 2023) is unaffected.

2. monitoring 2025-11-01 04:04 UTC

   The queue burndown has slowed due to an unusual number of crate publishes in the last hour, but it is slowly making progress and is now at 206 pending syncs. It could be anywhere from 2-4 hours from here until it catches up.

3. monitoring 2025-11-01 05:01 UTC

   Now at 116 pending syncs. Probably 1½ hours before we're caught up, give or take.

4. monitoring 2025-11-01 06:01 UTC

   57 pending syncs.

5. resolved 2025-11-01 06:38 UTC

   All published crates have been synced to the Git index, and there is now no backlog.

Excerpts are shortened. Read the full incident on crates.io's status page.

Affected: crates.io

Failure mode: CDN or edge layer failed or served bad content. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. monitoring 2025-09-02 22:48 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 2025-09-02 23:08 UTC

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

3. monitoring 2025-09-02 23:32 UTC

   The backlog has cleared and all queues are nominal.

4. resolved 2025-09-02 23:33 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on crates.io's status page.

Affected: crates.io

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: Not enough capacity for the load. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. identified 2025-08-12 21:47 UTC

   Due to a large number of crate versions being published in the last few hours, the legacy Git crate index is currently approximately 280 crate versions (or about two hours) behind. The sparse index (which has been the default since Rust 1.70, released in June 2023) is unaffected.

2. monitoring 2025-08-12 22:21 UTC

   The Git index sync job backlog is slowly burning down, and is anticipated to catch up in a few hours. We will continue to monitor the situation.

3. resolved 2025-08-13 01:55 UTC

   The Git index has caught up and is now up to date.

Excerpts are shortened. Read the full incident on crates.io's status page.

Affected: crates.io

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2025-05-13 07:37 UTC

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

2. identified 2025-05-13 07:39 UTC

   Background workers have been restarted.

3. monitoring 2025-05-13 07:41 UTC

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

4. resolved 2025-05-13 07:44 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.

Excerpts are shortened. Read the full incident on crates.io's status page.

Affected: crates.io

Failure mode: A schema or data migration caused the failure. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. identified 2024-05-20 11:17 UTC

   We are in the process of upgrading our database servers. This will require a short amount of time in read-only mode and a couple of minutes with degraded performance while our follower database is catching up with the new leader.

2. monitoring 2024-05-20 12:14 UTC

   We noticed a small issue with our database indexes after the upgrade, resulting in several crates not being found anymore. We've reindexed the relevant tables which appears to have fixed the problem. The new follower database is catching up an will soon be available to improve...

3. monitoring 2024-05-20 12:26 UTC

   Database server upgrade is complete and crates.io should be running at full capacity again now. Hopefully even a bit faster than before due to increased memory on the new database servers.

4. resolved 2024-05-20 12:26 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on crates.io's status page.

Affected: crates.io

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2024-03-22 13:04 UTC

   We are investigating the crates.io API and website being unreachable. Crate downloads should not be affected.

2. monitoring 2024-03-22 13:16 UTC

   The application is recovering, but we are still investigating trying to find the root cause. The incident seems to be unrelated to the one earlier today.

3. resolved 2024-03-22 13:25 UTC

   The application is stable, marking the incident as resolved. We will continue investigating the root cause of this.

Excerpts are shortened. Read the full incident on crates.io's status page.

Affected: crates.io

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2024-03-22 07:11 UTC

   We are investigating the crates.io website and API being unavailable. Downloads from recent Cargo versions should be working, but older Cargo releases relying on the crates.io API are affected.

2. monitoring 2024-03-22 07:26 UTC

   We have identified a problem with our read-only database replica and routed traffic away from it. We are monitoring the recovery, and we will continue investigating the cause of the problem.

3. monitoring 2024-03-22 07:48 UTC

   Since the last update, crates.io fully recovered and we are serving traffic as usual. We're continuing to monitor the situation and we'll re-enable the read-only replica again soon.

4. resolved 2024-03-22 07:56 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on crates.io's status page.

Affected: crates.io

Failure mode: A configuration change caused the failure. Root cause: A human mistake during operations. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. identified 2024-03-14 13:17 UTC

   The crates.io team will perform a database maintenance on 2024-03-15 from 12:00 to 12:15 UTC. We expect this to take less than 15 minutes to complete. During maintenance, crates.io will only be available in read-only mode: downloading crates and visiting the website will still...

2. identified 2024-03-15 12:00 UTC

   Scheduled maintenance on our database is starting. We expect this to take less than 15 minutes to complete. During maintenance, crates.io will only be available in read-only mode: downloading crates and visiting the website will still work, but logging in, publishing crates,...

3. resolved 2024-03-15 12:11 UTC

   Scheduled maintenance finished successfully.

Excerpts are shortened. Read the full incident on crates.io's status page.

Affected: crates.io

Failure mode: A code release introduced the failure. Root cause: A bug in the vendor's own code. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2024-02-14 19:30 UTC

   Some crates.io endpoints are timing out at present, including the summary route that drives the crates.io home page. We are investigating.

2. investigating 2024-02-14 19:30 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.)

3. identified 2024-02-14 22:13 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...

4. monitoring 2024-02-15 00:12 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...

5. monitoring 2024-02-15 00:12 UTC

   We are continuing to monitor for any further issues.

6. resolved 2024-02-15 02:43 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...

Excerpts are shortened. Read the full incident on crates.io's status page.

Affected: crates.io

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2024-02-14 18:45 UTC

   Some crates.io endpoints are timing out at present, including the summary route that drives the crates.io home page. We are investigating. Crate downloads are unaffected.

2. monitoring 2024-02-14 18:50 UTC

   Restarting the dynos has restored service, but we are still investigating the root cause of the issue, and continue to monitor crates.io performance.

3. resolved 2024-02-14 19:25 UTC

   crates.io continues to operate normally, and no further performance degradation or timeouts have been observed.

Excerpts are shortened. Read the full incident on crates.io's status page.

Affected: crates.io

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2023-12-27 14:24 UTC

   We are currently investigating this issue.

2. monitoring 2023-12-27 14:37 UTC

   Download traffic has been temporarily redirected and the system is recovering. We are monitoring the situation.

3. monitoring 2023-12-27 15:45 UTC

   Download traffic is being treated and counted regularly again. We are continuing to monitor for any further issues.

4. resolved 2023-12-27 17:11 UTC

   The incident has been resolved. Traffic and error rates are back to normal levels. The root cause has been identified and we are assessing solutions to avoid it from happening again in the future.

Excerpts are shortened. Read the full incident on crates.io's status page.

Affected: crates.io

Failure mode: A schema or data migration caused the failure. Root cause: A human mistake during operations. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2023-12-20 14:31 UTC

   The crates.io team will perform a database maintenance on 2023-12-21 from 11:00 to 11:15 UTC. We expect this to take less than 15 minutes to complete. During maintenance, crates.io will only be available in read-only mode: downloading crates and visiting the website will still...

2. investigating 2023-12-21 10:59 UTC

   Scheduled maintenance on our database is starting. We expect this to take less than 15 minutes to complete. During maintenance crates.io will only be available in read-only mode: downloading crates and visiting the website will still work, but logging in, publishing crates,...

3. resolved 2023-12-21 11:13 UTC

   Scheduled maintenance finished successfully.

Excerpts are shortened. Read the full incident on crates.io's status page.

Failure mode: A code release introduced the failure. Root cause: A bug in the vendor's own code. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. resolved 2023-11-16 07:00 UTC

   At 19:04 UTC a faulty deployment caused the crates.io API to not be reachable anymore. We immediately initiated a rollback to the previous deployment and the issue was resolved at 19:06 UTC. We are currently in the process of figuring out the root cause.

Excerpts are shortened. Read the full incident on crates.io's status page.

Affected: crates.io

Failure mode: Traffic surge or denial-of-service attack. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2023-10-18 19:03 UTC

   We have been seeing an elevated level of failing requests due to response timeouts over the past couple of minutes. This appears to be caused by a significantly increased level of traffic towards our API servers. We are investigating the root cause and will enable appropriate...

2. monitoring 2023-10-18 19:06 UTC

   The traffic levels have returned to regular levels at this point. We will continue to monitor the situation.

3. resolved 2023-10-19 06:45 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on crates.io's status page.

Affected: crates.io

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. identified 2023-07-21 09:28 UTC

   We're seeing crate publishes being reflected in the sparse index with a large delay, since 07:30:00 UTC. We have identified the root cause of the problem (the crates.io application being rate limited by a third party service due to a large volume of yanks), and we're working to...

2. resolved 2023-07-21 09:48 UTC

   The backlog of updates to the sparse index has been processed.

Excerpts are shortened. Read the full incident on crates.io's status page.

Affected: crates.io

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. identified 2023-07-21 02:45 UTC

   We're seeing crate publishes being reflected in the sparse index with a large delay, since 01:05:00 UTC. We have identified the root cause of the problem (the crates.io application being rate limited by a third party service due to a large volume of yanks), and we're working to...

2. resolved 2023-07-21 03:06 UTC

   The backlog of updates to the sparse index has been processed.

Excerpts are shortened. Read the full incident on crates.io's status page.

Affected: crates.io

Failure mode: A code release introduced the failure. Root cause: A bug in the vendor's own code. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. monitoring 2023-07-20 12:17 UTC

   After a deployment we noticed an elevated number of download requests, that were caused by crates.io generating broken download URLs and cargo retrying those downloads again and again. We have rolled back the deployment to fix the issue in production. The bug is already...

2. resolved 2023-07-20 14:15 UTC

   The bugfix has been merged and deployed to production. We have adjusted our test suite to reduce the chances of this issue appearing again in the future.

Excerpts are shortened. Read the full incident on crates.io's status page.

Affected: crates.io

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2023-04-15 06:16 UTC

   We're experiencing an elevated level of API errors and are currently looking into the issue. This leads to the "Browse All Crates" feature on the crates.io to be broken.

2. resolved 2023-04-15 06:34 UTC

   The crates.io API is back to normal.

Excerpts are shortened. Read the full incident on crates.io's status page.

Affected: crates.io

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2023-02-08 16:34 UTC

   We're investigating crates.io taking more time than usual to respond to requests.

2. resolved 2023-02-08 16:50 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on crates.io's status page.

Affected: crates.io

Failure mode: Network, DNS, routing or connectivity failure. Root cause: A human mistake during operations. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. identified 2023-01-25 09:40 UTC

   Due to an infrastructure change, the DNS record for static.crates.io, the CDN serving crate releases, stopped resolving. The new records are propagating, the problem should be fixed soon.

2. monitoring 2023-01-25 09:58 UTC

   Traffic to static.crates.io is returning to normal levels and we're monitoring the situation.

3. resolved 2023-01-25 10:18 UTC

   Traffic returned to normal levels.

Excerpts are shortened. Read the full incident on crates.io's status page.

Failure mode: A code release introduced the failure. Root cause: A configuration change. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. resolved 2023-01-23 10:00 UTC

   Due to an upgrade earlier today, background updates started failing. Crates published since 10:00 UTC have not been added to the index yet but remain in the queue. We have reverted the change and restarted the workers. We will continue to monitor the situation.

Excerpts are shortened. Read the full incident on crates.io's status page.

Affected: crates.io

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. monitoring 2023-01-13 13:45 UTC

   We are seeing reports of index updates taking a long time right now due to changes in the index. See https://github.com/rust-lang/cargo/issues/11014 for workarounds to speed up the process. Sorry for the inconvenience!

2. resolved 2023-02-02 11:13 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on crates.io's status page.

Affected: crates.io

Failure mode: Exhausted memory, disk, CPU, queues, connection pools or quotas. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2022-12-05 21:06 UTC

   We're investigating a high number of jobs in our background worker queue, slowing down crate uploads.

2. identified 2022-12-05 21:37 UTC

   We have identified the root cause and applied measures to reduce the length of the background job queue.

3. resolved 2022-12-05 21:45 UTC

   All pending background jobs have been executed, and the queue is back to a normal state. This incident is now resolved.

Excerpts are shortened. Read the full incident on crates.io's status page.

Affected: crates.io

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

Names an upstream provider: GitHub.

1. investigating 2022-03-17 15:24 UTC

   Crate publishes might be delayed due to the current GitHub outage. We're sorry for the disruption.

2. investigating 2022-03-17 15:27 UTC

   We are continuing to investigate this issue.

3. resolved 2022-03-17 16:30 UTC

   The incident has been resolved.

Excerpts are shortened. Read the full incident on crates.io's status page.

Affected: crates.io

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. investigating 2022-02-24 16:54 UTC

   We're investigating crates.io being unreachable.

2. identified 2022-02-24 17:06 UTC

   Due to an issue to our infrastructure provider, fully resolving the crates.io outage will take longer than expected, so we're executing our disaster recovery plan. We apologize for the disruption this is causing. Ensuring builds with Cargo keep working is our highest priority,...

3. monitoring 2022-02-24 17:22 UTC

   We're seeing traffic coming back to the crates.io application. We're monitoring the recovery, and we'll revert the emergency registry configuration change once we have confirmation the situation is fully resolved.

4. resolved 2022-02-24 17:37 UTC

   The situation has been stable for the past 20 minutes. We reverted the emergency change to the configuration of the registry index, and we're marking this incident as resolved. We're sorry for the disruption.

Excerpts are shortened. Read the full incident on crates.io's status page.

Affected: crates.io

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. investigating 2021-12-22 12:27 UTC

   We are currently investigating an incident that causes slow responses and request timeouts on crates.io.

2. investigating 2021-12-22 12:37 UTC

   We are continuing to investigate this issue.

3. monitoring 2021-12-22 13:02 UTC

   An outage of one of our service providers impacts our primary database and one of our application dynos. Currently, write operations will fail (uploading new crates, ...) and downloads will not be counted. About 25% of all download requests hit the affected dyno and will fail...

4. monitoring 2021-12-22 14:39 UTC

   Our service provider is still working to restore full functionality, but unfortunately there is no ETA for full recovery at this time. We continue to monitor the situation.

5. resolved 2021-12-22 15:07 UTC

   All of our affected infrastructure has recovered and full functionality has been restored. Some caches may require a bit of warming up, so some slow responses should still be expected.

Excerpts are shortened. Read the full incident on crates.io's status page.

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. monitoring 2021-07-07 16:59 UTC

   We are receiving reports of intermittent issues with the Rust website (www.rust-lang.org). We believe this is due to an on-going issue with our infrastructure provider. We're monitoring the situation.

2. resolved 2021-07-07 18:00 UTC

   The incident has been resolved.

Excerpts are shortened. Read the full incident on crates.io's status page.

Affected: crates.io

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2021-04-25 09:52 UTC

   We're investigating crates.io being unreachable.

2. monitoring 2021-04-25 09:56 UTC

   Crates.io is starting to recover and requests are being processed again.

3. resolved 2021-04-25 10:02 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on crates.io's status page.

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. resolved 2021-04-18 19:50 UTC

   The primary database for crates.io was unavailable for about 10 minutes, causing all API and download requests to timeout. Service has been restored and is being monitored.

Excerpts are shortened. Read the full incident on crates.io's status page.

Affected: crates.io

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: Hardware or facility. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. identified 2021-03-24 09:08 UTC

   We're investigating an issue with crates.io being unreachable.

2. identified 2021-03-24 09:17 UTC

   One of our database servers is experiencing problems, and that's preventing the crates.io application from starting back up. No data loss happened. We're working on a fix.

3. monitoring 2021-03-24 09:23 UTC

   The problems on the database servers are fixed. The application has been restarted and we're monitoring the recovery.

4. resolved 2021-03-24 09:28 UTC

   The incident has been resolved!

Excerpts are shortened. Read the full incident on crates.io's status page.

Failure mode: A configuration change caused the failure. Root cause: A configuration change. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. resolved 2020-10-29 09:23 UTC

   On 2020-10-29 between 9:23 and 9:28 UTC, the crates.io application failed to serve requests due to a wrong configuration change. The team promptly noticed the fallout from the changed and rolled back the application to the previous version.

Excerpts are shortened. Read the full incident on crates.io's status page.

Affected: crates.io

Failure mode: CDN or edge layer failed or served bad content. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. investigating 2020-09-11 00:37 UTC

   We received reports that Cargo is failing to download packages from static.crates.io, with the error message "failed to get 200 response from URL, got 206". Our understanding is that this is affecting just a few geographical regions in of US, and that this is an issue with our...

2. investigating 2020-09-11 10:06 UTC

   The situation is slowly improving, as over the past 6 hours only 14 requests were affected by the issue according to our logs, across the US and Asia. We're continuing to monitor the situation, and we're in contact with our CDN provider to get it fixed permanently.

3. monitoring 2020-09-11 14:16 UTC

   There are no more invalid responses showing up in our CDN logs for the past 3 hours. We'll continue to monitor the situation and work with our CDN provider to make sure the issue is permanently addressed.

4. monitoring 2020-09-11 23:26 UTC

   In the past 12 hours no invalid response was sent from our CDN, according to our response logs. We're continuing to monitor the issue, and our CDN provider is rolling out a permanent fix to the problem.

5. monitoring 2020-09-13 13:47 UTC

   In the past 26 hours no invalid response was sent from our CDN, according to our response logs. We're continuing to monitor the issue, and our CDN provider is rolling out a permanent fix to the problem.

6. resolved 2020-09-15 21:11 UTC

   Since our last update no invalid response was sent from our CDN, according to our response logs. We're marking this incident as resolved, and we're working with our CDN provider to avoid similar problems in the future.

Excerpts are shortened. Read the full incident on crates.io's status page.

Affected: docs.rs

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. identified 2020-06-15 18:10 UTC

   We're aware of a docs.rs outage, and we're working on a fix.

2. monitoring 2020-06-15 18:34 UTC

   We mitigated the outage and we're monitoring recovery. We will deploy a permanent fix after the service fully recovered.

3. resolved 2020-06-15 18:48 UTC

   We deployed a permanent fix for the outage.

Excerpts are shortened. Read the full incident on crates.io's status page.

Affected: crates.io

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. investigating 2020-06-12 18:59 UTC

   We are aware of an issue preventing users from accessing crates.io directly or through its API

2. identified 2020-06-12 19:06 UTC

   The issue appears to be caused by an outage in Cloudfront.

3. monitoring 2020-06-12 19:08 UTC

   A fix has been implemented and we are monitoring the results.

4. resolved 2020-06-12 19:21 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on crates.io's status page.

Affected: docs.rs

Failure mode: Network, DNS, routing or connectivity failure. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2020-06-12 12:41 UTC

   We're aware of connectivity problems with docs.rs, and we're working on a fix.

2. monitoring 2020-06-12 13:04 UTC

   docs.rs is up again, and we're monitoring its recovery.

3. resolved 2020-06-12 13:17 UTC

   The incident is now resolved.

Excerpts are shortened. Read the full incident on crates.io's status page.

Affected: docs.rs

Failure mode: A code release introduced the failure. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2020-06-06 10:51 UTC

   docs.rs is failing to build new releases, and we're investigating the problem.

2. identified 2020-06-06 11:12 UTC

   We have identified a possible cause of the issue and we're working on a fix.

3. monitoring 2020-06-06 11:17 UTC

   We have deployed a fix and we're monitoring recovery.

4. resolved 2020-06-06 11:35 UTC

   We confirmed the fix worked and we re-enabled builds. Build delays will be experienced for the next few hours as the server works through the backlog. The build queue is available at https://docs.rs/releases/queue.

Excerpts are shortened. Read the full incident on crates.io's status page.

Affected: crates.io

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. monitoring 2020-03-16 16:53 UTC

   Due to a outage affecting our infrastructure provider, in the past hour we experienced an increased number of errors while connecting to crates.io. We're continuing to monitor the situation, and you can follow the progress on Heroku's status page:...

2. resolved 2020-03-16 17:06 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on crates.io's status page.

Affected: crates.io

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2019-12-05 22:21 UTC

   We are currently seeing an increase in both response times and error rates and are investigating the issue.

2. monitoring 2019-12-05 22:31 UTC

   A fix has been implemented and we are monitoring the results.

3. resolved 2019-12-05 22:58 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on crates.io's status page.

Affected: crates.io

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2019-08-18 13:13 UTC

   We are currently seeing degraded performance across all endpoints on crates.io

2. monitoring 2019-08-18 13:21 UTC

   A fix has been implemented and we are monitoring the results.

3. resolved 2019-08-18 13:55 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on crates.io's status page.

Affected: crates.io

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. identified 2019-08-14 18:15 UTC

   An issue is preventing newly published crates from appearing in the index. We've identified the cause and are working on a fix.

2. monitoring 2019-08-14 18:32 UTC

   A fix has been implemented and we are monitoring the results.

3. resolved 2019-08-14 21:23 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on crates.io's status page.

Affected: crates.io

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

Names an upstream provider: GitHub.

1. resolved 2019-07-22 16:29 UTC

   Crates published to crates.io may experience a delay in appearing in the crates.io index, due to an ongoing issue with GitHub. This means that your crate may appear on crates.io, but cannot yet be used in Cargo.toml. If your crate is affected, it will automatically be published...

Excerpts are shortened. Read the full incident on crates.io's status page.