Huge, huge props to Cloudflare. THAT is what a good RFO report should look like.
Sucks when it happens, but spotting it quickly, backing out the change, and identifying how it happened is crucial to helping ensure it won't happen that way again. Thank you again to Tom, Bryton, and the rest of the Cloudflare team for the clear and comprehensive analysis of the outage. There's some really good learning lessons for all of us that are implementing automation across large networks. We don't all have to put our hands on the hot stove, one after another. ;) Thanks! Matt On Sun, Jan 25, 2026, 21:25 Hank Nussbacher via NANOG <[email protected]> wrote: > https://blog.cloudflare.com/route-leak-incident-january-22-2026/ > > > -Hank > > _______________________________________________ > NANOG mailing list > > https://lists.nanog.org/archives/list/[email protected]/message/5JDWQBCULLABBVZ5TMEEKGH7RLKZMNZH/ > _______________________________________________ NANOG mailing list https://lists.nanog.org/archives/list/[email protected]/message/IJYI7LW7PK6TM53QDGJXJ6KFK5T234V3/
