Network · data from 2026-11-12
AS198128 Connecting Project
Registry name: ASN-CONNECTING Connecting Project s.r.l., IT · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS198128, 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.
| 128.127.56.0/21 | No ROA | RIR databaseRIPE | 673 100% |
| 185.103.52.0/22 | No ROA | RIR databaseRIPE | 673 100% |
| 82.24.201.0/24 | Valid | RIR databaseRADB, RIPE | 673 100% |
| 82.38.84.0/22 | Valid | RIR databaseRADB, RIPE | 673 100% |
| 82.109.200.0/22 | Valid | RIR databaseRADB, RIPE | 673 100% |
| 167.148.36.0/22 | Valid | RIR databaseRADB, RIPE | 673 100% |
| 193.207.32.0/22 | Valid | RIR databaseRIPE | 673 100% |
| 193.207.36.0/22 | Valid | RIR databaseRIPE | 673 100% |
| 193.207.40.0/22 | Valid | RIR databaseRIPE | 673 100% |
| 193.207.44.0/22 | Valid | RIR databaseRIPE | 673 100% |
AS-SET
AS198128'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 3 are in fix.csv.
- ROA: none2
- Route object: not announced1
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 128.127.56.0/21 | No ROA covers it. Add a ROA for AS198128, maxLength 21. |
| ROA: none | 185.103.52.0/22 | No ROA covers it. Add a ROA for AS198128, maxLength 22. |
Route objects not announced
Route objects with origin AS198128 whose prefix no peer sees AS198128 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 2a05:fe00::/29 | 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.