On 26. 11. 25 09:59, Joe Abley wrote: > I seem to think normal exit selection works just fine for this in > most cases, but perhaps you have seen problems that I am not aware > of. What scenarios do you see where a special routing policy would > make things better? Khm... We had a case where we announced our anycast prefixes to our upstream in Johannesburg and that upstream was a paying customer of a large tier1 (that we all know... :( ) and due to the fact that that tier1 received prefixes from a paying customer thye got higher preference - so all of a sudden they started routing traffic from around the world (that was inside their global network) to Johannesburg, despite the fact that they received our prefixes from other places around the world. Of course the latency went instantly up for everyone outside South Africa :( Classic frozen potatoe routing.
No-export to that tier1 fixed the problem, but still... Cheers, Jan ----- To unsubscribe from this mailing list or change your subscription options, please visit: https://mailman.ripe.net/mailman3/lists/ripe-list.ripe.net/ As we have migrated to Mailman 3, you will need to create an account with the email matching your subscription before you can change your settings. More details at: https://www.ripe.net/membership/mail/mailman-3-migration/
