asn.dev

Observed topology

AS38345 ZDNS Internet Domain Name System Beijing Engineering Resrarch Center Ltd.

Unclassified APNIC

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS38345: 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
AS7497Computer Network Information Center of Chinese Academy of Sciences (CNIC-CAS)EducationIPv4 IPv6859
AS174Cogent Communications, LLCTransitIPv4 IPv6570
AS4641The Hong Kong Internet Exchange LimitedUnclassifiedIPv4 IPv6229
AS4635Hong Kong Internet Exchange--Route Server 1UnclassifiedIPv6104
AS24482SG.GSHostingIPv68

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS63363Tucows.com Co.UnclassifiedIPv459
AS393818Tucows.com Co.UnclassifiedIPv41

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS7497Computer Network Information Center of Chinese Academy of Sciences (CNIC-CAS)EducationIPv4 IPv6919
AS174Cogent Communications, LLCTransitIPv4 IPv6570
AS4641The Hong Kong Internet Exchange LimitedUnclassifiedIPv4 IPv6229
AS4635Hong Kong Internet Exchange--Route Server 1UnclassifiedIPv6104
AS63363Tucows.com Co.UnclassifiedIPv459
AS24482SG.GSHostingIPv68
AS393818Tucows.com Co.UnclassifiedIPv41

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.