bgpreport

Network · data from 2026-11-12

AS7965 AS7965 - Universidad Catolica Andres Bello

Registry name: AS7965 - Universidad Catolica Andres Bello, VE · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS7965, 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.2.11.0/24 Valid Nonecovered by 200.2.8.0/21 670 100% 67
200.2.8.0/24 Valid Nonecovered by 200.2.8.0/21 669 99% 67
200.2.9.0/24 Valid Nonecovered by 200.2.8.0/21 669 99% 67
200.2.12.0/24 Valid Nonecovered by 200.2.8.0/21 669 99% 67
200.2.14.0/24 Valid Nonecovered by 200.2.8.0/21 669 99% 67
200.2.15.0/24 Valid Nonecovered by 200.2.8.0/21 669 99% 67
200.2.13.0/24 Valid Nonecovered by 200.2.8.0/21 668 99% 67
200.2.8.0/21 Valid RIR databaseLACNIC 669 99% 67

AS-SET

AS7965 isn't in PeeringDB, where networks name their 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 7 are in fix.csv.

  • Route object: none7
ChangePrefix or setDetailFull-table peers
Route object: none200.2.11.0/24No route object for it. A route object for 200.2.8.0/21 with origin AS7965 covers it (filters allowing more-specifics accept it). Add a route object with origin AS7965 in the RIR database for the space.670 of 673
Route object: none200.2.8.0/24No route object for it. A route object for 200.2.8.0/21 with origin AS7965 covers it (filters allowing more-specifics accept it). Add a route object with origin AS7965 in the RIR database for the space.669 of 673
Route object: none200.2.9.0/24No route object for it. A route object for 200.2.8.0/21 with origin AS7965 covers it (filters allowing more-specifics accept it). Add a route object with origin AS7965 in the RIR database for the space.669 of 673
Route object: none200.2.12.0/24No route object for it. A route object for 200.2.8.0/21 with origin AS7965 covers it (filters allowing more-specifics accept it). Add a route object with origin AS7965 in the RIR database for the space.669 of 673
Route object: none200.2.14.0/24No route object for it. A route object for 200.2.8.0/21 with origin AS7965 covers it (filters allowing more-specifics accept it). Add a route object with origin AS7965 in the RIR database for the space.669 of 673
Route object: none200.2.15.0/24No route object for it. A route object for 200.2.8.0/21 with origin AS7965 covers it (filters allowing more-specifics accept it). Add a route object with origin AS7965 in the RIR database for the space.669 of 673
Route object: none200.2.13.0/24No route object for it. A route object for 200.2.8.0/21 with origin AS7965 covers it (filters allowing more-specifics accept it). Add a route object with origin AS7965 in the RIR database for the space.668 of 673

Route objects not announced

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