bgpreport

Network · data from 2026-11-12

AS37191 Raya Holding - Raya Holding

Registry name: Raya Holding - Raya Holding, EG · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS37191, 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.78.20.0/24 No ROA Nonecovered by 41.78.20.0/22 673 100% 67
41.78.21.0/24 No ROA Nonecovered by 41.78.20.0/22 673 100% 67
41.78.22.0/24 No ROA Nonecovered by 41.78.20.0/22 673 100% 67
41.78.23.0/24 No ROA Nonecovered by 41.78.20.0/22 672 100% 67
169.239.36.0/24 No ROA Nonecovered by 169.239.36.0/22 672 100% 67
169.239.37.0/24 No ROA Nonecovered by 169.239.36.0/22 672 100% 67
41.78.20.0/22 No ROA Other IRR onlyRIPE-NONAUTH 673 100% 67
102.217.70.0/24 No ROA RIR databaseAFRINIC 673 100% 67
169.239.38.0/24 No ROA RIR databaseAFRINIC 673 100% 67
169.239.39.0/24 No ROA RIR databaseAFRINIC 673 100% 67
102.217.68.0/24 No ROA RIR databaseAFRINIC 671 100% 67
102.217.69.0/24 No ROA RIR databaseAFRINIC 671 100% 67
102.217.71.0/24 No ROA RIR databaseAFRINIC 671 100% 67
82.41.142.0/24 Valid RIR databaseRADB, RIPE 670 100% 67
146.103.32.0/24 Valid RIR databaseRADB, RIPE 670 100% 67

AS-SET

AS37191 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 22 are in fix.csv.

  • ROA: none13
  • Route object: none6
  • Route object: RIR1
  • Route object: not announced2
ChangePrefix or setDetailFull-table peers
ROA: none41.78.20.0/24No ROA covers it. Add a ROA for AS37191, maxLength 24.673 of 673
Route object: none41.78.20.0/24No route object for it. A route object for 41.78.20.0/22 with origin AS37191 covers it (filters allowing more-specifics accept it). Add a route object with origin AS37191 in the RIR database for the space.673 of 673
ROA: none41.78.21.0/24No ROA covers it. Add a ROA for AS37191, maxLength 24.673 of 673
Route object: none41.78.21.0/24No route object for it. A route object for 41.78.20.0/22 with origin AS37191 covers it (filters allowing more-specifics accept it). Add a route object with origin AS37191 in the RIR database for the space.673 of 673
ROA: none41.78.22.0/24No ROA covers it. Add a ROA for AS37191, maxLength 24.673 of 673
Route object: none41.78.22.0/24No route object for it. A route object for 41.78.20.0/22 with origin AS37191 covers it (filters allowing more-specifics accept it). Add a route object with origin AS37191 in the RIR database for the space.673 of 673
ROA: none41.78.23.0/24No ROA covers it. Add a ROA for AS37191, maxLength 24.672 of 673
Route object: none41.78.23.0/24No route object for it. A route object for 41.78.20.0/22 with origin AS37191 covers it (filters allowing more-specifics accept it). Add a route object with origin AS37191 in the RIR database for the space.672 of 673
ROA: none169.239.36.0/24No ROA covers it. Add a ROA for AS37191, maxLength 24.672 of 673
Route object: none169.239.36.0/24No route object for it. A route object for 169.239.36.0/22 with origin AS37191 covers it (filters allowing more-specifics accept it). Add a route object with origin AS37191 in the RIR database for the space.672 of 673
ROA: none169.239.37.0/24No ROA covers it. Add a ROA for AS37191, maxLength 24.672 of 673
Route object: none169.239.37.0/24No route object for it. A route object for 169.239.36.0/22 with origin AS37191 covers it (filters allowing more-specifics accept it). Add a route object with origin AS37191 in the RIR database for the space.672 of 673
ROA: none41.78.20.0/22No ROA covers it. Add a ROA for AS37191, maxLength 22.673 of 673
Route object: RIR41.78.20.0/22Route object only in RIPE-NONAUTH. Add it in the RIR database for the space.673 of 673
ROA: none102.217.70.0/24No ROA covers it. Add a ROA for AS37191, maxLength 24.673 of 673
ROA: none169.239.38.0/24No ROA covers it. Add a ROA for AS37191, maxLength 24.673 of 673
ROA: none169.239.39.0/24No ROA covers it. Add a ROA for AS37191, maxLength 24.673 of 673
ROA: none102.217.68.0/24No ROA covers it. Add a ROA for AS37191, maxLength 24.671 of 673
ROA: none102.217.69.0/24No ROA covers it. Add a ROA for AS37191, maxLength 24.671 of 673
ROA: none102.217.71.0/24No ROA covers it. Add a ROA for AS37191, maxLength 24.671 of 673

Route objects not announced

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

102.217.68.0/22AFRINICNo ROA
169.239.36.0/22AFRINICNo 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.