Network · data from 2026-11-12
AS31699 bank-al-jazira-as BANK AL JAZIRA
Registry name: bank-al-jazira-as BANK AL JAZIRA, SA · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS31699, 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.
| 217.173.90.0/29 | Invalid: maxLength | Nonecovered by 217.173.90.0/23 | 1 0%low visibility |
| 217.173.94.0/29 | Invalid: maxLength | Nonecovered by 217.173.94.0/24 | 1 0%low visibility |
| 217.173.90.0/24 | Valid | Nonecovered by 217.173.90.0/23 | 673 100% |
| 217.173.91.0/24 | Valid | Nonecovered by 217.173.90.0/23 | 673 100% |
| 217.173.95.0/24 | Valid | Nonecovered by 217.173.94.0/23 | 672 100% |
| 217.173.82.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 217.173.84.0/23 | Valid | RIR databaseRADB, RIPE | 672 100% |
| 217.173.84.0/24 | Valid | RIR databaseRADB, RIPE | 672 100% |
| 217.173.85.0/24 | Valid | RIR databaseRADB, RIPE | 672 100% |
| 217.173.82.0/23 | Valid | RIR databaseRIPE | 671 100% |
| 217.173.83.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 217.173.86.0/23 | Valid | RIR databaseRIPE | 671 100% |
| 217.173.94.0/24 | Valid | RIR databaseRIPE | 671 100% |
AS-SET
AS31699 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 21 are in fix.csv.
- ROA: maxLength2
- Route object: none5
- Route object: not announced14
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: maxLength | 217.173.90.0/29 | ROA 217.173.90.0/24 AS31699 has maxLength 24; the route is a /29. Raise the maxLength, or add a ROA for 217.173.90.0/29. |
| Route object: none | 217.173.90.0/29 | No route object for it. A route object for 217.173.90.0/23 with origin AS31699 covers it (too long for filters allowing more-specifics up to /24). Add a route object with origin AS31699 in the RIR database for the space. |
| ROA: maxLength | 217.173.94.0/29 | ROA 217.173.94.0/24 AS31699 has maxLength 24; the route is a /29. Raise the maxLength, or add a ROA for 217.173.94.0/29. |
| Route object: none | 217.173.94.0/29 | No route object for it. A route object for 217.173.94.0/24 with origin AS31699 covers it (too long for filters allowing more-specifics up to /24). Add a route object with origin AS31699 in the RIR database for the space. |
| Route object: none | 217.173.90.0/24 | No route object for it. A route object for 217.173.90.0/23 with origin AS31699 covers it (filters allowing more-specifics accept it). Add a route object with origin AS31699 in the RIR database for the space. |
| Route object: none | 217.173.91.0/24 | No route object for it. A route object for 217.173.90.0/23 with origin AS31699 covers it (filters allowing more-specifics accept it). Add a route object with origin AS31699 in the RIR database for the space. |
| Route object: none | 217.173.95.0/24 | No route object for it. A route object for 217.173.94.0/23 with origin AS31699 covers it (filters allowing more-specifics accept it). Add a route object with origin AS31699 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS31699 whose prefix no peer sees AS31699 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 217.173.80.0/20 | RADB, RIPE | No ROA |
| 217.173.80.0/23 | RIPE | No ROA |
| 217.173.80.0/24 | RIPE | No ROA |
| 217.173.81.0/24 | RIPE | No ROA |
| 217.173.88.0/21 | RIPE | No ROA |
| 217.173.88.0/23 | RIPE | Invalid: origin |
| 217.173.88.0/24 | RIPE | Invalid: origin |
| 217.173.89.0/24 | RIPE | Invalid: origin |
| 217.173.90.0/23 | RIPE | No ROA |
| 217.173.92.0/23 | RIPE | Invalid: origin |
| 217.173.92.0/24 | RIPE | Invalid: origin |
| 217.173.93.0/24 | RIPE | Invalid: origin |
| 217.173.94.0/23 | RIPE | No ROA |
| 2a00:d7c0::/32 | RADB, RIPE | No 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.