bgpreport

Network · data from 2026-11-12

AS37373 Ashesi University College - Ashesi University College

Registry name: Ashesi University College - Ashesi University College, GH · not in PeeringDB

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

Announced routes

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

41.79.96.0/24 No ROA Nonecovered by 41.79.96.0/22 673 100% 67
41.79.97.0/24 No ROA Nonecovered by 41.79.96.0/22 673 100% 67
41.79.98.0/24 No ROA Nonecovered by 41.79.96.0/22 673 100% 67
41.79.99.0/24 No ROA Nonecovered by 41.79.96.0/22 673 100% 67
41.79.96.0/22 No ROA Other IRR onlyRIPE-NONAUTH 673 100% 67
196.13.192.0/21 No ROA RIR databaseAFRINIC, RADB 673 100% 67

AS-SET

AS37373 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 26 are in fix.csv.

  • ROA: none6
  • Route object: none4
  • Route object: RIR1
  • Route object: not announced15
ChangePrefix or setDetailFull-table peers
ROA: none41.79.96.0/24No ROA covers it. Add a ROA for AS37373, maxLength 24.673 of 673
Route object: none41.79.96.0/24No route object for it. A route object for 41.79.96.0/22 with origin AS37373 covers it (filters allowing more-specifics accept it). Add a route object with origin AS37373 in the RIR database for the space.673 of 673
ROA: none41.79.97.0/24No ROA covers it. Add a ROA for AS37373, maxLength 24.673 of 673
Route object: none41.79.97.0/24No route object for it. A route object for 41.79.96.0/22 with origin AS37373 covers it (filters allowing more-specifics accept it). Add a route object with origin AS37373 in the RIR database for the space.673 of 673
ROA: none41.79.98.0/24No ROA covers it. Add a ROA for AS37373, maxLength 24.673 of 673
Route object: none41.79.98.0/24No route object for it. A route object for 41.79.96.0/22 with origin AS37373 covers it (filters allowing more-specifics accept it). Add a route object with origin AS37373 in the RIR database for the space.673 of 673
ROA: none41.79.99.0/24No ROA covers it. Add a ROA for AS37373, maxLength 24.673 of 673
Route object: none41.79.99.0/24No route object for it. A route object for 41.79.96.0/22 with origin AS37373 covers it (filters allowing more-specifics accept it). Add a route object with origin AS37373 in the RIR database for the space.673 of 673
ROA: none41.79.96.0/22No ROA covers it. Add a ROA for AS37373, maxLength 22.673 of 673
Route object: RIR41.79.96.0/22Route object only in RIPE-NONAUTH. Add it in the RIR database for the space.673 of 673
ROA: none196.13.192.0/21No ROA covers it. Add a ROA for AS37373, maxLength 21.673 of 673

Route objects not announced

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

196.13.192.0/22RADBNo ROA
196.13.192.0/23RADBNo ROA
196.13.192.0/24RADBNo ROA
196.13.193.0/24RADBNo ROA
196.13.194.0/23RADBNo ROA
196.13.194.0/24RADBNo ROA
196.13.195.0/24RADBNo ROA
196.13.196.0/22RADBNo ROA
196.13.196.0/23RADBNo ROA
196.13.196.0/24RADBNo ROA
196.13.197.0/24RADBNo ROA
196.13.198.0/23RADBNo ROA
196.13.198.0/24RADBNo ROA
196.13.199.0/24RADBNo ROA
2c0f:fa00::/32AFRINIC, RIPE-NONAUTHNo 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.