asn.dev

Observed topology

AS152435 IDNIC-KONNEK-AS-ID - PT Konnek Jaya Bersama

Unclassified APNIC Cable/DSL/ISP

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS152435: 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
AS133095PT Pusat Fiber IndonesiaUnclassifiedIPv4 IPv6216
AS150506PT Pusat Fiber IndonesiaUnclassifiedIPv4 IPv68
AS24482SG.GSHostingIPv43
AS63516Transhybrid Internet XchangeUnclassifiedIPv61
AS138089PT.Global Media Data PrimaResidentialIPv61

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS152761PT AJI RAFASYA ROSO ANTENG BERKAHUnclassifiedIPv46
AS154527PT Mikrolink Elektra DataUnclassifiedIPv46
AS152393PT Gaisar Teknologi BersamaUnclassifiedIPv42

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS133095PT Pusat Fiber IndonesiaUnclassifiedIPv4 IPv6216
AS24482SG.GSHostingIPv49
AS150506PT Pusat Fiber IndonesiaUnclassifiedIPv4 IPv68
AS152761PT AJI RAFASYA ROSO ANTENG BERKAHUnclassifiedIPv46
AS154527PT Mikrolink Elektra DataUnclassifiedIPv46
AS138089PT.Global Media Data PrimaResidentialIPv4 IPv63
AS152393PT Gaisar Teknologi BersamaUnclassifiedIPv42
AS63516Transhybrid Internet XchangeUnclassifiedIPv61

Provenance

Where this comes from

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