Verizon no BGP route to some of AS38365 (182.61.200.0/24)

Rafael Possamai rafael at thinkpad.io
Thu Jul 21 13:35:06 UTC 2022


>but that it would be incumbent on Verizon to do the legwork to fix it since they are the ones who know their peering >agreements and have these contacts. Unfortunately it seems like policy that Verizon pushes any issues that aren't internal >routing issues to an external party, but surely they have a responsibility to maintain their peering and routes to external >services as well.
>Any thoughts?

You're probably right they have a responsibility to maintain their peering and routes, but rather than move mountains to get a large network to do "the right thing" (either vzw or baidu), I'd think most of the time it's much easier to pick a different provider to work with instead.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman.nanog.org/pipermail/nanog/attachments/20220721/64ba4e88/attachment.html>


More information about the NANOG mailing list