Announced routes
Every prefix a peer of the route collectors sees with origin AS34766, 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.
| 194.59.216.0/23 | Valid | Nonecovered by 194.59.216.0/22 | 673 100% |
| 194.59.218.0/23 | Valid | Nonecovered by 194.59.216.0/22 | 673 100% |
| 2a07:a80::/40 | Valid | Nonecovered by 2a07:a80::/29 | 635 100% |
| 2a07:a80:200::/40 | Valid | Nonecovered by 2a07:a80::/29 | 635 100% |
| 2a07:a80:300::/40 | Valid | Nonecovered by 2a07:a80::/29 | 635 100% |
| 31.22.84.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 95.142.110.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 178.237.34.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 185.138.56.0/22 | Valid | RIR databaseRIPE | 673 100% |
| 185.138.56.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 185.138.57.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 193.202.88.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 194.99.46.0/23 | Valid | RIR databaseRIPE | 673 100% |
| 45.148.186.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 2a07:a80::/29 | Valid | RIR databaseRIPE | 635 100% |
AS-SET
AS34766'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 8 are in fix.csv.
- Route object: none5
- Route object: not announced3
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: none | 194.59.216.0/23 | No route object for it. A route object for 194.59.216.0/22 with origin AS34766 covers it (filters allowing more-specifics accept it). Add a route object with origin AS34766 in the RIR database for the space. |
| Route object: none | 194.59.218.0/23 | No route object for it. A route object for 194.59.216.0/22 with origin AS34766 covers it (filters allowing more-specifics accept it). Add a route object with origin AS34766 in the RIR database for the space. |
| Route object: none | 2a07:a80::/40 | No route object for it. A route object for 2a07:a80::/29 with origin AS34766 covers it (filters allowing more-specifics accept it). Add a route object with origin AS34766 in the RIR database for the space. |
| Route object: none | 2a07:a80:200::/40 | No route object for it. A route object for 2a07:a80::/29 with origin AS34766 covers it (filters allowing more-specifics accept it). Add a route object with origin AS34766 in the RIR database for the space. |
| Route object: none | 2a07:a80:300::/40 | No route object for it. A route object for 2a07:a80::/29 with origin AS34766 covers it (filters allowing more-specifics accept it). Add a route object with origin AS34766 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS34766 whose prefix no peer sees AS34766 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 194.59.216.0/22 | RIPE | Valid |
| 194.99.44.0/23 | RIPE | Valid |
| 2a00:4140::/32 | RIPE | Invalid: origin |
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.