On 10/7/21 00:37, Michael Thomas wrote:
Maybe the problem here is that two things happened and the article conflated the two: the DNS infrastructure pulled its routes from the anycast address and something else pulled all of the other routes but wasn't mentioned in the article.
The origin problem was some "automation thingy" that went to check capacity status around the network ahead of some planned maintenance work, and that "automation thingy" decided checking was not enough, let's just turn the whole thing off.
Mark.
