Now this is kind of interesting. I see route-views can see the route now... BGP routing table entry for 23.151.232.0/24, version 2814701286 Paths: (19 available, best #19, table default) Not advertised to any peer Refresh Epoch 1 3333 1257 6453 23470 23470 23470 23470 193.0.0.56 from 193.0.0.56 (193.0.0.56) Origin IGP, localpref 100, valid, external Community: 1257:50 1257:51 1257:3528 1257:4103 path 7FE0DBA20378 RPKI State not found rx pathid: 0, tx pathid: 0 Refresh Epoch 1 ... The only IRR route object I see for it is route: 23.151.232.0/24 origin: AS23470 descr: Qeru Systems, LLC mnt-by: MAINT-AS23470 changed: jcid@reliablesite.net 20230425 #01:09:36Z source: RADB rpki-ov-state: not_found # No ROAs found, or RPKI validation not enabled for source and there appears to be no ROA. According to https://lg.as6453.net/doc/cust-routing-policy.html, I would not have expected Tata to accept this route from RELIABLESITE (not based on the above route object), unless Tata is not using an IRR-based auto-generated prefix-list filter for RELIABLESITE, but rather a manually edited one. ---------------------------------------------------------------------- Jon Lewis, MCP :) | I route StackPath, Sr. Neteng | therefore you are _________ http://www.lewis.org/~jlewis/pgp for PGP public key_________