prefix-routing-consistency widget only shows a result for the route observed by the lowest amount of peers

[nusenu]

example:
https://stat.ripe.net/widget/prefix-overview#w.resource=147.171.0.0%2F16

and

https://stat.ripe.net/widget/routing-history#w.resource=147.171.0.0%2F16
say the source is AS1942:

but prefix-routing-consistency disagrees. It says the only source is AS2200:

https://stat.ripe.net/widget/prefix-routing-consistency#w.resource=147.171.0.0%2F16

Rene Wilhelm wrote on the routing-wg (2018-09-27):
https://www.ripe.net/ripe/mail/archives/routing-wg/2018-September/003630.html

prefix-routing-consistency widget appears to indeed have problems;
at least in this case. It only shows a result for the route observed
by the lowest amount of peers.

[cteusche-ripencc]

I consider this a bug and I will check it in the next bug fixing phase.

[nusenu]

Hi Christian, since I'm getting hit by this bug again, can you share any timeline or update on this?

[cteusche-ripencc]

Hi Nusenu,

I was under the impression that was fixed, as Prefix Routing Consistency also shows both ASNs for the given prefix.
Please share the resource and I'll check it!

[cteusche-ripencc]

[nusenu]

this is some strange prefix announced via a private and non-private ASN https://stat.ripe.net/widget/prefix-routing-consistency#w.resource=2803%3A7d00%3A80%3A%3A%2F48 https://stat.ripe.net/widget/prefix-overview#w.resource=2803%3A7d00%3A80%3A%3A%2F48 there are some more: https://nusenu.github.io/RPKI-Observatory/unreachable_AS64513-v6.html

[cteusche-ripencc]

Gotcha! I'll get back to you soon

[cteusche-ripencc]

Bummer, this issue was indeed not fixed and the second ASN in the 147.171/16 result was actually coming from the registry data, sorry about that.

I created a bug fix, which should be available in production in about 2 hours.

[nusenu]

thank you!