Network · data from 2026-11-12
AS200984 NUOVARETI
Registry name: NUOVARETI-AS NUOVAFIBER S.R.L., IT · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS200984, 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.
| 154.56.216.0/22 | No ROA | Other IRR onlyRADB | 673 100% |
| 45.13.80.0/22 | No ROA | RIR databaseRIPE | 673 100% |
| 185.89.180.0/22 | No ROA | RIR databaseRIPE | 673 100% |
| 2.58.184.0/22 | Valid | RIR databaseRIPE | 673 100% |
AS-SET
AS200984'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 10 are in fix.csv.
- ROA: none3
- Route object: RIR1
- Route object: not announced6
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 154.56.216.0/22 | No ROA covers it. Add a ROA for AS200984, maxLength 22. |
| Route object: RIR | 154.56.216.0/22 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 45.13.80.0/22 | No ROA covers it. Add a ROA for AS200984, maxLength 22. |
| ROA: none | 185.89.180.0/22 | No ROA covers it. Add a ROA for AS200984, maxLength 22. |
Route objects not announced
Route objects with origin AS200984 whose prefix no peer sees AS200984 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 2.58.184.0/24 | RIPE | Invalid: maxLength |
| 2.58.186.0/24 | RIPE | Invalid: maxLength |
| 185.89.180.0/24 | RIPE | No ROA |
| 185.89.181.0/24 | RIPE | No ROA |
| 185.89.182.0/24 | RIPE | No ROA |
| 185.89.183.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.