asn.dev

Observed topology

AS142332 TELNETINDONESIA-AS-ID - Telnet Indonesia

Residential RIPE

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS142332: 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 IndonesiaUnclassifiedIPv4 IPv6229
AS147094PT. MITRA VISIONER PRATAMAUnclassifiedIPv4109
AS7713PT Telekomunikasi IndonesiaResidentialIPv459
AS131111PT Mora Telematika IndonesiaUnclassifiedIPv4 IPv65
AS138128PT Solnet IndonesiaUnclassifiedIPv42

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS138124Universitas SamudraUnclassifiedIPv464

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS23947PT.Mora Telematika IndonesiaUnclassifiedIPv4 IPv6229
AS147094PT. MITRA VISIONER PRATAMAUnclassifiedIPv4173
AS138124Universitas SamudraUnclassifiedIPv464
AS7713PT Telekomunikasi IndonesiaResidentialIPv459
AS131111PT Mora Telematika IndonesiaUnclassifiedIPv4 IPv65
AS138128PT Solnet IndonesiaUnclassifiedIPv42

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.