asn.dev

Observed topology

AS4641 HKIX-AS-AP The Hong Kong Internet Exchange Limited

Unclassified APNIC

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS4641: 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
AS2914NTT America, Inc.TransitIPv4 IPv6104
AS6939Hurricane Electric LLCTransitIPv4 IPv652
AS6453TATA COMMUNICATIONS (AMERICA) INCTransitIPv4 IPv644
AS4635Hong Kong Internet Exchange--Route Server 1UnclassifiedIPv44
AS24482SG.GSHostingIPv4 IPv63
AS8359MTS PJSCMobileIPv42
AS55720Gigabit Hosting Sdn BhdHostingIPv42

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS38345Internet Domain Name System Beijing Engineering Resrarch Center Ltd.UnclassifiedIPv4 IPv6229
AS24149Internet Domain Name System Beijing Engineering Resrarch Center Ltd.UnclassifiedIPv4 IPv689

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS2914NTT America, Inc.TransitIPv4 IPv6243
AS38345Internet Domain Name System Beijing Engineering Resrarch Center Ltd.UnclassifiedIPv4 IPv6229
AS6453TATA COMMUNICATIONS (AMERICA) INCTransitIPv4 IPv6203
AS24149Internet Domain Name System Beijing Engineering Resrarch Center Ltd.UnclassifiedIPv4 IPv689
AS6939Hurricane Electric LLCTransitIPv4 IPv652
AS24482SG.GSHostingIPv4 IPv613
AS55720Gigabit Hosting Sdn BhdHostingIPv412
AS4635Hong Kong Internet Exchange--Route Server 1UnclassifiedIPv44
AS8359MTS PJSCMobileIPv42

Provenance

Where this comes from

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