asn.dev

Observed topology

AS215208 PRIMA

Unclassified RIPE

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS215208: 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
AS4800PT Aplikanusa LintasartaHostingIPv4132
AS140475PT Citra Celebas MultimediaResidentialIPv466
AS24482SG.GSHostingIPv42

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS140424DINAS KOMUNIKASI INFORMATIKA STATISTIK DAN PERSANDIAN PROVINSI SULAWESI SELATANResidentialIPv460
AS137339Dinas Komunikasi dan Informatika Kabupaten PinrangUnclassifiedIPv429
AS150283Dinas Komunikasi Informatika, Statistik dan Persandian Kabupaten GowaUnclassifiedIPv43

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS4800PT Aplikanusa LintasartaHostingIPv4135
AS7713PT Telekomunikasi IndonesiaResidentialIPv489
AS140475PT Citra Celebas MultimediaResidentialIPv466
AS140424DINAS KOMUNIKASI INFORMATIKA STATISTIK DAN PERSANDIAN PROVINSI SULAWESI SELATANResidentialIPv460
AS137339Dinas Komunikasi dan Informatika Kabupaten PinrangUnclassifiedIPv429
AS150283Dinas Komunikasi Informatika, Statistik dan Persandian Kabupaten GowaUnclassifiedIPv43
AS24482SG.GSHostingIPv42

Provenance

Where this comes from

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