3 ms·
> outright laziness (which this incident clearly was) I don't think it was clearly laziness. It could have been a configuration mistake.
by collinmanderson 7y ago
> outright laziness (which this incident clearly was)
I don't think it was clearly laziness. It could have been a configuration mistake.
- bogomipz 7y agoIndeed and we saw that as a cause recently for a major Google outage. However that likely possibility of a bad config or edit doesn't fit the narrative Cloudflare is spinning here - that Verizon is simply dumb and lazy. Clearly Verizon has inbound prefix filtering in place otherwise this would be a common occurrence for AS 701 and it is most certainly not. And it's quite surprising and sad to see how willing people are to just blindly parrot Cloudflare here and pile on. This of course was the desired outcome of the blog post.