Network · data from 2026-11-12
AS61068 NECSTEL
Registry name: NECSTEL-AS OOO "NECSTEL", RU · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS61068, 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.
| 146.19.209.0/24 | No ROA | RIR databaseRIPE | 673 100% |
| 77.105.167.0/24 | No ROA | RIR databaseRIPE | 671 100% |
| 185.9.76.0/22 | No ROA | RIR databaseRIPE | 671 100% |
| 185.9.78.0/24 | No ROA | RIR databaseRIPE | 671 100% |
| 185.20.44.0/22 | No ROA | RIR databaseRIPE | 671 100% |
| 185.20.45.0/24 | No ROA | RIR databaseRIPE | 671 100% |
| 193.23.50.0/24 | No ROA | RIR databaseRIPE | 671 100% |
| 195.88.69.0/24 | No ROA | RIR databaseRIPE | 671 100% |
AS-SET
AS61068'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 9 are in fix.csv.
- ROA: none8
- Route object: not announced1
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 146.19.209.0/24 | No ROA covers it. Add a ROA for AS61068, maxLength 24. |
| ROA: none | 77.105.167.0/24 | No ROA covers it. Add a ROA for AS61068, maxLength 24. |
| ROA: none | 185.9.76.0/22 | No ROA covers it. Add a ROA for AS61068, maxLength 22. |
| ROA: none | 185.9.78.0/24 | No ROA covers it. Add a ROA for AS61068, maxLength 24. |
| ROA: none | 185.20.44.0/22 | No ROA covers it. Add a ROA for AS61068, maxLength 22. |
| ROA: none | 185.20.45.0/24 | No ROA covers it. Add a ROA for AS61068, maxLength 24. |
| ROA: none | 193.23.50.0/24 | No ROA covers it. Add a ROA for AS61068, maxLength 24. |
| ROA: none | 195.88.69.0/24 | No ROA covers it. Add a ROA for AS61068, maxLength 24. |
Route objects not announced
Route objects with origin AS61068 whose prefix no peer sees AS61068 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 2a00:4d20::/32 | 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.