asn.dev

Observed topology

AS58944 Telekomunikasi Indonesia International (HongKong) Limited

Residential APNIC

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS58944: 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.

No upstream observed. Typical for a tier-1 network that buys transit from nobody.

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS134835Starry Network LimitedUnclassifiedIPv4282
AS138959Telekomunikasi Indonesia International (Hong Kong) LimitedUnclassifiedIPv4236
AS6134XNNET LLCHostingIPv458
AS46559ZGX US LLCUnclassifiedIPv458

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS7713PT Telekomunikasi IndonesiaResidentialIPv4650
AS134835Starry Network LimitedUnclassifiedIPv4282
AS138959Telekomunikasi Indonesia International (Hong Kong) LimitedUnclassifiedIPv4236
AS6134XNNET LLCHostingIPv458
AS46559ZGX US LLCUnclassifiedIPv458
AS4635Hong Kong Internet Exchange--Route Server 1UnclassifiedIPv446
AS24482SG.GSHostingIPv46

Provenance

Where this comes from

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