asn.dev

Observed topology

AS142362 IDNIC-SUKMA-AS-ID PT Sukma Sejati Media

Unclassified RIPE

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS142362: 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
AS45147PT. NAP Info Lintas NusaUnclassifiedIPv4243
AS7713PT Telekomunikasi IndonesiaResidentialIPv459
AS138840PT. PARSAORAN GLOBAL DATATRANS - NAPUnclassifiedIPv48
AS147168PT NTT IndonesiaUnclassifiedIPv44
AS38001NewMedia Express Pte LtdHostingIPv43
AS24482SG.GSHostingIPv42

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS151595PT Merdeka Media TeknologiUnclassifiedIPv42

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS45147PT. NAP Info Lintas NusaUnclassifiedIPv4243
AS7713PT Telekomunikasi IndonesiaResidentialIPv459
AS138840PT. PARSAORAN GLOBAL DATATRANS - NAPUnclassifiedIPv48
AS147168PT NTT IndonesiaUnclassifiedIPv44
AS38001NewMedia Express Pte LtdHostingIPv43
AS7717OpenIXP ASNUnclassifiedIPv42
AS24482SG.GSHostingIPv42
AS151595PT Merdeka Media TeknologiUnclassifiedIPv42

Provenance

Where this comes from

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