Crates.io Status

Resolved crates.io failed to serve requests

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.

Resolved Cargo error when downloading crates from our CDN

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 CDN provider. We're in contact with their support team to address the issue.

Resolved docs.rs outage

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

Resolved crates.io outage

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

Resolved docs.rs unreachable

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

Resolved docs.rs fails to build new releases

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

Resolved Increased errors while connecting to crates.io

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: https://status.heroku.com/incidents/1973

Resolved Increased Error Rate

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

Resolved Degraded performance

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

Resolved Delay in index updates

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