bgpreport

Network · data from 2026-11-12

AS29690 ATHEER AI Jeraisy Electronic Services Company Ltd.

Registry name: ATHEER AI Jeraisy Electronic Services Company Ltd., SA · not in PeeringDB

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

Announced routes

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

83.101.128.0/24 Valid Nonecovered by 83.101.128.0/19 673 100% 67
83.101.129.0/24 Valid Nonecovered by 83.101.128.0/19 673 100% 67
83.101.138.0/24 Valid Nonecovered by 83.101.128.0/19 673 100% 67
83.101.139.0/24 Valid Nonecovered by 83.101.128.0/19 673 100% 67
83.101.141.0/24 Valid Nonecovered by 83.101.128.0/19 673 100% 67
83.101.143.0/24 Valid Nonecovered by 83.101.128.0/19 673 100% 67
83.101.150.0/24 Valid Nonecovered by 83.101.128.0/19 673 100% 67
83.101.151.0/24 Valid Nonecovered by 83.101.128.0/19 673 100% 67
83.101.154.0/24 Valid Nonecovered by 83.101.128.0/19 673 100% 67
83.101.155.0/24 Valid Nonecovered by 83.101.128.0/19 673 100% 67
83.101.156.0/24 Valid Nonecovered by 83.101.128.0/19 673 100% 67
212.70.32.0/24 Valid Nonecovered by 212.70.32.0/19 673 100% 66
212.70.34.0/24 Valid Nonecovered by 212.70.32.0/19 673 100% 66
212.70.36.0/24 Valid Nonecovered by 212.70.32.0/19 673 100% 66
212.70.38.0/24 Valid Nonecovered by 212.70.32.0/19 673 100% 66
212.70.47.0/24 Valid Nonecovered by 212.70.32.0/19 673 100% 67
212.70.48.0/24 Valid Nonecovered by 212.70.32.0/19 673 100% 67
212.70.49.0/24 Valid Nonecovered by 212.70.32.0/19 673 100% 67
212.70.50.0/24 Valid Nonecovered by 212.70.32.0/19 673 100% 66
212.70.51.0/24 Valid Nonecovered by 212.70.32.0/19 673 100% 66
212.70.53.0/24 Valid Nonecovered by 212.70.32.0/19 673 100% 66
212.70.54.0/24 Valid Nonecovered by 212.70.32.0/19 673 100% 66
83.101.128.0/19 Valid RIR databaseRADB, RIPE 673 100% 66
83.101.137.0/24 Valid RIR databaseRIPE 673 100% 67
83.101.140.0/24 Valid RIR databaseRIPE 673 100% 67
83.101.149.0/24 Valid RIR databaseRIPE 673 100% 67
212.70.32.0/19 Valid RIR databaseRADB, RIPE 673 100% 66
212.70.40.0/24 Valid RIR databaseRIPE 673 100% 66
212.70.52.0/24 Valid RIR databaseRIPE 673 100% 66

AS-SET

AS29690 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 35 are in fix.csv.

  • Route object: none22
  • Route object: not announced13
ChangePrefix or setDetailFull-table peers
Route object: none83.101.128.0/24No route object for it. A route object for 83.101.128.0/19 with origin AS29690 covers it (filters allowing more-specifics accept it). Add a route object with origin AS29690 in the RIR database for the space.673 of 673
Route object: none83.101.129.0/24No route object for it. A route object for 83.101.128.0/19 with origin AS29690 covers it (filters allowing more-specifics accept it). Add a route object with origin AS29690 in the RIR database for the space.673 of 673
Route object: none83.101.138.0/24No route object for it. A route object for 83.101.128.0/19 with origin AS29690 covers it (filters allowing more-specifics accept it). Add a route object with origin AS29690 in the RIR database for the space.673 of 673
Route object: none83.101.139.0/24No route object for it. A route object for 83.101.128.0/19 with origin AS29690 covers it (filters allowing more-specifics accept it). Add a route object with origin AS29690 in the RIR database for the space.673 of 673
Route object: none83.101.141.0/24No route object for it. A route object for 83.101.128.0/19 with origin AS29690 covers it (filters allowing more-specifics accept it). Add a route object with origin AS29690 in the RIR database for the space.673 of 673
Route object: none83.101.143.0/24No route object for it. A route object for 83.101.128.0/19 with origin AS29690 covers it (filters allowing more-specifics accept it). Add a route object with origin AS29690 in the RIR database for the space.673 of 673
Route object: none83.101.150.0/24No route object for it. A route object for 83.101.128.0/19 with origin AS29690 covers it (filters allowing more-specifics accept it). Add a route object with origin AS29690 in the RIR database for the space.673 of 673
Route object: none83.101.151.0/24No route object for it. A route object for 83.101.128.0/19 with origin AS29690 covers it (filters allowing more-specifics accept it). Add a route object with origin AS29690 in the RIR database for the space.673 of 673
Route object: none83.101.154.0/24No route object for it. A route object for 83.101.128.0/19 with origin AS29690 covers it (filters allowing more-specifics accept it). Add a route object with origin AS29690 in the RIR database for the space.673 of 673
Route object: none83.101.155.0/24No route object for it. A route object for 83.101.128.0/19 with origin AS29690 covers it (filters allowing more-specifics accept it). Add a route object with origin AS29690 in the RIR database for the space.673 of 673
Route object: none83.101.156.0/24No route object for it. A route object for 83.101.128.0/19 with origin AS29690 covers it (filters allowing more-specifics accept it). Add a route object with origin AS29690 in the RIR database for the space.673 of 673
Route object: none212.70.32.0/24No route object for it. A route object for 212.70.32.0/19 with origin AS29690 covers it (filters allowing more-specifics accept it). Add a route object with origin AS29690 in the RIR database for the space.673 of 673
Route object: none212.70.34.0/24No route object for it. A route object for 212.70.32.0/19 with origin AS29690 covers it (filters allowing more-specifics accept it). Add a route object with origin AS29690 in the RIR database for the space.673 of 673
Route object: none212.70.36.0/24No route object for it. A route object for 212.70.32.0/19 with origin AS29690 covers it (filters allowing more-specifics accept it). Add a route object with origin AS29690 in the RIR database for the space.673 of 673
Route object: none212.70.38.0/24No route object for it. A route object for 212.70.32.0/19 with origin AS29690 covers it (filters allowing more-specifics accept it). Add a route object with origin AS29690 in the RIR database for the space.673 of 673
Route object: none212.70.47.0/24No route object for it. A route object for 212.70.32.0/19 with origin AS29690 covers it (filters allowing more-specifics accept it). Add a route object with origin AS29690 in the RIR database for the space.673 of 673
Route object: none212.70.48.0/24No route object for it. A route object for 212.70.32.0/19 with origin AS29690 covers it (filters allowing more-specifics accept it). Add a route object with origin AS29690 in the RIR database for the space.673 of 673
Route object: none212.70.49.0/24No route object for it. A route object for 212.70.32.0/19 with origin AS29690 covers it (filters allowing more-specifics accept it). Add a route object with origin AS29690 in the RIR database for the space.673 of 673
Route object: none212.70.50.0/24No route object for it. A route object for 212.70.32.0/19 with origin AS29690 covers it (filters allowing more-specifics accept it). Add a route object with origin AS29690 in the RIR database for the space.673 of 673
Route object: none212.70.51.0/24No route object for it. A route object for 212.70.32.0/19 with origin AS29690 covers it (filters allowing more-specifics accept it). Add a route object with origin AS29690 in the RIR database for the space.673 of 673
Route object: none212.70.53.0/24No route object for it. A route object for 212.70.32.0/19 with origin AS29690 covers it (filters allowing more-specifics accept it). Add a route object with origin AS29690 in the RIR database for the space.673 of 673
Route object: none212.70.54.0/24No route object for it. A route object for 212.70.32.0/19 with origin AS29690 covers it (filters allowing more-specifics accept it). Add a route object with origin AS29690 in the RIR database for the space.673 of 673

Route objects not announced

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

83.101.130.0/24RIPEInvalid: maxLength
83.101.131.0/24RIPEInvalid: maxLength
83.101.132.0/24RIPEInvalid: maxLength
83.101.134.0/24RIPEInvalid: maxLength
83.101.135.0/24RIPEInvalid: maxLength
83.101.136.0/24RIPEInvalid: maxLength
91.229.220.0/24RIPEInvalid: origin
193.105.119.0/24RIPEInvalid: origin
194.36.164.0/24RIPEInvalid: origin
212.70.35.0/24RIPEInvalid: maxLength
212.70.44.0/24RIPEInvalid: maxLength
212.70.45.0/24RIPEValid
2a00:1ef8::/32RIPENo 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.