[routing-wg] is RIPEstat confused about the origin of 147.171.0.0/16?
- Previous message (by thread): [routing-wg] "Mapping the RPKI unreachable IP address space" - RIPE specific results
- Next message (by thread): [routing-wg] is RIPEstat confused about the origin of 147.171.0.0/16?
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
nusenu
nusenu-lists at riseup.net
Thu Sep 27 01:11:00 CEST 2018
Hi, I came across this particular prefix when going through big RPKI unreachable blocks. prefix-routing-consistency [1] says: current origin is AS2200 prefix-overview [2] says: current origin is AS1942 (nlnog's LG agrees) routing-history [3] says it was announced by AS220 until 2017-06-10 and is currently announced by AS1942 RPKI validator's BGP Preview (using RIS): says it is announced by AS1942 and is therefore invalid (ROA authorizes AS2200 - not AS1942) So why does [1] say this prefix is announced by AS2200? maybe it is announced by both? btw: AS2200 and AS1942 have the same owner and AS2200 appears to be the only upstream of AS1942. [1] https://stat.ripe.net/widget/prefix-routing-consistency#w.resource=147.171.0.0%2F16 [2] https://stat.ripe.net/widget/prefix-overview#w.resource=147.171.0.0%2F16 [3] https://stat.ripe.net/widget/routing-history#w.resource=147.171.0.0%2F16 -- https://twitter.com/nusenu_ https://mastodon.social/@nusenu -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 833 bytes Desc: OpenPGP digital signature URL: <https://lists.ripe.net/ripe/mail/archives/routing-wg/attachments/20180926/1f14f57f/attachment.sig>
- Previous message (by thread): [routing-wg] "Mapping the RPKI unreachable IP address space" - RIPE specific results
- Next message (by thread): [routing-wg] is RIPEstat confused about the origin of 147.171.0.0/16?
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]