Observed topology

AS17622 CNCGROUP-GZ - China Unicom Guangzhou network

Residential APNIC

Upstreams 2 carry this network

Downstreams 4 this network carries

Adjacent (IPv4) 6

Adjacent (IPv6) 2

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS17622: 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
AS4837	CHINA UNICOM China169 Backbone	Mobile	IPv4 IPv6	80,078
AS9929	CHINA UNICOM Industrial Internet Backbone	Unclassified	IPv4 IPv6	5,987

Transit

Downstream networks

inferred

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

AS	Network	Type	Families	Paths seen
AS10212	China Enterprise ICT Solutions Limited	Unclassified	IPv4	124
AS17428	21Vianet.Co.,Ltd	Unclassified	IPv4	30
AS146814	Hong Kong University of Science and Technology, Dongchung Town,	Unclassified	IPv4	16
AS151951	Shenzhen lesuyun Network Technology Co., Ltd	Unclassified	IPv4	2

Adjacency

Adjacent networks

observed

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

AS	Network	Type	Families	Paths seen
AS4837	CHINA UNICOM China169 Backbone	Mobile	IPv4 IPv6	80,250
AS9929	CHINA UNICOM Industrial Internet Backbone	Unclassified	IPv4 IPv6	5,987
AS10212	China Enterprise ICT Solutions Limited	Unclassified	IPv4	124
AS17428	21Vianet.Co.,Ltd	Unclassified	IPv4	30
AS146814	Hong Kong University of Science and Technology, Dongchung Town,	Unclassified	IPv4	16
AS151951	Shenzhen lesuyun Network Technology Co., Ltd	Unclassified	IPv4	2

Provenance

Where this comes from

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