asn.dev

Observed topology

AS58820 IDNIC-PTAMI-AS-ID APIK Media Networks

Hosting ARIN Content

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS58820: 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 IPv6641
AS6939Hurricane Electric LLCTransitIPv436
AS24482SG.GSHostingIPv411
AS24213PT. Arsen Kusuma IndonesiaUnclassifiedIPv410
AS35280F5 Networks SARLHostingIPv43

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS24213PT. Arsen Kusuma IndonesiaUnclassifiedIPv4 IPv6111
AS140476PT Ardi Jaya SolusindoUnclassifiedIPv474
AS63515Indonesia Network Information CenterUnclassifiedIPv425
AS4434PT Rahajasa Media InternetResidentialIPv47
AS139983PT. Borneo Cakrawala MediaUnclassifiedIPv42
AS141584PT Jetorbit Teknologi IndonesiaHostingIPv41

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS38158PT. Cyberindo AditamaUnclassifiedIPv4 IPv6889
AS24213PT. Arsen Kusuma IndonesiaUnclassifiedIPv4 IPv6161
AS140476PT Ardi Jaya SolusindoUnclassifiedIPv474
AS6939Hurricane Electric LLCTransitIPv436
AS63515Indonesia Network Information CenterUnclassifiedIPv425
AS24482SG.GSHostingIPv417
AS4434PT Rahajasa Media InternetResidentialIPv47
AS35280F5 Networks SARLHostingIPv47
AS139983PT. Borneo Cakrawala MediaUnclassifiedIPv42
AS141584PT Jetorbit Teknologi IndonesiaHostingIPv41

Provenance

Where this comes from

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