asn.dev

Observed topology

AS140469 WANET-AS-ID PT Wahyu Adidaya Network

Residential ARIN

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS140469: 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
AS137366PT iForte Solusi Infotek - NAPUnclassifiedIPv4133
AS136106PT. Mega Akses PersadaResidentialIPv4122
AS38158PT. Cyberindo AditamaUnclassifiedIPv4 IPv6112
AS4800PT Aplikanusa LintasartaHostingIPv4104
AS134654PT Datautama Dinamika - NAPUnclassifiedIPv411
AS24482SG.GSHostingIPv4 IPv65
AS140443PT Herza Digital IndonesiaHostingIPv42
AS137367PT iForte Solusi InfotekResidentialIPv41

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS138876CV. SaranaindoUnclassifiedIPv4124
AS149703SMK Negeri 5 MalangUnclassifiedIPv465
AS155017PT Saviel Network IndonesiaUnclassifiedIPv634

Adjacency

Adjacent networks

All 11

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

ASNetworkTypeFamiliesPaths seen
AS38158PT. Cyberindo AditamaUnclassifiedIPv4 IPv6236
AS137366PT iForte Solusi Infotek - NAPUnclassifiedIPv4 IPv6220
AS138876CV. SaranaindoUnclassifiedIPv4124
AS136106PT. Mega Akses PersadaResidentialIPv4122
AS4800PT Aplikanusa LintasartaHostingIPv4104
AS149703SMK Negeri 5 MalangUnclassifiedIPv465
AS155017PT Saviel Network IndonesiaUnclassifiedIPv634
AS134654PT Datautama Dinamika - NAPUnclassifiedIPv4 IPv622
AS24482SG.GSHostingIPv4 IPv66
AS140443PT Herza Digital IndonesiaHostingIPv42

Provenance

Where this comes from

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