asn.dev

Observed topology

AS60391 PRMG Papa-Razzi Media Group A.s.b.l.

Unclassified RIPE Non-Profit

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS60391: 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
AS34872Sarah Rossius trading as Servperso SystemsHostingIPv6217
AS41273Antenne Collective Ettelbruck ASBLUnclassifiedIPv614
AS24482SG.GSHostingIPv67
AS56662Marcin GondekUnclassifiedIPv67
AS58057Securebit AGUnclassifiedIPv67
AS199854Jens ThiesUnclassifiedIPv67
AS401753BIXCE IncUnclassifiedIPv67

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS15780Luxembourg Amateur Radio Union, A.s.b.l.UnclassifiedIPv4 IPv6249

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS34872Sarah Rossius trading as Servperso SystemsHostingIPv4 IPv6383
AS15780Luxembourg Amateur Radio Union, A.s.b.l.UnclassifiedIPv4 IPv6249
AS41273Antenne Collective Ettelbruck ASBLUnclassifiedIPv4 IPv670
AS24482SG.GSHostingIPv4 IPv613
AS401753BIXCE IncUnclassifiedIPv4 IPv613
AS56662Marcin GondekUnclassifiedIPv612
AS58057Securebit AGUnclassifiedIPv612
AS199854Jens ThiesUnclassifiedIPv612

Provenance

Where this comes from

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