Struck in red is what crates.io removed; blue is what they added. Muted text is unchanged context.
BeforeAfter
AddedTitle#1
Before: not present
After: Cargo error when downloading crates from our CDN
AddedImpact#2
Before: not present
After: major
AddedStatus#3
Before: not present
After: resolved
AddedStart time#4
Before: not present
After: 2020-09-11 00:37 UTC
AddedResolved time#5
Before: not present
After: 2020-09-15 21:11 UTC
AddedAffected components#6
Before: not present
After: crates.io
AddedUpdateinvestigating#7
Before: not present
After: 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.
AddedUpdateinvestigating#8
Before: not present
After: 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.
AddedUpdatemonitoring#9
Before: not present
After: 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.
AddedUpdatemonitoring#10
Before: not present
After: 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.
AddedUpdatemonitoring#11
Before: not present
After: 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.
AddedUpdateresolved#12
Before: not present
After: 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.
Rewindex commits each version of an incident it captures to a daily checkpoint, chains it to the day before, and has the checkpoint timestamped by FreeTSA and DigiCert.