asn.dev

Observed topology

AS206720 Airbus

Unclassified RIPE Enterprise

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

Transit

Upstream networks

All 11

Networks observed carrying traffic for AS206720: 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.

ASNetworkTypeFamiliesPaths seen
AS15830Equinix (EMEA) Acquisition Enterprises B.V.HostingIPv4348
AS6461Zayo BandwidthTransitIPv4120
AS4755TATA Communications formerly VSNL is Leading ISPHostingIPv461
AS1221Telstra LimitedMobileIPv460
AS6939Hurricane Electric LLCTransitIPv444
AS20766Association "Gitoyen"UnclassifiedIPv45
AS24482SG.GSHostingIPv45
AS34927iFog GmbHHostingIPv45
AS37721Virtual Technologies & SolutionsResidentialIPv45
AS50628Leonix Telecom SASUnclassifiedIPv45

All 11 upstreams →

Transit

Downstream networks

inferred

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

No downstream observed. This network does not appear to carry transit for anyone.

Adjacency

Adjacent networks

All 11

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

ASNetworkTypeFamiliesPaths seen
AS15830Equinix (EMEA) Acquisition Enterprises B.V.HostingIPv4348
AS6461Zayo BandwidthTransitIPv4120
AS4755TATA Communications formerly VSNL is Leading ISPHostingIPv461
AS1221Telstra LimitedMobileIPv460
AS6939Hurricane Electric LLCTransitIPv444
AS20766Association "Gitoyen"UnclassifiedIPv45
AS24482SG.GSHostingIPv45
AS34927iFog GmbHHostingIPv45
AS37721Virtual Technologies & SolutionsResidentialIPv45
AS50628Leonix Telecom SASUnclassifiedIPv45

All 11 adjacent →

Provenance

Where this comes from

Derived from routing tables collected at 2026-10-29 10:00 UTC by route-views2,rrc00, as seen from 76 BGP vantage points across 74.36M 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.