Network · data from 2026-11-12
AS22346 NRZ-NETWORK - Newroads Telecom
Registry name: NRZ-NETWORK - Newroads Telecom, US · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS22346, 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.
| 72.18.32.0/20 | No ROA | RIR databaseARIN, RADB | 673 100% |
| 162.211.16.0/23 | No ROA | RIR databaseARIN | 673 100% |
| 209.183.160.0/20 | No ROA | RIR databaseARIN, RADB | 673 100% |
| 2607:f6e0::/32 | No ROA | RIR databaseARIN | 635 100% |
AS-SET
AS22346 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 10 are in fix.csv.
- ROA: none4
- Route object: not announced6
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 72.18.32.0/20 | No ROA covers it. Add a ROA for AS22346, maxLength 20. |
| ROA: none | 162.211.16.0/23 | No ROA covers it. Add a ROA for AS22346, maxLength 23. |
| ROA: none | 209.183.160.0/20 | No ROA covers it. Add a ROA for AS22346, maxLength 20. |
| ROA: none | 2607:f6e0::/32 | No ROA covers it. Add a ROA for AS22346, maxLength 32. |
Route objects not announced
Route objects with origin AS22346 whose prefix no peer sees AS22346 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 23.236.16.0/20 | RADB | No ROA |
| 72.18.32.0/21 | ARIN | No ROA |
| 72.18.40.0/21 | ARIN | No ROA |
| 162.211.16.0/22 | RADB | No ROA |
| 162.211.18.0/23 | ARIN | No ROA |
| 162.211.18.0/24 | ARIN | 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.