Network · data from 2026-11-12
AS59708 Rayanhamafza-AS Rayan Hamafza Company Public Joint Stock
Registry name: Rayanhamafza-AS Rayan Hamafza Company Public Joint Stock, IR · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS59708, 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.
| 80.253.157.0/24 | Valid | Other IRR onlyRADB | 672 100% |
| 185.4.104.0/22 | Valid | RIR databaseRADB, RIPE | 672 100% |
| 185.4.104.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 185.4.105.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 185.4.106.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 185.4.107.0/24 | Valid | RIR databaseRIPE | 671 100% |
AS-SET
AS59708 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 2 are in fix.csv.
- Route object: RIR1
- Route object: not announced1
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: RIR | 80.253.157.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS59708 whose prefix no peer sees AS59708 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 185.4.104.0/23 | 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.