asn.dev

Observed topology

AS24348 CNGI-BJ-IX2-AS-AP - CERNET2 IX at Tsinghua University

Unclassified APNIC

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS24348: 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
AS4538China Education and Research Network CenterEducationIPv4107
AS23910China Next Generation Internet CERNET2UnclassifiedIPv659

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS45576Tsinghua UniversityUnclassifiedIPv6147
AS24302CRIS-CERNETUnclassifiedIPv637
AS9405Test platform Service CenterUnclassifiedIPv636
AS24310Net-Glyph Data CenterUnclassifiedIPv636
AS131490CERNET CorporationUnclassifiedIPv61

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS23910China Next Generation Internet CERNET2UnclassifiedIPv6280
AS45576Tsinghua UniversityUnclassifiedIPv6147
AS4538China Education and Research Network CenterEducationIPv4 IPv6143
AS24302CRIS-CERNETUnclassifiedIPv637
AS9405Test platform Service CenterUnclassifiedIPv636
AS24310Net-Glyph Data CenterUnclassifiedIPv636
AS131490CERNET CorporationUnclassifiedIPv61

Provenance

Where this comes from

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