Observed topology

AS20021 LNH-INC

Hosting APNIC Content

Upstreams 7 carry this network

Downstreams 3 this network carries

Adjacent (IPv4) 10

Adjacent (IPv6) 6

Upstream graph Who carries AS20021, and who carries them, drawn as a map up to the transit-free core. 3 exchanges Where AS20021 physically turns up to peer, and its address on each fabric.

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS20021: 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
AS1299	Arelion Sweden AB	Transit	IPv4 IPv6	585
AS3356	Level 3 Parent, LLC	Transit	IPv4 IPv6	575
AS6939	Hurricane Electric LLC	Transit	IPv4 IPv6	218
AS852	TELUS Communications Inc.	Residential	IPv4 IPv6	26
AS24482	SG.GS	Hosting	IPv4 IPv6	26
AS37721	Virtual Technologies & Solutions	Residential	IPv4 IPv6	26
AS293	ESnet	Unclassified	IPv4	24

Transit

Downstream networks

inferred

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

AS	Network	Type	Families	Paths seen
AS40481	G3 Group	Unclassified	IPv4	59
AS53658	SocketLabs	Unclassified	IPv4	59
AS55117	Long View Systems Corporation (USA)	Unclassified	IPv4	57

Adjacency

Adjacent networks

observed

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

AS	Network	Type	Families	Paths seen
AS1299	Arelion Sweden AB	Transit	IPv4 IPv6	679
AS3356	Level 3 Parent, LLC	Transit	IPv4 IPv6	621
AS6939	Hurricane Electric LLC	Transit	IPv4 IPv6	245
AS40481	G3 Group	Unclassified	IPv4	59
AS53658	SocketLabs	Unclassified	IPv4	59
AS55117	Long View Systems Corporation (USA)	Unclassified	IPv4	57
AS852	TELUS Communications Inc.	Residential	IPv4 IPv6	28
AS24482	SG.GS	Hosting	IPv4 IPv6	28
AS37721	Virtual Technologies & Solutions	Residential	IPv4 IPv6	28
AS293	ESnet	Unclassified	IPv4	26

Provenance

Where this comes from

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