asn.dev

Observed topology

AS147155 IDNIC-GATEWAYNET-AS-ID PT Gateway Internet Indonesia

Residential ARIN

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS147155: 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
AS38158PT. Cyberindo AditamaUnclassifiedIPv437
AS55685PT Jala Lintas MediaUnclassifiedIPv428
AS24482SG.GSHostingIPv41

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS59147PT. Drupadi PrimaHostingIPv4202
AS140433PT. Colo Media NetindoUnclassifiedIPv4132
AS138868CV. RUMAH CLOUD INDONESIAUnclassifiedIPv466
AS150556CV KLIK FARM INDONESIAUnclassifiedIPv466
AS152433CV Klik Server IndonesiaUnclassifiedIPv466

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS38158PT. Cyberindo AditamaUnclassifiedIPv4311
AS55685PT Jala Lintas MediaUnclassifiedIPv4279
AS59147PT. Drupadi PrimaHostingIPv4202
AS140433PT. Colo Media NetindoUnclassifiedIPv4132
AS138868CV. RUMAH CLOUD INDONESIAUnclassifiedIPv466
AS150556CV KLIK FARM INDONESIAUnclassifiedIPv466
AS152433CV Klik Server IndonesiaUnclassifiedIPv466
AS24482SG.GSHostingIPv48

Provenance

Where this comes from

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