Resolved -
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.
Sep 15, 21:11 UTC
Update -
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.
Sep 13, 13:47 UTC
Update -
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.
Sep 11, 23:26 UTC
Monitoring -
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.
Sep 11, 14:16 UTC
Update -
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.
Sep 11, 10:06 UTC
Investigating -
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.
Sep 11, 00:37 UTC