asn.dev

Observed topology

AS20648 TMN-SA

Hosting RIPE

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS20648: 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
AS6939Hurricane Electric LLCTransitIPv42,176
AS15830Equinix (EMEA) Acquisition Enterprises B.V.HostingIPv4379
AS174Cogent Communications, LLCTransitIPv4327
AS1299Arelion Sweden ABTransitIPv4276
AS9002RETN LimitedUnclassifiedIPv4229
AS29802HIVELOCITY, Inc.HostingIPv4170
AS3356Level 3 Parent, LLCTransitIPv4145

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS56817TMN SAUnclassifiedIPv466

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS6939Hurricane Electric LLCTransitIPv42,229
AS15830Equinix (EMEA) Acquisition Enterprises B.V.HostingIPv4379
AS174Cogent Communications, LLCTransitIPv4327
AS1299Arelion Sweden ABTransitIPv4276
AS9002RETN LimitedUnclassifiedIPv4242
AS29802HIVELOCITY, Inc.HostingIPv4170
AS3356Level 3 Parent, LLCTransitIPv4145
AS56817TMN SAUnclassifiedIPv466

Provenance

Where this comes from

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