Announced routes
Every prefix a peer of the route collectors sees with origin AS34970, 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.
| 130.117.58.0/23 | No ROA | Other IRR onlyRADB | 673 100% |
| 91.195.206.0/23 | Valid | RIR databaseRIPE | 673 100% |
| 95.130.152.0/21 | Valid | RIR databaseRIPE | 673 100% |
| 185.55.144.0/22 | Valid | RIR databaseRIPE | 673 100% |
| 194.50.78.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 212.103.24.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 212.103.25.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 212.103.28.0/24 | Valid | RIR databaseRIPE | 673 100% |
AS-SET
AS34970'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: none1
- Route object: RIR1
- Route object: not announced1
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 130.117.58.0/23 | No ROA covers it. Add a ROA for AS34970, maxLength 23. |
| Route object: RIR | 130.117.58.0/23 | Route object only in RADB. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS34970 whose prefix no peer sees AS34970 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 80.245.42.0/23 | RIPE | Valid |
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.