Network · data from 2026-11-12
AS56503 BADR-AS PJSC "Badr Rayan Jonoob"
Registry name: BADR-AS PJSC "Badr Rayan Jonoob", IR · not in PeeringDB
44IPv4 routes
100.0% RPKI valid · 56.8% with a route object
0IPv6 routes
0RPKI invalid
0 origin · 0 maxLength
0No ROA
19 with no route object for this origin
0Low visibility
seen by under 10% of full-table peers
7Route objects not announced
registered with origin AS56503, seen from no peer
Announced routes
Every prefix a peer of the route collectors sees with origin AS56503, 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.
| 185.26.232.0/23 | Valid | Nonecovered by 185.26.232.0/22 | 671 100% |
| 185.26.234.0/23 | Valid | Nonecovered by 185.26.232.0/22 | 671 100% |
| 91.106.80.0/24 | Valid | Nonecovered by 91.106.80.0/20 | 670 100% |
| 91.106.81.0/24 | Valid | Nonecovered by 91.106.80.0/20 | 670 100% |
| 91.106.82.0/24 | Valid | Nonecovered by 91.106.80.0/20 | 670 100% |
| 91.106.83.0/24 | Valid | Nonecovered by 91.106.80.0/20 | 670 100% |
| 91.106.84.0/24 | Valid | Nonecovered by 91.106.80.0/20 | 670 100% |
| 91.106.85.0/24 | Valid | Nonecovered by 91.106.80.0/20 | 670 100% |
| 91.106.86.0/24 | Valid | Nonecovered by 91.106.80.0/20 | 670 100% |
| 91.106.87.0/24 | Valid | Nonecovered by 91.106.80.0/20 | 670 100% |
| 91.106.88.0/24 | Valid | Nonecovered by 91.106.80.0/20 | 670 100% |
| 91.106.89.0/24 | Valid | Nonecovered by 91.106.80.0/20 | 670 100% |
| 91.106.90.0/24 | Valid | Nonecovered by 91.106.80.0/20 | 670 100% |
| 91.106.91.0/24 | Valid | Nonecovered by 91.106.80.0/20 | 670 100% |
| 91.106.92.0/24 | Valid | Nonecovered by 91.106.80.0/20 | 670 100% |
| 91.106.93.0/24 | Valid | Nonecovered by 91.106.80.0/20 | 670 100% |
| 91.106.94.0/24 | Valid | Nonecovered by 91.106.80.0/20 | 670 100% |
| 91.106.95.0/24 | Valid | Nonecovered by 91.106.80.0/20 | 670 100% |
| 185.104.232.0/22 | Valid | None | 641 95% |
| 91.106.67.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 185.103.248.0/22 | Valid | RIR databaseRIPE | 671 100% |
| 185.104.240.0/22 | Valid | RIR databaseRIPE | 671 100% |
| 185.106.144.0/22 | Valid | RIR databaseRIPE | 671 100% |
| 185.107.28.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 185.107.29.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 185.107.30.0/23 | Valid | RIR databaseRIPE | 671 100% |
| 185.108.164.0/22 | Valid | RIR databaseRIPE | 671 100% |
| 91.106.64.0/24 | Valid | RIR databaseRIPE | 670 100% |
| 91.106.65.0/24 | Valid | RIR databaseRIPE | 670 100% |
| 91.106.66.0/24 | Valid | RIR databaseRIPE | 670 100% |
| 91.106.68.0/24 | Valid | RIR databaseRIPE | 670 100% |
| 91.106.69.0/24 | Valid | RIR databaseRIPE | 670 100% |
| 91.106.70.0/24 | Valid | RIR databaseRIPE | 670 100% |
| 91.106.71.0/24 | Valid | RIR databaseRIPE | 670 100% |
| 91.106.72.0/24 | Valid | RIR databaseRIPE | 670 100% |
| 91.106.73.0/24 | Valid | RIR databaseRIPE | 670 100% |
| 91.106.74.0/24 | Valid | RIR databaseRIPE | 670 100% |
| 91.106.75.0/24 | Valid | RIR databaseRIPE | 670 100% |
| 91.106.76.0/24 | Valid | RIR databaseRIPE | 670 100% |
| 91.106.77.0/24 | Valid | RIR databaseRIPE | 670 100% |
| 91.106.78.0/24 | Valid | RIR databaseRIPE | 670 100% |
| 91.106.79.0/24 | Valid | RIR databaseRIPE | 670 100% |
| 185.103.244.0/22 | Valid | RIR databaseRIPE | 670 100% |
| 185.106.136.0/22 | Valid | RIR databaseRIPE | 670 100% |
AS-SET
AS56503 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.
- Route object: none19
- Route object: not announced7
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: none | 185.26.232.0/23 | No route object for it. A route object for 185.26.232.0/22 with origin AS56503 covers it (filters allowing more-specifics accept it). Add a route object with origin AS56503 in the RIR database for the space. |
| Route object: none | 185.26.234.0/23 | No route object for it. A route object for 185.26.232.0/22 with origin AS56503 covers it (filters allowing more-specifics accept it). Add a route object with origin AS56503 in the RIR database for the space. |
| Route object: none | 91.106.80.0/24 | No route object for it. A route object for 91.106.80.0/20 with origin AS56503 covers it (filters allowing more-specifics accept it). Add a route object with origin AS56503 in the RIR database for the space. |
| Route object: none | 91.106.81.0/24 | No route object for it. A route object for 91.106.80.0/20 with origin AS56503 covers it (filters allowing more-specifics accept it). Add a route object with origin AS56503 in the RIR database for the space. |
| Route object: none | 91.106.82.0/24 | No route object for it. A route object for 91.106.80.0/20 with origin AS56503 covers it (filters allowing more-specifics accept it). Add a route object with origin AS56503 in the RIR database for the space. |
| Route object: none | 91.106.83.0/24 | No route object for it. A route object for 91.106.80.0/20 with origin AS56503 covers it (filters allowing more-specifics accept it). Add a route object with origin AS56503 in the RIR database for the space. |
| Route object: none | 91.106.84.0/24 | No route object for it. A route object for 91.106.80.0/20 with origin AS56503 covers it (filters allowing more-specifics accept it). Add a route object with origin AS56503 in the RIR database for the space. |
| Route object: none | 91.106.85.0/24 | No route object for it. A route object for 91.106.80.0/20 with origin AS56503 covers it (filters allowing more-specifics accept it). Add a route object with origin AS56503 in the RIR database for the space. |
| Route object: none | 91.106.86.0/24 | No route object for it. A route object for 91.106.80.0/20 with origin AS56503 covers it (filters allowing more-specifics accept it). Add a route object with origin AS56503 in the RIR database for the space. |
| Route object: none | 91.106.87.0/24 | No route object for it. A route object for 91.106.80.0/20 with origin AS56503 covers it (filters allowing more-specifics accept it). Add a route object with origin AS56503 in the RIR database for the space. |
| Route object: none | 91.106.88.0/24 | No route object for it. A route object for 91.106.80.0/20 with origin AS56503 covers it (filters allowing more-specifics accept it). Add a route object with origin AS56503 in the RIR database for the space. |
| Route object: none | 91.106.89.0/24 | No route object for it. A route object for 91.106.80.0/20 with origin AS56503 covers it (filters allowing more-specifics accept it). Add a route object with origin AS56503 in the RIR database for the space. |
| Route object: none | 91.106.90.0/24 | No route object for it. A route object for 91.106.80.0/20 with origin AS56503 covers it (filters allowing more-specifics accept it). Add a route object with origin AS56503 in the RIR database for the space. |
| Route object: none | 91.106.91.0/24 | No route object for it. A route object for 91.106.80.0/20 with origin AS56503 covers it (filters allowing more-specifics accept it). Add a route object with origin AS56503 in the RIR database for the space. |
| Route object: none | 91.106.92.0/24 | No route object for it. A route object for 91.106.80.0/20 with origin AS56503 covers it (filters allowing more-specifics accept it). Add a route object with origin AS56503 in the RIR database for the space. |
| Route object: none | 91.106.93.0/24 | No route object for it. A route object for 91.106.80.0/20 with origin AS56503 covers it (filters allowing more-specifics accept it). Add a route object with origin AS56503 in the RIR database for the space. |
| Route object: none | 91.106.94.0/24 | No route object for it. A route object for 91.106.80.0/20 with origin AS56503 covers it (filters allowing more-specifics accept it). Add a route object with origin AS56503 in the RIR database for the space. |
| Route object: none | 91.106.95.0/24 | No route object for it. A route object for 91.106.80.0/20 with origin AS56503 covers it (filters allowing more-specifics accept it). Add a route object with origin AS56503 in the RIR database for the space. |
| Route object: none | 185.104.232.0/22 | No route object for it. Add a route object with origin AS56503 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS56503 whose prefix no peer sees AS56503 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 91.106.80.0/20 | RIPE | No ROA |
| 185.26.232.0/22 | RIPE | No ROA |
| 185.104.232.0/24 | RIPE | Invalid: maxLength |
| 185.104.233.0/24 | RIPE | Invalid: maxLength |
| 185.104.234.0/24 | RIPE | Invalid: maxLength |
| 185.104.235.0/24 | RIPE | Invalid: maxLength |
| 2a04:1380::/29 | RIPE | Valid |
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.