From theodore at ciscodude.net Thu Jun 27 19:13:41 2019
From: theodore at ciscodude.net (Theodore Baschak)
Date: Thu, 27 Jun 2019 19:13:41 -0500
Subject: [MBNOG] the routing leak on monday from MBNOG's perspective
Message-ID: <08AEA8B2-EB2D-405B-8C06-101A0135A615@ciscodude.net>
There was a routing incident on monday. It was pretty early in the morning so it may or may not have come up on your radar. There's been some news/reporting about it all week, and cloudflare's done at least 2 blogs now. This is the second.
https://blog.cloudflare.com/the-deep-dive-into-how-verizon-and-a-bgp-optimizer-knocked-large-parts-of-the-internet-offline-monday/
I read this blog earlier when I was too busy to fully comprehend that I've got data locally about this routing leak as well.
It just came up again and it reminded me, and so I just searched the MBNOG MRT archive for routing updates from 2019-06-24 thru 2019-06-25 that had the AS-PATH 701 396531 33154 in them, and was able to determine that everyone who feeds DFZ routing data to MBNOG was affected because their upstreams or upstreams of upstreams (577, 6939, and 6327) all propagated the routes down to them as customers from peering or transit sessions they themselves had with transit-free networks who let the routes flow (174 and 6453 it looks like), or direct sessions with 701.
Theodore Baschak - AS395089 - Hextet Systems
https://bgp.guru/ - https://hextet.net/
http://mbix.ca/ - http://mbnog.ca/
-------------- next part --------------
An HTML attachment was scrubbed...
URL: