Cargo error when downloading crates from our CDN

What to do

• Check whether you use crates.io crates.io in apac, us. Check your stack

  Paste a package.json, lockfile, Terraform or a list of domains at down.guide/stack to see every provider you depend on.

• Confirm your retries, queues and scheduled jobs caught up after the 4d 20h it lasted.

  Anything that failed between 2020-09-11 00:37 UTC and 2020-09-15 21:11 UTC may need a replay.

• Subscribe to crates.io's feed to hear about the next one first. RSS feed

  https://down.guide/feed?provider=crates-io works in Slack (/feed subscribe), Discord feed bots and any RSS reader.

Updates from crates.io 6

1. investigatingSep 11, 2020, 12:37 AM 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 CDN provider. We're in contact with their support team to address the issue.

   provider

2. investigatingSep 11, 2020, 10:06 AM 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.

   provider

3. monitoringSep 11, 2020, 2:16 PM 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.

   provider

4. monitoringSep 11, 2020, 11:26 PM 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.

   provider

5. monitoringSep 13, 2020, 1:47 PM 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.

   provider

6. resolvedSep 15, 2020, 9:11 PM 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.

   provider

Corrections

None so far.

Something wrong on this page? Report an error or send us a note. Every fix is listed here.