bgpreport

Network · data from 2026-11-12

AS52291 Coop. Provincia de Serv. Publicos y Comunitarios de Neuquen LTDA.

Registry name: AS52291 - Coop. Provincia de Serv. Publicos y Comunitarios de Neuquen LTDA., AR · PeeringDB

6IPv4 routes 66.7% RPKI valid · 16.7% with a route object
1IPv6 routes 100.0% RPKI valid · 100.0% with a route object
0RPKI invalid 0 origin · 0 maxLength
2No ROA 5 with no route object for this origin
0Low visibility seen by under 10% of full-table peers
1Route objects not announced registered with origin AS52291, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS52291, things to look at first. Visibility = full-table peers that see it, of 673 (IPv4) and 636 (IPv6) on 75 collectors. Also as routes.csv.

38.51.23.0/24 No ROA None 668 99% 67
38.51.20.0/24 No ROA Other IRR onlyRADB 668 99% 66
190.111.124.0/24 Valid Nonecovered by 190.111.124.0/22 669 99% 66
190.111.125.0/24 Valid Nonecovered by 190.111.124.0/22 669 99% 66
190.111.126.0/24 Valid Nonecovered by 190.111.124.0/22 669 99% 66
190.111.127.0/24 Valid Nonecovered by 190.111.124.0/22 669 99% 66
2803:3950::/32 Valid Other IRR onlyRADB 633 100% 69

AS-SET

AS52291's PeeringDB record names no AS-SET.

Fix list

The changes that would bring RPKI, the IRR and what's announced into line. Some are deliberate (a route object kept for a backup route, say); the network decides. All 10 are in fix.csv.

  • ROA: none2
  • Route object: none5
  • Route object: RIR2
  • Route object: not announced1
ChangePrefix or setDetailFull-table peers
ROA: none38.51.23.0/24No ROA covers it. Add a ROA for AS52291, maxLength 24.668 of 673
Route object: none38.51.23.0/24No route object for it. Add a route object with origin AS52291 in the RIR database for the space.668 of 673
ROA: none38.51.20.0/24No ROA covers it. Add a ROA for AS52291, maxLength 24.668 of 673
Route object: RIR38.51.20.0/24Route object only in RADB. Add it in the RIR database for the space.668 of 673
Route object: none190.111.124.0/24No route object for it. A route object for 190.111.124.0/22 with origin AS52291 covers it (filters allowing more-specifics accept it). Add a route object with origin AS52291 in the RIR database for the space.669 of 673
Route object: none190.111.125.0/24No route object for it. A route object for 190.111.124.0/22 with origin AS52291 covers it (filters allowing more-specifics accept it). Add a route object with origin AS52291 in the RIR database for the space.669 of 673
Route object: none190.111.126.0/24No route object for it. A route object for 190.111.124.0/22 with origin AS52291 covers it (filters allowing more-specifics accept it). Add a route object with origin AS52291 in the RIR database for the space.669 of 673
Route object: none190.111.127.0/24No route object for it. A route object for 190.111.124.0/22 with origin AS52291 covers it (filters allowing more-specifics accept it). Add a route object with origin AS52291 in the RIR database for the space.669 of 673
Route object: RIR2803:3950::/32Route object only in RADB. Add it in the RIR database for the space.633 of 636

Route objects not announced

Route objects with origin AS52291 whose prefix no peer sees AS52291 announce. Many are kept on purpose (backup routes, space announced only in some places).

190.111.124.0/22RADBValid

Routes: the 08:00 UTC snapshots of 2026-11-12 from 75 RIPE RIS and RouteViews collectors. RPKI: our rpki-client run before the snapshot. IRR: the day's dumps of the five RIR databases and RADB's mirrors. The LEVEL3 and IDNIC databases publish no dump and aren't read, so route objects only there count as none.