Network · data from 2026-11-12
AS28938 MEDUNET-AS Sultan Bin Abdulaziz Foundation
Registry name: MEDUNET-AS Sultan Bin Abdulaziz Foundation, SA · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS28938, 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.
| 89.189.224.0/20 | No ROA | Nonecovered by 89.189.224.0/19 | 672 100% |
| 89.189.240.0/20 | No ROA | Nonecovered by 89.189.224.0/19 | 672 100% |
| 213.230.0.0/24 | No ROA | RIR databaseRADB, RIPE | 672 100% |
AS-SET
AS28938 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 44 are in fix.csv.
- ROA: none3
- Route object: none2
- Route object: not announced39
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 89.189.224.0/20 | No ROA covers it. Add a ROA for AS28938, maxLength 20. |
| Route object: none | 89.189.224.0/20 | No route object for it. A route object for 89.189.224.0/19 with origin AS28938 covers it (filters allowing more-specifics accept it). Add a route object with origin AS28938 in the RIR database for the space. |
| ROA: none | 89.189.240.0/20 | No ROA covers it. Add a ROA for AS28938, maxLength 20. |
| Route object: none | 89.189.240.0/20 | No route object for it. A route object for 89.189.224.0/19 with origin AS28938 covers it (filters allowing more-specifics accept it). Add a route object with origin AS28938 in the RIR database for the space. |
| ROA: none | 213.230.0.0/24 | No ROA covers it. Add a ROA for AS28938, maxLength 24. |
Route objects not announced
Route objects with origin AS28938 whose prefix no peer sees AS28938 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 89.189.224.0/19 | RADB, RIPE | No ROA |
| 89.189.224.0/24 | RADB, RIPE | No ROA |
| 89.189.225.0/24 | RADB, RIPE | No ROA |
| 89.189.226.0/24 | RADB, RIPE | No ROA |
| 89.189.227.0/24 | RADB, RIPE | No ROA |
| 89.189.229.0/24 | RIPE | No ROA |
| 89.189.232.0/24 | RADB, RIPE | No ROA |
| 213.230.0.0/19 | RADB, RIPE | No ROA |
| 213.230.1.0/24 | RADB, RIPE | No ROA |
| 213.230.2.0/24 | RADB, RIPE | No ROA |
| 213.230.3.0/24 | RADB, RIPE | No ROA |
| 213.230.4.0/24 | RADB, RIPE | No ROA |
| 213.230.5.0/24 | RADB, RIPE | No ROA |
| 213.230.6.0/24 | RADB, RIPE | No ROA |
| 213.230.7.0/24 | RADB, RIPE | No ROA |
| 213.230.8.0/24 | RADB, RIPE | No ROA |
| 213.230.9.0/24 | RADB, RIPE | No ROA |
| 213.230.10.0/24 | RADB, RIPE | No ROA |
| 213.230.11.0/24 | RADB, RIPE | No ROA |
| 213.230.12.0/24 | RADB, RIPE | No ROA |
| 213.230.13.0/24 | RADB, RIPE | No ROA |
| 213.230.14.0/24 | RADB, RIPE | No ROA |
| 213.230.15.0/24 | RADB, RIPE | No ROA |
| 213.230.16.0/24 | RADB, RIPE | No ROA |
| 213.230.17.0/24 | RADB, RIPE | No ROA |
| 213.230.18.0/24 | RADB, RIPE | No ROA |
| 213.230.19.0/24 | RADB, RIPE | No ROA |
| 213.230.20.0/24 | RADB | No ROA |
| 213.230.21.0/24 | RADB, RIPE | No ROA |
| 213.230.22.0/24 | RADB, RIPE | No ROA |
| 213.230.23.0/24 | RADB, RIPE | No ROA |
| 213.230.24.0/24 | RADB, RIPE | No ROA |
| 213.230.25.0/24 | RADB, RIPE | No ROA |
| 213.230.26.0/24 | RADB, RIPE | No ROA |
| 213.230.27.0/24 | RADB, RIPE | No ROA |
| 213.230.28.0/24 | RADB, RIPE | No ROA |
| 213.230.29.0/24 | RADB, RIPE | No ROA |
| 213.230.30.0/24 | RADB, RIPE | No ROA |
| 213.230.31.0/24 | 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.