Observed topology

AS58536 AP-CONAC-AS-AP CONAC China Organizational Name Administration Center

Unclassified APNIC

Upstreams 6 carry this network

Downstreams 0 this network carries

Adjacent (IPv4) 5

Adjacent (IPv6) 1

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS58536: 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
AS19174	China Unicom (Americas) Operations Ltd	Unclassified	IPv4	157
AS4808	China Unicom Beijing Province Network	Residential	IPv4	149
AS3356	Level 3 Parent, LLC	Transit	IPv6	102
AS4812	China Telecom (Group)	Residential	IPv4	61
AS38283	CHINANET SiChuan Telecom Internet Data Center	Unclassified	IPv4	25
AS141425	China Mobile Group Guangdong communications corporation	Unclassified	IPv4	7

Transit

Downstream networks

inferred

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

No downstream observed. This network does not appear to carry transit for anyone.

Adjacency

Adjacent networks

observed

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

AS	Network	Type	Families	Paths seen
AS19174	China Unicom (Americas) Operations Ltd	Unclassified	IPv4	157
AS4808	China Unicom Beijing Province Network	Residential	IPv4	149
AS3356	Level 3 Parent, LLC	Transit	IPv6	102
AS4812	China Telecom (Group)	Residential	IPv4	61
AS38283	CHINANET SiChuan Telecom Internet Data Center	Unclassified	IPv4	25
AS141425	China Mobile Group Guangdong communications corporation	Unclassified	IPv4	7

Provenance

Where this comes from

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