Network · data from 2026-11-12
AS34618 PROMETEO-AS Prometeo S.r.l.
Registry name: PROMETEO-AS Prometeo S.r.l., IT · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS34618, 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.
| 46.254.40.0/21 | No ROA | RIR databaseRIPE | 673 100% |
| 95.131.56.0/21 | No ROA | RIR databaseRIPE | 673 100% |
| 185.92.104.0/22 | No ROA | RIR databaseRIPE | 673 100% |
| 193.238.76.0/23 | No ROA | RIR databaseRIPE | 673 100% |
| 193.238.78.0/23 | No ROA | RIR databaseRIPE | 673 100% |
AS-SET
AS34618 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 5 are in fix.csv.
- ROA: none5
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 46.254.40.0/21 | No ROA covers it. Add a ROA for AS34618, maxLength 21. |
| ROA: none | 95.131.56.0/21 | No ROA covers it. Add a ROA for AS34618, maxLength 21. |
| ROA: none | 185.92.104.0/22 | No ROA covers it. Add a ROA for AS34618, maxLength 22. |
| ROA: none | 193.238.76.0/23 | No ROA covers it. Add a ROA for AS34618, maxLength 23. |
| ROA: none | 193.238.78.0/23 | No ROA covers it. Add a ROA for AS34618, maxLength 23. |
Route objects not announced
Every route object with origin AS34618 is announced.
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.