asn.dev

Observed topology

AS142382 IDNIC-JNHOST-AS-ID PT Klinik Digital Indonesia JNHOST

Unclassified ARIN

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS142382: 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
AS137366PT iForte Solusi Infotek - NAPUnclassifiedIPv4 IPv6247
AS136106PT. Mega Akses PersadaResidentialIPv460
AS64313PT. NAP Info Lintas NusaUnclassifiedIPv4 IPv645
AS38158PT. Cyberindo AditamaUnclassifiedIPv4 IPv629
AS24482SG.GSHostingIPv44
AS141137PT Media Cepat IndonesiaUnclassifiedIPv44
AS23947PT.Mora Telematika IndonesiaUnclassifiedIPv42

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS152349PT Majapahit Network IndonesiaUnclassifiedIPv466

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS137366PT iForte Solusi Infotek - NAPUnclassifiedIPv4 IPv6310
AS152349PT Majapahit Network IndonesiaUnclassifiedIPv466
AS136106PT. Mega Akses PersadaResidentialIPv460
AS64313PT. NAP Info Lintas NusaUnclassifiedIPv4 IPv645
AS38158PT. Cyberindo AditamaUnclassifiedIPv4 IPv629
AS24482SG.GSHostingIPv45
AS23947PT.Mora Telematika IndonesiaUnclassifiedIPv44
AS141137PT Media Cepat IndonesiaUnclassifiedIPv44

Provenance

Where this comes from

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