asn.dev

Observed topology

AS17440 SAANET-AS-ID - PT Sinar Alam Abadi

Residential ARIN

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS17440: 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 AditamaUnclassifiedIPv4230
AS24534PT. Transhybrid CommunicationUnclassifiedIPv458
AS147094PT. MITRA VISIONER PRATAMAUnclassifiedIPv423
AS24482SG.GSHostingIPv43
AS23679PT. Media Antar NusaUnclassifiedIPv41

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS141638Yayasan Lembaga Pengembangan Perbankan IndonesiaUnclassifiedIPv44
AS147159PT Beibi Cemerlang IndonesiaUnclassifiedIPv43

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS38158PT. Cyberindo AditamaUnclassifiedIPv4230
AS24534PT. Transhybrid CommunicationUnclassifiedIPv458
AS147094PT. MITRA VISIONER PRATAMAUnclassifiedIPv423
AS24482SG.GSHostingIPv47
AS141638Yayasan Lembaga Pengembangan Perbankan IndonesiaUnclassifiedIPv44
AS147159PT Beibi Cemerlang IndonesiaUnclassifiedIPv43
AS64315PT MITRA VISIONER PRATAMAUnclassifiedIPv42
AS4787PT Cyberindo AditamaResidentialIPv41
AS23679PT. Media Antar NusaUnclassifiedIPv41

Provenance

Where this comes from

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