asn.dev

Observed topology

AS142381 IDNIC-MACTEL-AS-ID PT Media Access Telematika

Unclassified RIPE Cable/DSL/ISP

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS142381: 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
AS23947PT.Mora Telematika IndonesiaUnclassifiedIPv4198
AS136106PT. Mega Akses PersadaResidentialIPv4122
AS131111PT Mora Telematika IndonesiaUnclassifiedIPv43

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS152083Dinas Komunikasi dan Informatika Kabupaten CiamisUnclassifiedIPv465

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS23947PT.Mora Telematika IndonesiaUnclassifiedIPv4198
AS136106PT. Mega Akses PersadaResidentialIPv4125
AS152083Dinas Komunikasi dan Informatika Kabupaten CiamisUnclassifiedIPv465
AS38783PT. Simaya Jejaring MandiriResidentialIPv456
AS131717PT Citra Jelajah InformatikaResidentialIPv46
AS131111PT Mora Telematika IndonesiaUnclassifiedIPv43

Provenance

Where this comes from

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