Hi nusenu, 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..". Best regards, Christian PS: For a more in-depth explanation of the filter threshold please read [2]. [0] https://stat.ripe.net/docs/data_api#as-routing-consistency [1] https://stat.ripe.net/docs/data_api#announced-prefixes [2] https://labs.ripe.net/Members/wilhelm/content-how-define-address-space-routed On 18/03/2019 02:48, nusenu wrote: > Hi Nathalie, > > Nathalie Trenaman: >> The data in the validator is consistent with the data in RIS: >> https://stat.ripe.net/widget/announced-prefixes#w.resource=15576 >> <https://stat.ripe.net/widget/announced-prefixes#w.resource=15576> >> You can see 0.0.0.0/0 (and ::/0 by the way) there. > > then I'm wondering what the difference between the two RIPEstat widgets is > since the other one does not include 0.0.0.0/0 as mentioned in the first email > https://stat.ripe.net/widget/as-routing-consistency#w.resource=AS15576 > > https://stat.ripe.net/docs/data_api#as-routing-consistency > in_bgp "True" if the route has been seen by RIS, "False" otherwise > > - AS Routing Consistency > "This data call shows the difference between routing and registration state > of a ASN." > > - Announced Prefixes > "This data call returns all announced prefixes for a given ASN. The results > can be restricted to a specific time period." > >> Out of curiosity, did you ping them about these mis-announcements already? > I did not. > > thanks for your reply, > nusenu > -- Christian Teuschel | Human behind RIPEstat Follow me on Twitter: @NCC_RIPEstat
