Network · data from 2026-11-12
AS57457 asan-as Asan Pardakht Persian Co. LTD
Registry name: asan-as Asan Pardakht Persian Co. LTD, IR · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS57457, 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.
| 91.232.64.0/24 | Valid | Nonecovered by 91.232.64.0/23 | 671 100% |
| 91.232.65.0/24 | Valid | Nonecovered by 91.232.64.0/23 | 671 100% |
| 91.232.66.0/24 | Valid | Nonecovered by 91.232.66.0/23 | 671 100% |
| 91.232.67.0/24 | Valid | Nonecovered by 91.232.66.0/23 | 671 100% |
| 91.232.68.0/24 | Valid | Nonecovered by 91.232.68.0/23 | 671 100% |
| 91.232.69.0/24 | Valid | Nonecovered by 91.232.68.0/23 | 671 100% |
| 185.210.200.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 185.210.201.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 185.210.203.0/24 | Valid | RIR databaseRIPE | 671 100% |
AS-SET
AS57457 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 12 are in fix.csv.
- Route object: none6
- Route object: not announced6
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: none | 91.232.64.0/24 | No route object for it. A route object for 91.232.64.0/23 with origin AS57457 covers it (filters allowing more-specifics accept it). Add a route object with origin AS57457 in the RIR database for the space. |
| Route object: none | 91.232.65.0/24 | No route object for it. A route object for 91.232.64.0/23 with origin AS57457 covers it (filters allowing more-specifics accept it). Add a route object with origin AS57457 in the RIR database for the space. |
| Route object: none | 91.232.66.0/24 | No route object for it. A route object for 91.232.66.0/23 with origin AS57457 covers it (filters allowing more-specifics accept it). Add a route object with origin AS57457 in the RIR database for the space. |
| Route object: none | 91.232.67.0/24 | No route object for it. A route object for 91.232.66.0/23 with origin AS57457 covers it (filters allowing more-specifics accept it). Add a route object with origin AS57457 in the RIR database for the space. |
| Route object: none | 91.232.68.0/24 | No route object for it. A route object for 91.232.68.0/23 with origin AS57457 covers it (filters allowing more-specifics accept it). Add a route object with origin AS57457 in the RIR database for the space. |
| Route object: none | 91.232.69.0/24 | No route object for it. A route object for 91.232.68.0/23 with origin AS57457 covers it (filters allowing more-specifics accept it). Add a route object with origin AS57457 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS57457 whose prefix no peer sees AS57457 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 91.232.64.0/22 | RIPE | No ROA |
| 91.232.64.0/23 | RIPE | No ROA |
| 91.232.66.0/23 | RIPE | No ROA |
| 91.232.68.0/23 | RIPE | No ROA |
| 185.210.200.0/22 | RIPE | No ROA |
| 185.210.202.0/24 | 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.