Announced routes
Every prefix a peer of the route collectors sees with origin AS29238, 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.
| 217.21.152.0/24 | Valid | Nonecovered by 217.21.144.0/20 | 673 100% |
| 217.21.159.0/24 | Valid | Nonecovered by 217.21.144.0/20 | 673 100% |
| 79.98.112.0/21 | Valid | RIR databaseRIPE | 673 100% |
| 79.98.112.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 79.98.113.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 79.98.114.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 79.98.115.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 185.66.128.0/22 | Valid | RIR databaseRIPE | 673 100% |
| 217.21.144.0/20 | Valid | RIR databaseRIPE | 673 100% |
AS-SET
AS29238'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 7 are in fix.csv.
- Route object: none2
- Route object: not announced5
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: none | 217.21.152.0/24 | No route object for it. A route object for 217.21.144.0/20 with origin AS29238 covers it (filters allowing more-specifics accept it). Add a route object with origin AS29238 in the RIR database for the space. |
| Route object: none | 217.21.159.0/24 | No route object for it. A route object for 217.21.144.0/20 with origin AS29238 covers it (filters allowing more-specifics accept it). Add a route object with origin AS29238 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS29238 whose prefix no peer sees AS29238 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 79.98.116.0/24 | RIPE | Valid |
| 217.21.145.0/24 | RIPE | Valid |
| 217.21.146.0/24 | RIPE | Valid |
| 217.21.148.0/22 | RIPE | Valid |
| 217.21.158.0/24 | 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.