asn.dev

Observed topology

AS139977 PRISMA-AS-ID - PT PRISMA MEDIA NUSANTARA

Residential RIPE Cable/DSL/ISP

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS139977: 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
AS55818MC-IX Matrix Internet Exchange RS-1ResidentialIPv4 IPv6792
AS147094PT. MITRA VISIONER PRATAMAUnclassifiedIPv4 IPv6160
AS45147PT. NAP Info Lintas NusaUnclassifiedIPv484
AS24482SG.GSHostingIPv4 IPv631

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS149909PT Panjalu Sarana Data IndonesiaResidentialIPv42
AS153961PT Connexa Digital NetworkUnclassifiedIPv42

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS55818MC-IX Matrix Internet Exchange RS-1ResidentialIPv4 IPv6792
AS147094PT. MITRA VISIONER PRATAMAUnclassifiedIPv4 IPv6160
AS45147PT. NAP Info Lintas NusaUnclassifiedIPv484
AS24482SG.GSHostingIPv4 IPv635
AS149909PT Panjalu Sarana Data IndonesiaResidentialIPv42
AS153961PT Connexa Digital NetworkUnclassifiedIPv42

Provenance

Where this comes from

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