Thursday, 30 August, 2018 UTC
Summary
Aug 30, 12:00 UTC
Resolved - A bug in a recently updated service caused a small number of packages (in fact we believe only 2 were actually affected) to 404 on install if they had recently been the subject of a security advisory.
The root cause was identified and fix pushed soon after.
It was in no way related to the planned DNS migration which did not proceed as planned at 12:00 UTC but instead was postponed.
We're sorry for the disruption this caused to some of our users, please do get in touch through our support channels if you see any other issues.
Resolved - A bug in a recently updated service caused a small number of packages (in fact we believe only 2 were actually affected) to 404 on install if they had recently been the subject of a security advisory.
The root cause was identified and fix pushed soon after.
It was in no way related to the planned DNS migration which did not proceed as planned at 12:00 UTC but instead was postponed.
We're sorry for the disruption this caused to some of our users, please do get in touch through our support channels if you see any other issues.