Network · data from 2026-11-12
AS58254 NANOTELECOM-AS
Registry name: NANOTELECOM-AS Nano Telecom LLC, UZ · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS58254, 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.240.12.0/22 | No ROA | RIR databaseRIPE | 673 100% |
| 91.240.14.0/24 | No ROA | RIR databaseRIPE | 673 100% |
| 185.166.255.0/24 | No ROA | RIR databaseRIPE | 673 100% |
| 95.47.153.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 146.120.16.0/22 | Valid | RIR databaseRIPE | 673 100% |
| 146.120.16.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 146.120.17.0/24 | Valid | RIR databaseRIPE | 673 100% |
AS-SET
AS58254's PeeringDB record names no 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 8 are in fix.csv.
- ROA: none3
- Route object: not announced5
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 91.240.12.0/22 | No ROA covers it. Add a ROA for AS58254, maxLength 22. |
| ROA: none | 91.240.14.0/24 | No ROA covers it. Add a ROA for AS58254, maxLength 24. |
| ROA: none | 185.166.255.0/24 | No ROA covers it. Add a ROA for AS58254, maxLength 24. |
Route objects not announced
Route objects with origin AS58254 whose prefix no peer sees AS58254 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 91.240.12.0/24 | RIPE | No ROA |
| 91.240.13.0/24 | RIPE | No ROA |
| 91.240.15.0/24 | RIPE | No ROA |
| 146.120.18.0/24 | RIPE | Valid |
| 146.120.19.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.