Network · data from 2026-11-12
AS39308 ASK-AS ANDISHE SABZ KHAZAR CO. P.J.S.
Registry name: ASK-AS ANDISHE SABZ KHAZAR CO. P.J.S., IR · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS39308, 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.
| 185.56.96.0/23 | Valid | Nonecovered by 185.56.96.0/22 | 672 100% |
| 185.56.98.0/24 | Valid | Nonecovered by 185.56.96.0/22 | 672 100% |
| 89.144.156.0/24 | Valid | Nonecovered by 89.144.152.0/21 | 671 100% |
| 95.81.76.0/22 | Valid | None | 671 100% |
| 89.144.128.0/18 | Valid | RIR databaseRIPE | 672 100% |
| 89.144.128.0/20 | Valid | RIR databaseRIPE | 672 100% |
| 89.144.130.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 89.144.144.0/20 | Valid | RIR databaseRIPE | 672 100% |
| 89.144.160.0/20 | Valid | RIR databaseRIPE | 672 100% |
| 89.144.176.0/20 | Valid | RIR databaseRIPE | 672 100% |
| 109.109.32.0/19 | Valid | RIR databaseRIPE | 672 100% |
| 159.20.96.0/20 | Valid | RIR databaseRIPE | 672 100% |
| 185.56.96.0/22 | Valid | RIR databaseRIPE | 672 100% |
AS-SET
AS39308 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 31 are in fix.csv.
- Route object: none4
- Route object: not announced27
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: none | 185.56.96.0/23 | No route object for it. A route object for 185.56.96.0/22 with origin AS39308 covers it (filters allowing more-specifics accept it). Add a route object with origin AS39308 in the RIR database for the space. |
| Route object: none | 185.56.98.0/24 | No route object for it. A route object for 185.56.96.0/22 with origin AS39308 covers it (filters allowing more-specifics accept it). Add a route object with origin AS39308 in the RIR database for the space. |
| Route object: none | 89.144.156.0/24 | No route object for it. A route object for 89.144.152.0/21 with origin AS39308 covers it (filters allowing more-specifics accept it). Add a route object with origin AS39308 in the RIR database for the space. |
| Route object: none | 95.81.76.0/22 | No route object for it. Add a route object with origin AS39308 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS39308 whose prefix no peer sees AS39308 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 89.144.128.0/19 | RIPE | Valid |
| 89.144.128.0/21 | RIPE | Valid |
| 89.144.128.0/24 | RIPE | Valid |
| 89.144.129.0/24 | RIPE | Valid |
| 89.144.131.0/24 | RIPE | Valid |
| 89.144.132.0/24 | RIPE | Valid |
| 89.144.133.0/24 | RIPE | Valid |
| 89.144.134.0/24 | RIPE | Valid |
| 89.144.135.0/24 | RIPE | Valid |
| 89.144.136.0/21 | RIPE | Valid |
| 89.144.136.0/24 | RIPE | Valid |
| 89.144.137.0/24 | RIPE | Valid |
| 89.144.138.0/24 | RIPE | Valid |
| 89.144.141.0/24 | RIPE | Valid |
| 89.144.142.0/24 | RIPE | Valid |
| 89.144.143.0/24 | RIPE | Valid |
| 89.144.144.0/21 | RIPE | Valid |
| 89.144.146.0/24 | RIPE | Valid |
| 89.144.152.0/21 | RIPE | Valid |
| 89.144.160.0/24 | RIPE | Valid |
| 89.144.183.0/24 | RIPE | Valid |
| 109.109.32.0/20 | RIPE | Invalid: maxLength |
| 109.109.32.0/22 | RIPE | Invalid: maxLength |
| 109.109.33.0/24 | RIPE | Invalid: maxLength |
| 109.109.40.0/24 | RIPE | Invalid: maxLength |
| 109.109.48.0/20 | RIPE | Invalid: maxLength |
| 2a00:1570::/32 | 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.