asn.dev

Observed topology

AS138064 JINOM-AS-ID - PT. Jinom Network Indonesia

Residential APNIC Cable/DSL/ISP

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS138064: 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
AS4800PT Aplikanusa LintasartaHostingIPv4351
AS24534PT. Transhybrid CommunicationUnclassifiedIPv4183
AS17451BIZNET NETWORKSResidentialIPv436
AS7713PT Telekomunikasi IndonesiaResidentialIPv414
AS9905Linknet ASNUnclassifiedIPv412
AS24482SG.GSHostingIPv46
AS63516Transhybrid Internet XchangeUnclassifiedIPv42
AS55685PT Jala Lintas MediaUnclassifiedIPv41

Transit

Downstream networks

inferred

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

No downstream observed. This network does not appear to carry transit for anyone.

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS4800PT Aplikanusa LintasartaHostingIPv4351
AS24534PT. Transhybrid CommunicationUnclassifiedIPv4183
AS17451BIZNET NETWORKSResidentialIPv436
AS7713PT Telekomunikasi IndonesiaResidentialIPv414
AS9905Linknet ASNUnclassifiedIPv412
AS24482SG.GSHostingIPv46
AS63516Transhybrid Internet XchangeUnclassifiedIPv42
AS55685PT Jala Lintas MediaUnclassifiedIPv41

Provenance

Where this comes from

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