Network · data from 2026-11-12
AS205207 AbreNik-Cloud Padiz Dadeh Resan PJSC
Registry name: AbreNik-Cloud Padiz Dadeh Resan PJSC, IR · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS205207, 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.
| 194.26.64.0/24 | No ROA | None | 638 95% |
| 92.242.210.0/24 | Valid | Other origin only | 670 100% |
| 5.160.132.0/24 | Valid | RIR databaseRIPE | 669 99% |
| 5.160.153.0/24 | Valid | RIR databaseRIPE | 669 99% |
| 5.160.177.0/24 | Valid | RIR databaseRIPE | 669 99% |
| 5.160.203.0/24 | Valid | RIR databaseRIPE | 669 99% |
| 5.160.208.0/24 | Valid | RIR databaseRIPE | 669 99% |
| 77.104.92.0/24 | Valid | RIR databaseRIPE | 669 99% |
| 77.104.116.0/24 | Valid | RIR databaseRIPE | 669 99% |
| 77.104.117.0/24 | Valid | RIR databaseRIPE | 669 99% |
| 77.104.118.0/24 | Valid | RIR databaseRIPE | 669 99% |
| 77.104.119.0/24 | Valid | RIR databaseRIPE | 669 99% |
| 77.104.127.0/24 | Valid | RIR databaseRIPE | 669 99% |
| 77.237.81.0/24 | Valid | RIR databaseRIPE | 669 99% |
AS-SET
AS205207 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 25 are in fix.csv.
- ROA: none1
- Route object: none2
- Route object: not announced22
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 194.26.64.0/24 | No ROA covers it. Add a ROA for AS205207, maxLength 24. |
| Route object: none | 194.26.64.0/24 | No route object for it. Add a route object with origin AS205207 in the RIR database for the space. |
| Route object: none | 92.242.210.0/24 | Route objects for it name AS42337, AS2052207. Add a route object with origin AS205207 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS205207 whose prefix no peer sees AS205207 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 5.160.29.0/24 | RIPE | Invalid: origin |
| 5.160.49.0/24 | RIPE | Invalid: origin |
| 5.160.50.0/24 | RIPE | Invalid: origin |
| 46.209.58.0/24 | RIPE | Invalid: origin |
| 46.209.62.0/24 | RIPE | Invalid: origin |
| 46.209.69.0/24 | RIPE | Invalid: origin |
| 46.209.77.0/24 | RIPE | Invalid: origin |
| 46.209.95.0/24 | RIPE | Invalid: origin |
| 46.209.149.0/24 | RIPE | Invalid: origin |
| 77.104.64.0/18 | RIPE | Invalid: origin |
| 77.104.64.0/19 | RIPE | Invalid: origin |
| 77.104.66.0/24 | RIPE | Invalid: origin |
| 77.104.72.0/21 | RIPE | Invalid: origin |
| 77.104.73.0/24 | RIPE | Invalid: origin |
| 77.104.75.0/24 | RIPE | Invalid: origin |
| 77.104.106.0/24 | RIPE | Invalid: origin |
| 77.237.64.0/20 | RIPE | Invalid: origin |
| 77.237.68.0/24 | RIPE | Invalid: origin |
| 81.12.77.0/24 | RIPE | Valid |
| 185.14.160.0/22 | RIPE | Invalid: origin |
| 185.14.162.0/24 | RIPE | Invalid: origin |
| 185.225.240.0/22 | 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.