Announced routes
Every prefix a peer of the route collectors sees with origin AS269795, 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.
| 45.184.231.0/24 | Valid | Nonecovered by 45.184.228.0/22 | 672 100% |
| 45.184.228.0/24 | Valid | Nonecovered by 45.184.228.0/22 | 671 100% |
| 45.184.229.0/24 | Valid | Nonecovered by 45.184.228.0/22 | 671 100% |
| 179.60.222.0/24 | Valid | Nonecovered by 179.60.220.0/22 | 671 100% |
| 45.184.230.0/24 | Valid | Nonecovered by 45.184.228.0/22 | 670 100% |
| 179.60.220.0/24 | Valid | Nonecovered by 179.60.220.0/22 | 670 100% |
| 179.60.221.0/24 | Valid | Nonecovered by 179.60.220.0/22 | 670 100% |
| 179.60.223.0/24 | Valid | Nonecovered by 179.60.220.0/22 | 669 99% |
AS-SET
AS269795'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 | 45.184.231.0/24 | No route object for it. A route object for 45.184.228.0/22 with origin AS269795 covers it (filters allowing more-specifics accept it). Add a route object with origin AS269795 in the RIR database for the space. |
| Route object: none | 45.184.228.0/24 | No route object for it. A route object for 45.184.228.0/22 with origin AS269795 covers it (filters allowing more-specifics accept it). Add a route object with origin AS269795 in the RIR database for the space. |
| Route object: none | 45.184.229.0/24 | No route object for it. A route object for 45.184.228.0/22 with origin AS269795 covers it (filters allowing more-specifics accept it). Add a route object with origin AS269795 in the RIR database for the space. |
| Route object: none | 179.60.222.0/24 | No route object for it. A route object for 179.60.220.0/22 with origin AS269795 covers it (filters allowing more-specifics accept it). Add a route object with origin AS269795 in the RIR database for the space. |
| Route object: none | 45.184.230.0/24 | No route object for it. A route object for 45.184.228.0/22 with origin AS269795 covers it (filters allowing more-specifics accept it). Add a route object with origin AS269795 in the RIR database for the space. |
| Route object: none | 179.60.220.0/24 | No route object for it. A route object for 179.60.220.0/22 with origin AS269795 covers it (filters allowing more-specifics accept it). Add a route object with origin AS269795 in the RIR database for the space. |
| Route object: none | 179.60.221.0/24 | No route object for it. A route object for 179.60.220.0/22 with origin AS269795 covers it (filters allowing more-specifics accept it). Add a route object with origin AS269795 in the RIR database for the space. |
| Route object: none | 179.60.223.0/24 | No route object for it. A route object for 179.60.220.0/22 with origin AS269795 covers it (filters allowing more-specifics accept it). Add a route object with origin AS269795 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS269795 whose prefix no peer sees AS269795 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 45.184.228.0/22 | RADB | Valid |
| 179.60.220.0/22 | RADB | Valid |
| 2803:b360::/32 | RADB | No ROA |
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.