bgpreport

Network · data from 2026-11-12

AS264683 UNNOBA-Pergamino

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

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS264683, 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.

168.227.24.0/24 Valid Other IRR onlyRADB 673 100% 66
168.227.25.0/24 Valid Other IRR onlyRADB 673 100% 66
168.227.26.0/24 Valid Other IRR onlyRADB 673 100% 66
168.227.27.0/24 Valid Other IRR onlyRADB 673 100% 66
168.227.24.0/22 Valid RIR databaseLACNIC 670 100% 67
2801:0:141::/48 Valid RIR databaseLACNIC, RADB 319 50% 65

AS-SET

AS264683'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 4 are in fix.csv.

  • Route object: RIR4
ChangePrefix or setDetailFull-table peers
Route object: RIR168.227.24.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR168.227.25.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR168.227.26.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR168.227.27.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673

Route objects not announced

Every route object with origin AS264683 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.