Observed topology

AS132168 ESUNHK-AS-AP ESUN TECHNOLOGY INTERNATIONAL CO., LIMITED

Unclassified APNIC

Upstreams 7 carry this network

Downstreams 1 this network carries

Adjacent (IPv4) 7

Adjacent (IPv6) 2

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS132168: 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
AS9304	HGC Global Communications Limited	Hosting	IPv4	570
AS2914	NTT America, Inc.	Transit	IPv4	334
AS174	Cogent Communications, LLC	Transit	IPv4	224
AS1299	Arelion Sweden AB	Transit	IPv4 IPv6	146
AS3320	Deutsche Telekom AG	Mobile	IPv4	43
AS4635	Hong Kong Internet Exchange--Route Server 1	Unclassified	IPv4	12
AS24482	SG.GS	Hosting	IPv4	9

Transit

Downstream networks

inferred

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

AS	Network	Type	Families	Paths seen
AS63689	Esun Technology(Shanghai) Co.,Ltd	Unclassified	IPv6	64

Adjacency

Adjacent networks

observed

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

AS	Network	Type	Families	Paths seen
AS9304	HGC Global Communications Limited	Hosting	IPv4	570
AS2914	NTT America, Inc.	Transit	IPv4	334
AS174	Cogent Communications, LLC	Transit	IPv4	224
AS1299	Arelion Sweden AB	Transit	IPv4 IPv6	210
AS63689	Esun Technology(Shanghai) Co.,Ltd	Unclassified	IPv6	64
AS3320	Deutsche Telekom AG	Mobile	IPv4	43
AS4635	Hong Kong Internet Exchange--Route Server 1	Unclassified	IPv4	12
AS24482	SG.GS	Hosting	IPv4	9

Provenance

Where this comes from

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