The deep-dive into how Verizon and a BGP Optimizer Knocked Large Parts of the Internet Offline Monday

What this post added

This post provides a deep-dive analysis of a major BGP route leak event that occurred on June 24, 2019, caused by Verizon and a BGP optimizer. It details the technical investigation using RIPE NCC archived data to identify affected routes, the timing of the leak (approximately two hours), and the implications of invalid route propagation. The post highlights the importance of BGP communities like NO_EXPORT and the role of RPKI ROAs in preventing such incidents, directly contributing to the understanding and mitigation of global network stability issues.