asn.dev

Observed topology

AS149359 IDNIC-PDM-AS-ID - PT Persada Data Multimedia

Unclassified ARIN

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS149359: 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
AS136106PT. Mega Akses PersadaResidentialIPv4 IPv6627
AS38158PT. Cyberindo AditamaUnclassifiedIPv4293
AS58389PT Sumber Data IndonesiaUnclassifiedIPv490
AS141913PT Global Media Telekomunikasi NetworkUnclassifiedIPv448
AS24482SG.GSHostingIPv48

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS147161Universitas Muhammadiyah GresikUnclassifiedIPv463
AS141913PT Global Media Telekomunikasi NetworkUnclassifiedIPv411
AS151588PT Arjuna Lancar TeknologiResidentialIPv46

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS136106PT. Mega Akses PersadaResidentialIPv4 IPv6639
AS38158PT. Cyberindo AditamaUnclassifiedIPv4344
AS58389PT Sumber Data IndonesiaUnclassifiedIPv498
AS147161Universitas Muhammadiyah GresikUnclassifiedIPv463
AS141913PT Global Media Telekomunikasi NetworkUnclassifiedIPv459
AS24482SG.GSHostingIPv410
AS4787PT Cyberindo AditamaResidentialIPv47
AS151588PT Arjuna Lancar TeknologiResidentialIPv46

Provenance

Where this comes from

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