asn.dev

Observed topology

AS152419 IDNIC-BERBAURWIFI-AS-ID PT Berbaur Network Connected

Residential ARIN

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS152419: 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 AditamaUnclassifiedIPv463
AS24198PT. Datakom Padma Jaya (DatakomNAP)UnclassifiedIPv442
AS138089PT.Global Media Data PrimaResidentialIPv415
AS4787PT Cyberindo AditamaResidentialIPv42
AS23947PT.Mora Telematika IndonesiaUnclassifiedIPv42
AS24482SG.GSHostingIPv41

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS150934PT Hard Work Media Data TransUnclassifiedIPv42

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS38158PT. Cyberindo AditamaUnclassifiedIPv463
AS24198PT. Datakom Padma Jaya (DatakomNAP)UnclassifiedIPv442
AS138089PT.Global Media Data PrimaResidentialIPv415
AS4787PT Cyberindo AditamaResidentialIPv44
AS23947PT.Mora Telematika IndonesiaUnclassifiedIPv42
AS150934PT Hard Work Media Data TransUnclassifiedIPv42
AS24482SG.GSHostingIPv41

Provenance

Where this comes from

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