Network · data from 2026-11-12
AS47473 Ruzzo Reti S.p.a.
Registry name: RUZZO-AS Ruzzo Reti S.p.a., IT · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS47473, 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.
| 93.186.80.0/21 | Valid | Nonecovered by 93.186.80.0/20 | 673 100% |
| 93.186.88.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 93.186.89.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 93.186.90.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 93.186.91.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 93.186.92.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 93.186.93.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 93.186.94.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 93.186.95.0/24 | Valid | RIR databaseRIPE | 673 100% |
AS-SET
AS47473'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 11 are in fix.csv.
- Route object: none1
- Route object: not announced10
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: none | 93.186.80.0/21 | No route object for it. A route object for 93.186.80.0/20 with origin AS47473 covers it (filters allowing more-specifics accept it). Add a route object with origin AS47473 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS47473 whose prefix no peer sees AS47473 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 93.186.80.0/20 | RIPE | Valid |
| 93.186.80.0/24 | RIPE | Valid |
| 93.186.81.0/24 | RIPE | Valid |
| 93.186.82.0/24 | RIPE | Valid |
| 93.186.83.0/24 | RIPE | Valid |
| 93.186.84.0/24 | RIPE | Valid |
| 93.186.85.0/24 | RIPE | Valid |
| 93.186.86.0/24 | RIPE | Valid |
| 93.186.87.0/24 | RIPE | Valid |
| 2a02:518::/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.