[Outages-discussion] RPKI invalid 209.58.46.0/24 widely accepted (was: [outages] [23E-270B4044-0002] TATA issues in Los Angeles)

[Lukas Tribus]

Hello,


On Mon, 5 Oct 2020 at 19:35, Jared Geiger via Outages
<outages at outages.org> wrote:
>
> If anyone at TATA 6453 is watching, you're announcing 209.58.46.0/24 to NTT 2914 in Sydney causing traffic to your North American VOIP network to go through Australia. The rest of your announcements to your peers are for 209.58.0.0/17 which correctly keeps the traffic in North America. Filtering the /24 out of NTT's BGP feed fixed my latency and packet loss problem. NTT contacted the TATA NOC on my behalf but no one has fixed it yet.


Moving to outages-discussion@

This is a RPKI invalid prefix, the ROA 209.58.0.0/17 has maxlength /17
with a creation date back in August. Unless there was a parallel /24
ROA just a few minutes ago, I don't get it why 174, 2914 and other
networks would carry this prefix in their table:

http://lg.ring.nlnog.net/prefix_detail/lg01/ipv4?q=209.58.46.0/24

https://rpki.cloudflare.com/?view=validator&validateRoute=6453_209.58.46.0%2F24


Looks like 6453 is originating a number of invalids actually, but I
would expect the ROV enabled networks to drop those prefixes:
https://bgp.he.net/AS6453#_prefixes


Thoughts?



Lukas