Christian Teuschel:
Let me clarify, the AS Routing Consistency data call [0] is an API endpoint that was primarily developed to service the widget as it combines multiple data sources into a new functionality, the routing consistency. In order to fulfil this functionality RIPEstat applies a prefix filter to remove "unintended" routes so that the user can focus on consistency. The filter threshold is set so that routes that have not been seen by at least 10 full-table peers are removed.
The Announced Prefixes data call is more raw and is used as input for various other applications and provides more control over the output. This data call has a parameter which controls the filter threshold, "min_peers_seeing", which currently defaults to 3, as described in the documentation [1].
I understand why this can cause confusion and as an result I will change the default threshold for the Announced Prefixes to 10 and update the documentation for the AS Routing Consistency to reflect the route filter. Plus the typo "..registration state of aN ASN..".
thanks for your comprehensive answer, maybe you want to add the information about these filters that apply but can not be changed to the AS Routing Consistency data call to the documentation since you already typed it. thank you, nusenu -- https://twitter.com/nusenu_ https://mastodon.social/@nusenu