Network · data from 2026-11-12
AS52008 NESTER-NET NesterTelecom LLC
Registry name: NESTER-NET NesterTelecom LLC, RU · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS52008, 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.221.176.0/23 | No ROA | RIR databaseRIPE | 672 100% |
| 91.238.28.0/23 | No ROA | RIR databaseRIPE | 669 99% |
| 2a03:5a00::/48 | No ROA | RIR databaseRIPE | 635 100% |
| 95.81.116.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 185.58.206.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 185.172.128.0/24 | Valid | RIR databaseRIPE | 673 100% |
AS-SET
AS52008 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 7 are in fix.csv.
- ROA: none3
- Route object: not announced4
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 91.221.176.0/23 | No ROA covers it. Add a ROA for AS52008, maxLength 23. |
| ROA: none | 91.238.28.0/23 | No ROA covers it. Add a ROA for AS52008, maxLength 23. |
| ROA: none | 2a03:5a00::/48 | No ROA covers it. Add a ROA for AS52008, maxLength 48. |
Route objects not announced
Route objects with origin AS52008 whose prefix no peer sees AS52008 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 91.221.176.0/24 | RIPE | No ROA |
| 91.221.177.0/24 | RIPE | No ROA |
| 91.238.28.0/24 | RIPE | No ROA |
| 91.238.29.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.