3 ms·

It was gross negligence that leads to this. Nothing more.

• bogomipz 7y ago
  Do you work for Verizon's NOC or Network Engineering department then? You have inside knowledge that it was negligence? Because I provided a specific scenario where it would not be "gross negligence."
  • Cpoll 7y ago
    > Do you work for Verizon's NOC or Network Engineering department then If that's what it takes to be able to decide, then I guess we can safely declare that it wasn't negligence, because no-one that fits that description will ever publicly admit to it.
  • wtallis 7y ago
    > Because I provided a specific scenario where it would not be "gross negligence." No, you didn't. You provided a vague conjecture for how the initial cause of the problem might not have been gross negligence, but offered no hypothesis for why Verizon isn't answering the Red Phone.
    • bogomipz 7y ago
      Yes I did. It's the part where I clearly state it's possible that a router that offline or rebooted came up with a stale or incorrect config. This actually happens occasionally. I've been on both ends of it. Clearly Verizon has inbound prefix filtering in place as this is not some common occurrence for AS 701. Verizon was in contact with people yesterday. I have spoken to two people from two other carriers who were in touch with them. And you are just parroting the idea that because Cloudflare didn't get a response that Verizon wasn't responding to anyone period. And that's just not true. The fact that you think there's some red phone that just anyone can call the NOC and magically speak to someone during a major outage shows you have no practical experience with thes things you are commenting on and criticizing.