Network · data from 2026-11-12
AS20661 TurkmenTelecom-AS State Company of Electro Communications Turkmentelecom
Registry name: TurkmenTelecom-AS State Company of Electro Communications Turkmentelecom, TM · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS20661, 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.
| 95.85.101.0/24 | Valid | Nonecovered by 95.85.100.0/22 | 672 100% |
| 95.85.121.0/24 | Valid | Nonecovered by 95.85.96.0/19 | 670 100% |
| 95.85.96.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 95.85.98.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 95.85.99.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 95.85.100.0/22 | Valid | RIR databaseRIPE | 673 100% |
| 103.220.0.0/22 | Valid | RIR databaseRIPE | 673 100% |
| 119.235.112.0/20 | Valid | RIR databaseRIPE | 673 100% |
| 177.93.143.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 216.250.8.0/21 | Valid | RIR databaseRIPE | 673 100% |
| 217.174.224.0/20 | Valid | RIR databaseRIPE | 673 100% |
| 217.174.224.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 217.174.225.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 217.174.227.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 95.85.100.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 95.85.104.0/23 | Valid | RIR databaseRIPE | 672 100% |
| 95.85.104.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 95.85.106.0/23 | Valid | RIR databaseRIPE | 672 100% |
| 95.85.96.0/19 | Valid | RIR databaseRIPE | 670 100% |
| 2a05:2180::/29 | Valid | RIR databaseRIPE | 634 100% |
AS-SET
AS20661 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 21 are in fix.csv.
- Route object: none2
- Route object: not announced19
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: none | 95.85.101.0/24 | No route object for it. A route object for 95.85.100.0/22 with origin AS20661 covers it (filters allowing more-specifics accept it). Add a route object with origin AS20661 in the RIR database for the space. |
| Route object: none | 95.85.121.0/24 | No route object for it. A route object for 95.85.96.0/19 with origin AS20661 covers it (filters allowing more-specifics accept it). Add a route object with origin AS20661 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS20661 whose prefix no peer sees AS20661 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 95.85.97.0/24 | RIPE | Valid |
| 95.85.98.0/23 | RIPE | Valid |
| 95.85.104.0/22 | RIPE | Valid |
| 95.85.106.0/24 | RIPE | Valid |
| 95.85.111.0/24 | RIPE | Valid |
| 95.85.127.0/24 | RIPE | Valid |
| 217.174.226.0/24 | RIPE | Valid |
| 217.174.228.0/24 | RIPE | Valid |
| 217.174.229.0/24 | RIPE | Valid |
| 217.174.230.0/24 | RIPE | Valid |
| 217.174.231.0/24 | RIPE | Valid |
| 217.174.232.0/24 | RIPE | Valid |
| 217.174.233.0/24 | RIPE | Valid |
| 217.174.234.0/24 | RIPE | Valid |
| 217.174.235.0/24 | RIPE | Valid |
| 217.174.236.0/24 | RIPE | Valid |
| 217.174.237.0/24 | RIPE | Valid |
| 217.174.238.0/24 | RIPE | Valid |
| 217.174.239.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.