asn.dev

Observed topology

AS58376 AKGU-AS-ID - PT Angkasa Komunikasi Global Utama

Unclassified ARIN

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS58376: 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
AS38158PT. Cyberindo AditamaUnclassifiedIPv4 IPv6854
AS56258PT. PGAS TELEKOMUNIKASI NUSANTARAUnclassifiedIPv4113
AS24482SG.GSHostingIPv4 IPv617
AS6939Hurricane Electric LLCTransitIPv49
AS147168PT NTT IndonesiaUnclassifiedIPv46
AS9002RETN LimitedUnclassifiedIPv41
AS35280F5 Networks SARLHostingIPv41

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS136872PT Global Digital NiagaUnclassifiedIPv465

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS38158PT. Cyberindo AditamaUnclassifiedIPv4 IPv6915
AS56258PT. PGAS TELEKOMUNIKASI NUSANTARAUnclassifiedIPv4113
AS136872PT Global Digital NiagaUnclassifiedIPv465
AS24482SG.GSHostingIPv4 IPv618
AS6939Hurricane Electric LLCTransitIPv49
AS147168PT NTT IndonesiaUnclassifiedIPv48
AS9002RETN LimitedUnclassifiedIPv41
AS35280F5 Networks SARLHostingIPv41

Provenance

Where this comes from

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