Network · data from 2026-11-12
AS20895 UGTEL "Yuzhniy TELECOM" ltd.
Registry name: UGTEL "Yuzhniy TELECOM" ltd., RU · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS20895, 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.
| 81.26.129.29/32 | No ROA | Nonecovered by 81.26.129.0/24 | 1 0%low visibility |
| 80.240.48.0/20 | No ROA | RIR databaseRIPE | 673 100% |
| 80.240.48.0/22 | No ROA | RIR databaseRIPE | 673 100% |
| 80.240.52.0/22 | No ROA | RIR databaseRIPE | 673 100% |
| 80.240.56.0/22 | No ROA | RIR databaseRIPE | 673 100% |
| 80.240.60.0/22 | No ROA | RIR databaseRIPE | 673 100% |
| 81.26.128.0/20 | No ROA | RIR databaseRIPE | 673 100% |
| 81.26.128.0/22 | No ROA | RIR databaseRADB, RIPE | 673 100% |
| 81.26.132.0/22 | No ROA | RIR databaseRIPE | 673 100% |
| 81.26.136.0/22 | No ROA | RIR databaseRADB, RIPE | 673 100% |
| 81.26.140.0/22 | No ROA | RIR databaseRIPE | 673 100% |
| 185.20.132.0/23 | No ROA | RIR databaseRIPE | 673 100% |
| 185.20.134.0/24 | No ROA | RIR databaseRIPE | 673 100% |
| 2a04:d80::/32 | No ROA | RIR databaseRIPE | 636 100% |
AS-SET
AS20895 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 29 are in fix.csv.
- ROA: none14
- Route object: none1
- Route object: not announced14
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 81.26.129.29/32 | No ROA covers it. Add a ROA for AS20895, maxLength 32. |
| Route object: none | 81.26.129.29/32 | No route object for it. A route object for 81.26.129.0/24 with origin AS20895 covers it (too long for filters allowing more-specifics up to /24). Add a route object with origin AS20895 in the RIR database for the space. |
| ROA: none | 80.240.48.0/20 | No ROA covers it. Add a ROA for AS20895, maxLength 20. |
| ROA: none | 80.240.48.0/22 | No ROA covers it. Add a ROA for AS20895, maxLength 22. |
| ROA: none | 80.240.52.0/22 | No ROA covers it. Add a ROA for AS20895, maxLength 22. |
| ROA: none | 80.240.56.0/22 | No ROA covers it. Add a ROA for AS20895, maxLength 22. |
| ROA: none | 80.240.60.0/22 | No ROA covers it. Add a ROA for AS20895, maxLength 22. |
| ROA: none | 81.26.128.0/20 | No ROA covers it. Add a ROA for AS20895, maxLength 20. |
| ROA: none | 81.26.128.0/22 | No ROA covers it. Add a ROA for AS20895, maxLength 22. |
| ROA: none | 81.26.132.0/22 | No ROA covers it. Add a ROA for AS20895, maxLength 22. |
| ROA: none | 81.26.136.0/22 | No ROA covers it. Add a ROA for AS20895, maxLength 22. |
| ROA: none | 81.26.140.0/22 | No ROA covers it. Add a ROA for AS20895, maxLength 22. |
| ROA: none | 185.20.132.0/23 | No ROA covers it. Add a ROA for AS20895, maxLength 23. |
| ROA: none | 185.20.134.0/24 | No ROA covers it. Add a ROA for AS20895, maxLength 24. |
| ROA: none | 2a04:d80::/32 | No ROA covers it. Add a ROA for AS20895, maxLength 32. |
Route objects not announced
Route objects with origin AS20895 whose prefix no peer sees AS20895 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 81.26.128.0/21 | RADB | No ROA |
| 81.26.129.0/24 | RADB, RIPE | No ROA |
| 81.26.130.0/23 | RADB | No ROA |
| 81.26.131.0/24 | RADB | No ROA |
| 81.26.132.0/24 | RADB | No ROA |
| 81.26.134.0/23 | RADB | No ROA |
| 81.26.134.0/24 | RADB | No ROA |
| 81.26.135.0/24 | RIPE | No ROA |
| 81.26.136.0/23 | RADB | No ROA |
| 81.26.136.0/24 | RADB | No ROA |
| 81.26.138.0/23 | RADB | No ROA |
| 81.26.140.0/23 | RADB | No ROA |
| 185.20.132.0/24 | RIPE | No ROA |
| 185.20.133.0/24 | 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.