asn.dev

Observed topology

AS59019 BJKSCNET Beijing Kingsoft Cloud Internet Technology Co., Ltd

Unclassified APNIC

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS59019: 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
AS23724IDC, China Telecommunications CorporationUnclassifiedIPv4 IPv61,458
AS58542Tianjij,300000UnclassifiedIPv4591
AS58466CHINANET Guangdong province networkUnclassifiedIPv6512
AS4811China Telecom (Group)ResidentialIPv4178
AS133111CERNET New Technology Co., LtdUnclassifiedIPv6139
AS17621China Unicom Shanghai networkUnclassifiedIPv4 IPv620
AS9808China Mobile Communications Group Co., Ltd.MobileIPv47
AS133119China Unicom IP networkUnclassifiedIPv41

Transit

Downstream networks

inferred

Networks for which AS59019 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 AS59019 in a routing path, in either direction.

ASNetworkTypeFamiliesPaths seen
AS23724IDC, China Telecommunications CorporationUnclassifiedIPv4 IPv61,458
AS58542Tianjij,300000UnclassifiedIPv4591
AS58466CHINANET Guangdong province networkUnclassifiedIPv6512
AS4811China Telecom (Group)ResidentialIPv4178
AS133111CERNET New Technology Co., LtdUnclassifiedIPv6139
AS17621China Unicom Shanghai networkUnclassifiedIPv4 IPv620
AS9808China Mobile Communications Group Co., Ltd.MobileIPv47
AS133119China Unicom IP networkUnclassifiedIPv41

Provenance

Where this comes from

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