Network · data from 2026-11-12
AS208797 MASHREQBANK-AS MASHREQBANK PJSC
Registry name: MASHREQBANK-AS MASHREQBANK PJSC, AE · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS208797, 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.
| 213.42.10.0/23 | Invalid: origin | Other origin only | 2 0%low visibility |
| 213.42.10.0/24 | Invalid: origin | None | 2 0%low visibility |
| 213.42.11.0/24 | Invalid: origin | None | 2 0%low visibility |
| 94.201.28.0/24 | Invalid: origin | None | 1 0%low visibility |
| 195.244.14.0/24 | Valid | RIR databaseRADB, RIPE | 673 100% |
| 195.244.18.0/24 | Valid | RIR databaseRADB, RIPE | 673 100% |
| 195.244.19.0/24 | Valid | RIR databaseRADB, RIPE | 673 100% |
| 195.244.14.0/23 | Valid | RIR databaseRADB, RIPE | 672 100% |
| 195.244.15.0/24 | Valid | RIR databaseRADB, RIPE | 672 100% |
| 195.244.18.0/23 | Valid | RIR databaseRADB, RIPE | 672 100% |
AS-SET
AS208797 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 17 are in fix.csv.
- ROA: origin4
- Route object: none4
- Route object: not announced9
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: origin | 213.42.10.0/23 | ROAs covering it name AS5384, not AS208797. If AS208797 should announce it, add a ROA for AS208797. |
| Route object: none | 213.42.10.0/23 | Route objects for it name AS5384. Add a route object with origin AS208797 in the RIR database for the space. |
| ROA: origin | 213.42.10.0/24 | ROAs covering it name AS5384, not AS208797. If AS208797 should announce it, add a ROA for AS208797. |
| Route object: none | 213.42.10.0/24 | No route object for it. Add a route object with origin AS208797 in the RIR database for the space. |
| ROA: origin | 213.42.11.0/24 | ROAs covering it name AS5384, not AS208797. If AS208797 should announce it, add a ROA for AS208797. |
| Route object: none | 213.42.11.0/24 | No route object for it. Add a route object with origin AS208797 in the RIR database for the space. |
| ROA: origin | 94.201.28.0/24 | ROAs covering it name AS15802, not AS208797. If AS208797 should announce it, add a ROA for AS208797. |
| Route object: none | 94.201.28.0/24 | No route object for it. Add a route object with origin AS208797 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS208797 whose prefix no peer sees AS208797 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 2a04:e0c0::/29 | RIPE | Valid |
| 2a04:e0c0::/32 | RIPE | Valid |
| 2a04:e0c1::/32 | RIPE | Valid |
| 2a04:e0c2::/32 | RIPE | Valid |
| 2a04:e0c3::/32 | RIPE | Valid |
| 2a04:e0c4::/32 | RIPE | Valid |
| 2a04:e0c5::/32 | RIPE | Valid |
| 2a04:e0c6::/32 | RIPE | Valid |
| 2a04:e0c7::/32 | 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.