asn.dev

Observed topology

AS58411 GTDCL-HK - Unit A-E, 13/F, Golden Sun Centre,

Unclassified APNIC

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS58411: 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
AS10103HK Broadband Network Ltd.ResidentialIPv4628
AS6939Hurricane Electric LLCTransitIPv4347
AS10099China Unicom GlobalUnclassifiedIPv4 IPv6171
AS58807China Mobile International LimitedMobileIPv4165
AS24482SG.GSHostingIPv4 IPv6161
AS58453China Mobile International LimitedUnclassifiedIPv468
AS3491PCCW Global (HK) Ltd.TransitIPv448

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS10103HK Broadband Network Ltd.ResidentialIPv4628
AS6939Hurricane Electric LLCTransitIPv4347
AS10099China Unicom GlobalUnclassifiedIPv4 IPv6171
AS58807China Mobile International LimitedMobileIPv4165
AS24482SG.GSHostingIPv4 IPv6161
AS58453China Mobile International LimitedUnclassifiedIPv468
AS3491PCCW Global (HK) Ltd.TransitIPv448

Provenance

Where this comes from

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