bgpreport

Network · data from 2026-11-12

AS46764 UWI-OPEN-CAMPUS - University of the West Indies

Registry name: UWI-OPEN-CAMPUS - University of the West Indies, BB · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS46764, 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.
192.65.161.0/24 No ROA Nonecovered by 192.65.160.0/21 673 100% 67
192.65.163.0/24 No ROA Nonecovered by 192.65.160.0/21 673 100% 67
192.65.164.0/22 No ROA Nonecovered by 192.65.160.0/21 673 100% 67
2620:11c:1001::/48 No ROA Nonecovered by 2620:11c:1000::/40 635 100% 67

AS-SET

AS46764 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 10 are in fix.csv.

  • ROA: none4
  • Route object: none4
  • Route object: not announced2
ChangePrefix or setDetailFull-table peers
ROA: none192.65.161.0/24No ROA covers it. Add a ROA for AS46764, maxLength 24.673 of 673
Route object: none192.65.161.0/24No route object for it. A route object for 192.65.160.0/21 with origin AS46764 covers it (filters allowing more-specifics accept it). Add a route object with origin AS46764 in the RIR database for the space.673 of 673
ROA: none192.65.163.0/24No ROA covers it. Add a ROA for AS46764, maxLength 24.673 of 673
Route object: none192.65.163.0/24No route object for it. A route object for 192.65.160.0/21 with origin AS46764 covers it (filters allowing more-specifics accept it). Add a route object with origin AS46764 in the RIR database for the space.673 of 673
ROA: none192.65.164.0/22No ROA covers it. Add a ROA for AS46764, maxLength 22.673 of 673
Route object: none192.65.164.0/22No route object for it. A route object for 192.65.160.0/21 with origin AS46764 covers it (filters allowing more-specifics accept it). Add a route object with origin AS46764 in the RIR database for the space.673 of 673
ROA: none2620:11c:1001::/48No ROA covers it. Add a ROA for AS46764, maxLength 48.635 of 636
Route object: none2620:11c:1001::/48No route object for it. A route object for 2620:11c:1000::/40 with origin AS46764 covers it (filters allowing more-specifics accept it). Add a route object with origin AS46764 in the RIR database for the space.635 of 636

Route objects not announced

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

192.65.160.0/21NTTCOMNo ROA
2620:11c:1000::/40RADBNo ROA

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.