Observed topology

AS140056 CHINANET-MAOMING-AS-AP - China Telecom

Unclassified APNIC

Upstreams 1 carry this network

Downstreams 6 this network carries

Adjacent (IPv4) 0

Adjacent (IPv6) 7

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS140056: 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
AS58543	Guangdong	Unclassified	IPv6	32

Transit

Downstream networks

inferred

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

AS	Network	Type	Families	Paths seen
AS140053	China Telecom	Unclassified	IPv6	124
AS140309	CHINATELECOM Guangdong province Zhongshan 5G network	Unclassified	IPv6	124
AS140311	CHINATELECOM Guangdong province Jiangmen 5G network	Unclassified	IPv6	124
AS140318	CHINATELECOM Guangdong province Heyuan 5G network	Unclassified	IPv6	124
AS140319	CHINATELECOM Guangdong province Qingyuan 5G network	Unclassified	IPv6	124
AS140320	CHINATELECOM Guangdong province Shanwei 5G network	Unclassified	IPv6	124

Adjacency

Adjacent networks

observed

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

AS	Network	Type	Families	Paths seen
AS58543	Guangdong	Unclassified	IPv6	776
AS140053	China Telecom	Unclassified	IPv6	124
AS140309	CHINATELECOM Guangdong province Zhongshan 5G network	Unclassified	IPv6	124
AS140311	CHINATELECOM Guangdong province Jiangmen 5G network	Unclassified	IPv6	124
AS140318	CHINATELECOM Guangdong province Heyuan 5G network	Unclassified	IPv6	124
AS140319	CHINATELECOM Guangdong province Qingyuan 5G network	Unclassified	IPv6	124
AS140320	CHINATELECOM Guangdong province Shanwei 5G network	Unclassified	IPv6	124

Provenance

Where this comes from

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