Observed topology

AS20648 TMN-SA 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.

AS	Network	Type	Families	Paths seen
AS6939	Hurricane Electric LLC	Transit	IPv4	2,088
AS15830	Equinix (EMEA) Acquisition Enterprises B.V.	Hosting	IPv4	380
AS174	Cogent Communications, LLC	Transit	IPv4	324
AS1299	Arelion Sweden AB	Transit	IPv4	315
AS9002	RETN Limited	Unclassified	IPv4	229
AS29802	HIVELOCITY, Inc.	Hosting	IPv4	166
AS3356	Level 3 Parent, LLC	Transit	IPv4	143

Transit

Downstream networks

inferred

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

AS	Network	Type	Families	Paths seen
AS56817	TMN SA	Unclassified	IPv4	64

Adjacency

Adjacent networks

observed

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

AS	Network	Type	Families	Paths seen
AS6939	Hurricane Electric LLC	Transit	IPv4	2,139
AS15830	Equinix (EMEA) Acquisition Enterprises B.V.	Hosting	IPv4	380
AS174	Cogent Communications, LLC	Transit	IPv4	324
AS1299	Arelion Sweden AB	Transit	IPv4	315
AS9002	RETN Limited	Unclassified	IPv4	242
AS29802	HIVELOCITY, Inc.	Hosting	IPv4	166
AS3356	Level 3 Parent, LLC	Transit	IPv4	143
AS56817	TMN SA	Unclassified	IPv4	64

Provenance

Where this comes from

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