asn.dev

Observed topology

AS63741 DCNET-AS-VN - DCNET TELECOM

Unclassified APNIC Cable/DSL/ISP

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

Transit

Upstream networks

All 44

Networks observed carrying traffic for AS63741: 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
AS6939Hurricane Electric LLCTransitIPv4 IPv6274
AS24482SG.GSHostingIPv4 IPv6218
AS45903CMC Telecom Infrastructure CompanyResidentialIPv4 IPv6162
AS4637Telstra GlobalUnclassifiedIPv476
AS45899VNPT CorpMobileIPv4 IPv676
AS2914NTT America, Inc.TransitIPv4 IPv670
AS9304HGC Global Communications LimitedHostingIPv451
AS7552Viettel GroupMobileIPv447
AS58453China Mobile International LimitedUnclassifiedIPv444
AS34549meerfarbig GmbH & Co. KGHostingIPv4 IPv634

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS45552METASERV COMPANY LIMITEDUnclassifiedIPv4192
AS142211DCNET TELECOMUnclassifiedIPv460

Adjacency

Adjacent networks

All 48

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

ASNetworkTypeFamiliesPaths seen
AS6939Hurricane Electric LLCTransitIPv4 IPv61,103
AS4635Hong Kong Internet Exchange--Route Server 1UnclassifiedIPv4486
AS24482SG.GSHostingIPv4 IPv6218
AS45552METASERV COMPANY LIMITEDUnclassifiedIPv4192
AS45903CMC Telecom Infrastructure CompanyResidentialIPv4 IPv6162
AS18403FPT Telecom CompanyResidentialIPv4135
AS2914NTT America, Inc.TransitIPv4 IPv6130
AS4637Telstra GlobalUnclassifiedIPv476
AS45899VNPT CorpMobileIPv4 IPv676
AS9304HGC Global Communications LimitedHostingIPv460

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.