asn.dev

Observed topology

AS138106 LTN-AS-ID - PT Lintas Telematika Nusantara

Residential RIPE

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS138106: 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
AS147094PT. MITRA VISIONER PRATAMAUnclassifiedIPv4252
AS4800PT Aplikanusa LintasartaHostingIPv467
AS134654PT Datautama Dinamika - NAPUnclassifiedIPv48
AS24482SG.GSHostingIPv46
AS35280F5 Networks SARLHostingIPv42

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS136076PT Hesta Media SinergiUnclassifiedIPv4201
AS17671JETCOMS-ID Autonomous systemUnclassifiedIPv42

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS147094PT. MITRA VISIONER PRATAMAUnclassifiedIPv4441
AS136076PT Hesta Media SinergiUnclassifiedIPv4201
AS4800PT Aplikanusa LintasartaHostingIPv467
AS134654PT Datautama Dinamika - NAPUnclassifiedIPv417
AS24482SG.GSHostingIPv49
AS17671JETCOMS-ID Autonomous systemUnclassifiedIPv42
AS35280F5 Networks SARLHostingIPv42
AS7717OpenIXP ASNUnclassifiedIPv41
AS138089PT.Global Media Data PrimaResidentialIPv41

Provenance

Where this comes from

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