asn.dev

Observed topology

AS51706 France IX Services SASU

Unclassified RIPE

Upstreams 0 carry this network
Downstreams 9 this network carries
Adjacent (IPv4) 11
Adjacent (IPv6) 0
Upstream graph Who carries AS51706, and who carries them, drawn as a map up to the transit-free core. 1 exchange Where AS51706 physically turns up to peer, and its address on each fabric.

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS51706: the AS immediately before it in a routing path. Ranked by how many paths showed the relationship, which reflects how widely it is used, not how much traffic crosses it.

No upstream observed. Typical for a tier-1 network that buys transit from nobody.

Transit

Downstream networks

inferred

Networks for which AS51706 was observed as the last hop before the origin, meaning it appears to provide them transit.

ASNetworkTypeFamiliesPaths seen
AS47583Hostinger International LimitedHostingIPv4453
AS43142ADELI SASResidentialIPv47
AS2094RenaterUnclassifiedIPv44
AS9434Internet Initiative Japan, Inc.UnclassifiedIPv41
AS15436WITBE S.A.UnclassifiedIPv41
AS34572HELIANTIS SASUnclassifiedIPv41
AS37054Telecom MalagasyResidentialIPv41
AS199248NUMLOG S.A.S.ResidentialIPv41
AS327814Ecoband LtdUnclassifiedIPv41

Adjacency

Adjacent networks

All 11

Every AS seen directly next to AS51706 in a routing path, in either direction.

ASNetworkTypeFamiliesPaths seen
AS23764CTGNetUnclassifiedIPv4471
AS47583Hostinger International LimitedHostingIPv4453
AS43142ADELI SASResidentialIPv47
AS2094RenaterUnclassifiedIPv44
AS9434Internet Initiative Japan, Inc.UnclassifiedIPv41
AS15436WITBE S.A.UnclassifiedIPv41
AS34572HELIANTIS SASUnclassifiedIPv41
AS37054Telecom MalagasyResidentialIPv41
AS39063Leitwert GmbHUnclassifiedIPv41
AS199248NUMLOG S.A.S.ResidentialIPv41

All 11 adjacent →

Provenance

Where this comes from

Derived from routing tables collected at 2026-10-16 10:00 UTC by route-views2,rrc00, as seen from 75 BGP vantage points across 73.23M route entries. These are observations from those vantage points, not a complete or authoritative view of the internet.

Inferred from path position, not from any declaration by either party. A network appearing here is carrying these routes; whether that is a paid transit arrangement, a backup, or something else is not something routing data can tell you. Adjacency is not the same as peering. Being next to each other in a path covers paid transit, settlement-free peering and customer connections alike, and routing data cannot distinguish them. Treat this as "these networks exchange routes", nothing more specific.

Cross-check against RIPEstat or BGP.tools, which observe from a different and larger set of vantage points.