Network · data from 2026-11-12
AS201340 ENBD EMIRATES NBD (P.J.S.C).
Registry name: ENBD EMIRATES NBD (P.J.S.C)., AE · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS201340, 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.76.206.0/23 | No ROA | Other origin onlycovered by 185.76.204.0/22 | 671 100% |
| 185.76.204.0/23 | No ROA | Nonecovered by 185.76.204.0/22 | 45 7%low visibility |
| 185.76.204.0/22 | No ROA | Other IRR onlyNTTCOM | 673 100% |
| 185.76.204.0/24 | No ROA | Other IRR onlyRADB | 673 100% |
| 185.76.205.0/24 | No ROA | Other IRR onlyRADB | 673 100% |
| 185.76.206.0/24 | No ROA | Other IRR onlyRADB | 673 100% |
| 185.76.207.0/24 | No ROA | Other IRR onlyRADB | 673 100% |
| 109.175.206.0/24 | No ROA | RIR databaseRIPE | 673 100% |
| 194.164.220.0/24 | No ROA | RIR databaseRIPE | 673 100% |
| 194.164.221.0/24 | No ROA | RIR databaseRIPE | 673 100% |
| 194.164.225.0/24 | No ROA | RIR databaseRADB, RIPE | 673 100% |
| 194.170.8.0/24 | Valid | Other IRR onlyRADB | 45 7%low visibility |
| 194.170.245.0/24 | Valid | Other IRR onlyRADB | 45 7%low visibility |
AS-SET
AS201340 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: none11
- Route object: none2
- Route object: RIR7
- Route object: not announced1
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 185.76.206.0/23 | No ROA covers it. Add a ROA for AS201340, maxLength 23. |
| Route object: none | 185.76.206.0/23 | Route objects for it name AS15802. A route object for 185.76.204.0/22 with origin AS201340 covers it (filters allowing more-specifics accept it). Add a route object with origin AS201340 in the RIR database for the space. |
| ROA: none | 185.76.204.0/23 | No ROA covers it. Add a ROA for AS201340, maxLength 23. |
| Route object: none | 185.76.204.0/23 | No route object for it. A route object for 185.76.204.0/22 with origin AS201340 covers it (filters allowing more-specifics accept it). Add a route object with origin AS201340 in the RIR database for the space. |
| ROA: none | 185.76.204.0/22 | No ROA covers it. Add a ROA for AS201340, maxLength 22. |
| Route object: RIR | 185.76.204.0/22 | Route object only in NTTCOM. Add it in the RIR database for the space. |
| ROA: none | 185.76.204.0/24 | No ROA covers it. Add a ROA for AS201340, maxLength 24. |
| Route object: RIR | 185.76.204.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 185.76.205.0/24 | No ROA covers it. Add a ROA for AS201340, maxLength 24. |
| Route object: RIR | 185.76.205.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 185.76.206.0/24 | No ROA covers it. Add a ROA for AS201340, maxLength 24. |
| Route object: RIR | 185.76.206.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 185.76.207.0/24 | No ROA covers it. Add a ROA for AS201340, maxLength 24. |
| Route object: RIR | 185.76.207.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 109.175.206.0/24 | No ROA covers it. Add a ROA for AS201340, maxLength 24. |
| ROA: none | 194.164.220.0/24 | No ROA covers it. Add a ROA for AS201340, maxLength 24. |
| ROA: none | 194.164.221.0/24 | No ROA covers it. Add a ROA for AS201340, maxLength 24. |
| ROA: none | 194.164.225.0/24 | No ROA covers it. Add a ROA for AS201340, maxLength 24. |
| Route object: RIR | 194.170.8.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 194.170.245.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS201340 whose prefix no peer sees AS201340 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 194.164.220.0/23 | 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.