-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi, NANOGers.
Did anyone else notice that the path changed from 65332 to 65332 65331 earlier today?
My apologies! We had a configuration "oops" during a migration to a new back-end infrastructure. We're working through that now, and I believe we have it sorted. I'll send out a more gory detailed update in a bit.
We certainly did when we starting advertising all the bogons to our ISP peers. Probably should have had an inbound AS path filter on that cymru peering...
Yes, please, great advice from both you and Nick. Our Juniper configuration templates have something along these lines already. I need to add the same to our Cisco configuration snippets. <https://www.team-cymru.org/Services/Bogons/bgp-examples.html> Feedback on the configuration snippets is always welcome! Be the first in your ASN to add your name to the contributor list. :) Again my apologies for any inconvenience or consternation this mishap has caused. Thanks, Rob. - -- Rabbi Rob Thomas Team Cymru https://www.team-cymru.org/ "Does this augment or diminish human liberty?" - William F. Buckley -----BEGIN PGP SIGNATURE----- iQCVAwUBUjc+n1kX3QAo5sgJAQL4EQP+MIuA0TXvDIAXfDa2/0cW0k2pSpQqXuYe 52bYEMMHQDDLY+1XTXYnwrGGE/bcAIjyz6Mj9Kz0eN4FqvwTa2Nt64OjsQe6+drr eJoCp2kxOlYamX+tHX8KSd3Ge/l91LAkBms3GoM0CbL7JtBo+OZoZRUdYPj3PXdq EBH8eDQNboc= =8piW -----END PGP SIGNATURE-----