bgpreport

Network · data from 2026-11-12

AS52314 UNNOBA

Registry name: AS52314 - Universidad Nacional del Noroeste de Buenos Aires (UNNOBA), AR · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS52314, 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.
200.124.176.0/24 Valid Nonecovered by 200.124.176.0/21 669 99% 67
200.124.177.0/24 Valid Nonecovered by 200.124.176.0/21 669 99% 67
200.124.178.0/24 Valid Nonecovered by 200.124.176.0/21 669 99% 67
200.124.179.0/24 Valid Nonecovered by 200.124.176.0/21 669 99% 67
200.124.180.0/24 Valid Nonecovered by 200.124.176.0/21 669 99% 67
200.124.181.0/24 Valid Nonecovered by 200.124.176.0/21 669 99% 67
200.124.182.0/24 Valid Nonecovered by 200.124.176.0/21 669 99% 67
200.124.183.0/24 Valid Nonecovered by 200.124.176.0/21 669 99% 67
200.14.116.0/24 Valid RIR databaseLACNIC 671 100% 66
200.124.176.0/21 Valid RIR databaseLACNIC 666 99% 67
2801:0:140::/48 Valid RIR databaseLACNIC 629 99% 67
170.210.222.0/24 Valid RIR databaseLACNIC 103 15% 41

AS-SET

AS52314'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 8 are in fix.csv.

  • Route object: none8
ChangePrefix or setDetailFull-table peers
Route object: none200.124.176.0/24No route object for it. A route object for 200.124.176.0/21 with origin AS52314 covers it (filters allowing more-specifics accept it). Add a route object with origin AS52314 in the RIR database for the space.669 of 673
Route object: none200.124.177.0/24No route object for it. A route object for 200.124.176.0/21 with origin AS52314 covers it (filters allowing more-specifics accept it). Add a route object with origin AS52314 in the RIR database for the space.669 of 673
Route object: none200.124.178.0/24No route object for it. A route object for 200.124.176.0/21 with origin AS52314 covers it (filters allowing more-specifics accept it). Add a route object with origin AS52314 in the RIR database for the space.669 of 673
Route object: none200.124.179.0/24No route object for it. A route object for 200.124.176.0/21 with origin AS52314 covers it (filters allowing more-specifics accept it). Add a route object with origin AS52314 in the RIR database for the space.669 of 673
Route object: none200.124.180.0/24No route object for it. A route object for 200.124.176.0/21 with origin AS52314 covers it (filters allowing more-specifics accept it). Add a route object with origin AS52314 in the RIR database for the space.669 of 673
Route object: none200.124.181.0/24No route object for it. A route object for 200.124.176.0/21 with origin AS52314 covers it (filters allowing more-specifics accept it). Add a route object with origin AS52314 in the RIR database for the space.669 of 673
Route object: none200.124.182.0/24No route object for it. A route object for 200.124.176.0/21 with origin AS52314 covers it (filters allowing more-specifics accept it). Add a route object with origin AS52314 in the RIR database for the space.669 of 673
Route object: none200.124.183.0/24No route object for it. A route object for 200.124.176.0/21 with origin AS52314 covers it (filters allowing more-specifics accept it). Add a route object with origin AS52314 in the RIR database for the space.669 of 673

Route objects not announced

Every route object with origin AS52314 is announced.

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.