asn.dev

Observed topology

AS152377 IDNIC-TRITAMA-AS-ID PT Trimitra Aditama Koneksindo

Residential ARIN Cable/DSL/ISP

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS152377: 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 IPv6465
AS38158PT. Cyberindo AditamaUnclassifiedIPv4 IPv696
AS147168PT NTT IndonesiaUnclassifiedIPv415
AS24482SG.GSHostingIPv4 IPv614
AS150506PT Pusat Fiber IndonesiaUnclassifiedIPv611
AS4787PT Cyberindo AditamaResidentialIPv61

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS201488Ahmad Hanif Ihlasul AmalUnclassifiedIPv637

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS133095PT Pusat Fiber IndonesiaUnclassifiedIPv4 IPv6465
AS38158PT. Cyberindo AditamaUnclassifiedIPv4 IPv6131
AS201488Ahmad Hanif Ihlasul AmalUnclassifiedIPv637
AS147168PT NTT IndonesiaUnclassifiedIPv415
AS24482SG.GSHostingIPv4 IPv614
AS150506PT Pusat Fiber IndonesiaUnclassifiedIPv611
AS4787PT Cyberindo AditamaResidentialIPv63

Provenance

Where this comes from

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