Dear Reda, I assume you are referring to the RIPEstat Data API documentation. The data call you are looking for is the ASN Neighbours [0] and AS Routing Consistency [1]. [0] https://stat.ripe.net/docs/data_api#AsnNeighbours [1] https://stat.ripe.net/docs/data_api#AsRoutingConsistency ### IMPORTANT ### [0] provides the view based on routing data collected with the RIS system (http://ris.ripe.net). Seconding what Shane already said, the classification "left" and "right" is kept intentionally neutral as any business relationships ("up/downstream" vs. "peering") can NOT be derived from the data. An incorrect interpretation would associate "left" with upstream and "right" with downstream! There is only certainty about the statement that "left"-only classified can NOT be downstream, "right"-only classified can NOT be upstream. [1] provides the view based on registry data, more specifically from Internet Routing Registries. ### HOW TO USE ### If you want to see the adjacent networks for AS3333 as seen in RIS: https://stat.ripe.net/data/asn-neighbours/data.json?resource=AS3333 Replace the value of the parameter "resource" with the ASN you want to look up. By default you will get the latest status but the data call also supports historical lookups, see parameter "starttime". Similar for the AS Routing Consistency data call: https://stat.ripe.net/data/prefix-routing-consistency/data.json?resource=AS3... Look for the "exports" and "imports" attributes. Hth, Christian Teuschel R&D System Architect RIPE NCC Sent via RIPE Forum -- https://www.ripe.net/participate/mail/forum