Network · data from 2026-11-12
AS10718 CNO-FINANCIAL-GROUP - CNO Financial Group, Inc.
Registry name: CNO-FINANCIAL-GROUP - CNO Financial Group, Inc., US · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS10718, 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.
| 205.144.112.0/24 | No ROA | Nonecovered by 205.144.112.0/20 | 672 100% |
| 205.144.115.0/24 | No ROA | Nonecovered by 205.144.112.0/20 | 672 100% |
| 205.144.119.0/24 | No ROA | Other origin onlycovered by 205.144.112.0/20 | 672 100% |
| 205.144.120.0/24 | No ROA | Other origin onlycovered by 205.144.112.0/20 | 672 100% |
| 205.144.121.0/24 | No ROA | Nonecovered by 205.144.112.0/20 | 672 100% |
| 205.144.124.0/24 | No ROA | Nonecovered by 205.144.112.0/20 | 672 100% |
| 205.144.125.0/24 | No ROA | Other origin onlycovered by 205.144.112.0/20 | 672 100% |
| 205.144.126.0/24 | No ROA | Nonecovered by 205.144.112.0/20 | 672 100% |
| 205.144.127.0/24 | No ROA | Nonecovered by 205.144.112.0/20 | 672 100% |
| 205.144.123.0/24 | No ROA | Nonecovered by 205.144.112.0/20 | 671 100% |
AS-SET
AS10718 isn't in PeeringDB, where networks name their 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 23 are in fix.csv.
- ROA: none10
- Route object: none10
- Route object: not announced3
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 205.144.112.0/24 | No ROA covers it. Add a ROA for AS10718, maxLength 24. |
| Route object: none | 205.144.112.0/24 | No route object for it. A route object for 205.144.112.0/20 with origin AS10718 covers it (filters allowing more-specifics accept it). Add a route object with origin AS10718 in the RIR database for the space. |
| ROA: none | 205.144.115.0/24 | No ROA covers it. Add a ROA for AS10718, maxLength 24. |
| Route object: none | 205.144.115.0/24 | No route object for it. A route object for 205.144.112.0/20 with origin AS10718 covers it (filters allowing more-specifics accept it). Add a route object with origin AS10718 in the RIR database for the space. |
| ROA: none | 205.144.119.0/24 | No ROA covers it. Add a ROA for AS10718, maxLength 24. |
| Route object: none | 205.144.119.0/24 | Route objects for it name AS46887. A route object for 205.144.112.0/20 with origin AS10718 covers it (filters allowing more-specifics accept it). Add a route object with origin AS10718 in the RIR database for the space. |
| ROA: none | 205.144.120.0/24 | No ROA covers it. Add a ROA for AS10718, maxLength 24. |
| Route object: none | 205.144.120.0/24 | Route objects for it name AS17054. A route object for 205.144.112.0/20 with origin AS10718 covers it (filters allowing more-specifics accept it). Add a route object with origin AS10718 in the RIR database for the space. |
| ROA: none | 205.144.121.0/24 | No ROA covers it. Add a ROA for AS10718, maxLength 24. |
| Route object: none | 205.144.121.0/24 | No route object for it. A route object for 205.144.112.0/20 with origin AS10718 covers it (filters allowing more-specifics accept it). Add a route object with origin AS10718 in the RIR database for the space. |
| ROA: none | 205.144.124.0/24 | No ROA covers it. Add a ROA for AS10718, maxLength 24. |
| Route object: none | 205.144.124.0/24 | No route object for it. A route object for 205.144.112.0/20 with origin AS10718 covers it (filters allowing more-specifics accept it). Add a route object with origin AS10718 in the RIR database for the space. |
| ROA: none | 205.144.125.0/24 | No ROA covers it. Add a ROA for AS10718, maxLength 24. |
| Route object: none | 205.144.125.0/24 | Route objects for it name AS17054. A route object for 205.144.112.0/20 with origin AS10718 covers it (filters allowing more-specifics accept it). Add a route object with origin AS10718 in the RIR database for the space. |
| ROA: none | 205.144.126.0/24 | No ROA covers it. Add a ROA for AS10718, maxLength 24. |
| Route object: none | 205.144.126.0/24 | No route object for it. A route object for 205.144.112.0/20 with origin AS10718 covers it (filters allowing more-specifics accept it). Add a route object with origin AS10718 in the RIR database for the space. |
| ROA: none | 205.144.127.0/24 | No ROA covers it. Add a ROA for AS10718, maxLength 24. |
| Route object: none | 205.144.127.0/24 | No route object for it. A route object for 205.144.112.0/20 with origin AS10718 covers it (filters allowing more-specifics accept it). Add a route object with origin AS10718 in the RIR database for the space. |
| ROA: none | 205.144.123.0/24 | No ROA covers it. Add a ROA for AS10718, maxLength 24. |
| Route object: none | 205.144.123.0/24 | No route object for it. A route object for 205.144.112.0/20 with origin AS10718 covers it (filters allowing more-specifics accept it). Add a route object with origin AS10718 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS10718 whose prefix no peer sees AS10718 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 199.83.0.0/21 | RADB | No ROA |
| 205.144.112.0/20 | RADB | No ROA |
| 205.144.114.0/24 | 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.