Announced routes
Every prefix a peer of the route collectors sees with origin AS34240, 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.
| 89.238.80.0/24 | Valid | Nonecovered by 89.238.64.0/18 | 673 100% |
| 89.238.85.0/24 | Valid | Nonecovered by 89.238.64.0/18 | 673 100% |
| 2.59.84.0/22 | Valid | RIR databaseRIPE | 673 100% |
| 89.238.64.0/18 | Valid | RIR databaseRIPE | 673 100% |
| 217.11.48.0/20 | Valid | RIR databaseRIPE | 673 100% |
| 2a00:1828::/32 | Valid | RIR databaseRIPE | 635 100% |
AS-SET
AS34240'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 2 are in fix.csv.
- Route object: none2
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: none | 89.238.80.0/24 | No route object for it. A route object for 89.238.64.0/18 with origin AS34240 covers it (filters allowing more-specifics accept it). Add a route object with origin AS34240 in the RIR database for the space. |
| Route object: none | 89.238.85.0/24 | No route object for it. A route object for 89.238.64.0/18 with origin AS34240 covers it (filters allowing more-specifics accept it). Add a route object with origin AS34240 in the RIR database for the space. |
Route objects not announced
Every route object with origin AS34240 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.