asn.dev

Observed topology

AS58542 CHINATELECOM-TIANJIN - Tianjij,300000

Unclassified APNIC

Upstreams 1 carry this network
Downstreams 3 this network carries
Adjacent (IPv4) 4
Adjacent (IPv6) 3
Upstream graph Who carries AS58542, and who carries them, drawn as a map up to the transit-free core. 0 exchanges Where AS58542 physically turns up to peer, and its address on each fabric.

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS58542: 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.

ASNetworkTypeFamiliesPaths seen
AS4134No.31,Jin-rong StreetResidentialIPv4 IPv63,958

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS137718Beijing Volcano Engine Technology Co., Ltd.HostingIPv4 IPv66,831
AS45090Shenzhen Tencent Computer Systems Company LimitedHostingIPv4 IPv65,385
AS59019Beijing Kingsoft Cloud Internet Technology Co., LtdUnclassifiedIPv4596

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS4134No.31,Jin-rong StreetResidentialIPv4 IPv616,770
AS137718Beijing Volcano Engine Technology Co., Ltd.HostingIPv4 IPv66,831
AS45090Shenzhen Tencent Computer Systems Company LimitedHostingIPv4 IPv65,385
AS59019Beijing Kingsoft Cloud Internet Technology Co., LtdUnclassifiedIPv4596

Provenance

Where this comes from

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