bgpreport

Network · data from 2026-11-12

AS25242 kuwait-university KUWAIT UNIVERSITY

Registry name: kuwait-university KUWAIT UNIVERSITY, KW · not in PeeringDB

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

Announced routes

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

139.141.0.0/18 No ROA Nonecovered by 139.141.0.0/17 673 100% 67
139.141.32.0/20 No ROA Nonecovered by 139.141.32.0/19 673 100% 67
139.141.64.0/18 No ROA Nonecovered by 139.141.0.0/17 673 100% 67
139.141.100.0/22 No ROA Nonecovered by 139.141.0.0/17 673 100% 67
139.141.186.0/24 No ROA Nonecovered by 139.141.160.0/19 673 100% 67
139.141.192.0/18 No ROA Nonecovered by 139.141.128.0/17 673 100% 67
139.141.242.0/24 No ROA Nonecovered by 139.141.224.0/19 673 100% 67
139.141.243.0/24 No ROA Nonecovered by 139.141.224.0/19 673 100% 67
139.141.128.0/18 No ROA Other IRR onlyRADB 673 100% 67
139.141.0.0/16 No ROA RIR databaseRADB, RIPE 673 100% 67
139.141.160.0/19 No ROA RIR databaseRIPE 673 100% 67

AS-SET

AS25242 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 32 are in fix.csv.

  • ROA: none11
  • Route object: none8
  • Route object: RIR1
  • Route object: not announced12
ChangePrefix or setDetailFull-table peers
ROA: none139.141.0.0/18No ROA covers it. Add a ROA for AS25242, maxLength 18.673 of 673
Route object: none139.141.0.0/18No route object for it. A route object for 139.141.0.0/17 with origin AS25242 covers it (filters allowing more-specifics accept it). Add a route object with origin AS25242 in the RIR database for the space.673 of 673
ROA: none139.141.32.0/20No ROA covers it. Add a ROA for AS25242, maxLength 20.673 of 673
Route object: none139.141.32.0/20No route object for it. A route object for 139.141.32.0/19 with origin AS25242 covers it (filters allowing more-specifics accept it). Add a route object with origin AS25242 in the RIR database for the space.673 of 673
ROA: none139.141.64.0/18No ROA covers it. Add a ROA for AS25242, maxLength 18.673 of 673
Route object: none139.141.64.0/18No route object for it. A route object for 139.141.0.0/17 with origin AS25242 covers it (filters allowing more-specifics accept it). Add a route object with origin AS25242 in the RIR database for the space.673 of 673
ROA: none139.141.100.0/22No ROA covers it. Add a ROA for AS25242, maxLength 22.673 of 673
Route object: none139.141.100.0/22No route object for it. A route object for 139.141.0.0/17 with origin AS25242 covers it (filters allowing more-specifics accept it). Add a route object with origin AS25242 in the RIR database for the space.673 of 673
ROA: none139.141.186.0/24No ROA covers it. Add a ROA for AS25242, maxLength 24.673 of 673
Route object: none139.141.186.0/24No route object for it. A route object for 139.141.160.0/19 with origin AS25242 covers it (filters allowing more-specifics accept it). Add a route object with origin AS25242 in the RIR database for the space.673 of 673
ROA: none139.141.192.0/18No ROA covers it. Add a ROA for AS25242, maxLength 18.673 of 673
Route object: none139.141.192.0/18No route object for it. A route object for 139.141.128.0/17 with origin AS25242 covers it (filters allowing more-specifics accept it). Add a route object with origin AS25242 in the RIR database for the space.673 of 673
ROA: none139.141.242.0/24No ROA covers it. Add a ROA for AS25242, maxLength 24.673 of 673
Route object: none139.141.242.0/24No route object for it. A route object for 139.141.224.0/19 with origin AS25242 covers it (filters allowing more-specifics accept it). Add a route object with origin AS25242 in the RIR database for the space.673 of 673
ROA: none139.141.243.0/24No ROA covers it. Add a ROA for AS25242, maxLength 24.673 of 673
Route object: none139.141.243.0/24No route object for it. A route object for 139.141.224.0/19 with origin AS25242 covers it (filters allowing more-specifics accept it). Add a route object with origin AS25242 in the RIR database for the space.673 of 673
ROA: none139.141.128.0/18No ROA covers it. Add a ROA for AS25242, maxLength 18.673 of 673
Route object: RIR139.141.128.0/18Route object only in RADB. Add it in the RIR database for the space.673 of 673
ROA: none139.141.0.0/16No ROA covers it. Add a ROA for AS25242, maxLength 16.673 of 673
ROA: none139.141.160.0/19No ROA covers it. Add a ROA for AS25242, maxLength 19.673 of 673

Route objects not announced

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

139.141.0.0/17RADBNo ROA
139.141.0.0/19RIPENo ROA
139.141.0.0/24NTTCOM, RADBNo ROA
139.141.32.0/19RIPENo ROA
139.141.64.0/19RADB, RIPENo ROA
139.141.101.0/24RADBNo ROA
139.141.103.0/24NTTCOMNo ROA
139.141.105.0/24RADBNo ROA
139.141.128.0/17RADBNo ROA
139.141.128.0/19RIPENo ROA
139.141.224.0/19RADBNo ROA
139.141.224.0/20RADBNo 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.