asn.dev

Observed topology

AS139460 MMS-AS-ID - PT Maxindo Mitra Solusi

Unclassified APNIC

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS139460: 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
AS38320PT Maxindo Mitra SolusiUnclassifiedIPv4659
AS136106PT. Mega Akses PersadaResidentialIPv4297
AS7713PT Telekomunikasi IndonesiaResidentialIPv480
AS23947PT.Mora Telematika IndonesiaUnclassifiedIPv461
AS137375PT Internet Solusi PrimaUnclassifiedIPv458
AS131111PT Mora Telematika IndonesiaUnclassifiedIPv411

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS137360Universitas Muhammadiyah SurabayaUnclassifiedIPv41

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS38320PT Maxindo Mitra SolusiUnclassifiedIPv4659
AS136106PT. Mega Akses PersadaResidentialIPv4298
AS7713PT Telekomunikasi IndonesiaResidentialIPv480
AS23947PT.Mora Telematika IndonesiaUnclassifiedIPv461
AS137375PT Internet Solusi PrimaUnclassifiedIPv458
AS131111PT Mora Telematika IndonesiaUnclassifiedIPv411
AS137360Universitas Muhammadiyah SurabayaUnclassifiedIPv41

Provenance

Where this comes from

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