Announced routes
Every prefix a peer of the route collectors sees with origin AS212194, 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.
| 2.26.202.0/23 | Valid | Nonecovered by 2.26.200.0/21 | 671 100% |
| 2.26.204.0/23 | Valid | Nonecovered by 2.26.200.0/21 | 671 100% |
| 2.26.200.0/23 | Valid | Nonecovered by 2.26.200.0/21 | 668 99% |
| 2a14:67c4:11::/48 | Valid | Nonecovered by 2a14:67c4::/40 | 635 100% |
| 2a14:67c4:12::/48 | Valid | Nonecovered by 2a14:67c4::/40 | 635 100% |
| 2a14:67c4:13::/48 | Valid | Nonecovered by 2a14:67c4::/40 | 635 100% |
| 2.26.206.0/24 | Valid | Nonecovered by 2.26.200.0/21 | 2 0%low visibility |
| 2.27.212.0/24 | Valid | Nonecovered by 2.27.212.0/23 | 2 0%low visibility |
| 2.26.200.0/21 | Valid | RIR databaseRIPE | 673 100% |
| 2.27.146.0/23 | Valid | RIR databaseRIPE | 673 100% |
| 2.27.212.0/23 | Valid | RIR databaseRIPE | 673 100% |
| 169.40.128.0/24 | Valid | RIR databaseRADB, RIPE | 672 100% |
| 151.242.65.0/24 | Valid | RIR databaseRADB, RIPE | 671 100% |
AS-SET
AS212194'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 11 are in fix.csv.
- Route object: none8
- Route object: not announced3
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: none | 2.26.202.0/23 | No route object for it. A route object for 2.26.200.0/21 with origin AS212194 covers it (filters allowing more-specifics accept it). Add a route object with origin AS212194 in the RIR database for the space. |
| Route object: none | 2.26.204.0/23 | No route object for it. A route object for 2.26.200.0/21 with origin AS212194 covers it (filters allowing more-specifics accept it). Add a route object with origin AS212194 in the RIR database for the space. |
| Route object: none | 2.26.200.0/23 | No route object for it. A route object for 2.26.200.0/21 with origin AS212194 covers it (filters allowing more-specifics accept it). Add a route object with origin AS212194 in the RIR database for the space. |
| Route object: none | 2a14:67c4:11::/48 | No route object for it. A route object for 2a14:67c4::/40 with origin AS212194 covers it (filters allowing more-specifics accept it). Add a route object with origin AS212194 in the RIR database for the space. |
| Route object: none | 2a14:67c4:12::/48 | No route object for it. A route object for 2a14:67c4::/40 with origin AS212194 covers it (filters allowing more-specifics accept it). Add a route object with origin AS212194 in the RIR database for the space. |
| Route object: none | 2a14:67c4:13::/48 | No route object for it. A route object for 2a14:67c4::/40 with origin AS212194 covers it (filters allowing more-specifics accept it). Add a route object with origin AS212194 in the RIR database for the space. |
| Route object: none | 2.26.206.0/24 | No route object for it. A route object for 2.26.200.0/21 with origin AS212194 covers it (filters allowing more-specifics accept it). Add a route object with origin AS212194 in the RIR database for the space. |
| Route object: none | 2.27.212.0/24 | No route object for it. A route object for 2.27.212.0/23 with origin AS212194 covers it (filters allowing more-specifics accept it). Add a route object with origin AS212194 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS212194 whose prefix no peer sees AS212194 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 2a0f:e401:140::/44 | RADB | No ROA |
| 2a14:67c4::/40 | RIPE | Valid |
| 2a14:67c6::/32 | 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.