asn.dev

Observed topology

AS209162 INTERNETHELLAS-ASN

Unclassified RIPE

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

Transit

Upstream networks

All 21

Networks observed carrying traffic for AS209162: 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
AS199081Lancom Ltd.UnclassifiedIPv458
AS3356Level 3 Parent, LLCTransitIPv424
AS3257GTT Communications Inc.TransitIPv49
AS9002RETN LimitedUnclassifiedIPv49
AS50673Serverius Holding B.V.UnclassifiedIPv42
AS293ESnetUnclassifiedIPv41
AS3216PJSC "Vimpelcom"MobileIPv41
AS3333Reseaux IP Europeens Network Coordination Centre (RIPE NCC)UnclassifiedIPv41
AS4657StarHub LtdResidentialIPv41
AS8280SYNAPSECOM S.A. Provider of Telecommunications and Internet ServicesHostingIPv41

All 21 upstreams →

Transit

Downstream networks

inferred

Networks for which AS209162 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 21

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

ASNetworkTypeFamiliesPaths seen
AS199081Lancom Ltd.UnclassifiedIPv458
AS3356Level 3 Parent, LLCTransitIPv424
AS3257GTT Communications Inc.TransitIPv49
AS9002RETN LimitedUnclassifiedIPv49
AS50673Serverius Holding B.V.UnclassifiedIPv42
AS293ESnetUnclassifiedIPv41
AS3216PJSC "Vimpelcom"MobileIPv41
AS3333Reseaux IP Europeens Network Coordination Centre (RIPE NCC)UnclassifiedIPv41
AS4657StarHub LtdResidentialIPv41
AS8280SYNAPSECOM S.A. Provider of Telecommunications and Internet ServicesHostingIPv41

All 21 adjacent →

Provenance

Where this comes from

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