Network · data from 2026-11-12
AS60627 RA-AS Rayankadeh Apadana Company Ltd
Registry name: RA-AS Rayankadeh Apadana Company Ltd, IR · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS60627, 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.
| 193.228.136.0/24 | No ROA | RIR databaseRIPE | 670 100% |
| 185.83.89.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 185.113.56.0/22 | Valid | RIR databaseRIPE | 671 100% |
| 185.124.112.0/22 | Valid | RIR databaseRIPE | 671 100% |
| 185.140.56.0/22 | Valid | RIR databaseRIPE | 671 100% |
| 185.143.204.0/22 | Valid | RIR databaseRIPE | 671 100% |
| 185.145.8.0/22 | Valid | RIR databaseRIPE | 671 100% |
AS-SET
AS60627 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 10 are in fix.csv.
- ROA: none1
- Route object: not announced9
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 193.228.136.0/24 | No ROA covers it. Add a ROA for AS60627, maxLength 24. |
Route objects not announced
Route objects with origin AS60627 whose prefix no peer sees AS60627 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 185.113.56.0/24 | RIPE | Invalid: maxLength |
| 185.113.57.0/24 | RIPE | Invalid: maxLength |
| 185.113.58.0/24 | RIPE | Invalid: maxLength |
| 185.113.59.0/24 | RIPE | Invalid: maxLength |
| 185.124.112.0/23 | RIPE | Invalid: maxLength |
| 185.124.114.0/23 | RIPE | Invalid: maxLength |
| 185.124.114.0/24 | RIPE | Invalid: maxLength |
| 185.124.115.0/24 | RIPE | Invalid: maxLength |
| 2a0e:ea00::/29 | 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.