Network · data from 2026-11-12
AS25505 CHEREDA-KV-AS LUX GROUP, LLC
Registry name: CHEREDA-KV-AS LUX GROUP, LLC, UA · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS25505, 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.19.105.0/24 | No ROA | RIR databaseRIPE | 673 100% |
| 89.19.101.0/24 | No ROA | RIR databaseRIPE | 671 100% |
| 89.19.112.0/21 | No ROA | RIR databaseRIPE | 671 100% |
| 89.19.104.0/22 | No ROA | RIR databaseRIPE | 8 1%low visibility |
| 195.43.40.0/22 | No ROA | RIR databaseRIPE | 8 1%low visibility |
| 195.43.40.0/23 | No ROA | RIR databaseRIPE | 8 1%low visibility |
| 195.43.42.0/23 | No ROA | RIR databaseRIPE | 8 1%low visibility |
| 89.19.100.0/22 | No ROA | RIR databaseRIPE | 6 1%low visibility |
| 89.19.96.0/23 | No ROA | RIR databaseRIPE | 4 1%low visibility |
| 89.19.108.0/24 | No ROA | RIR databaseRIPE | 4 1%low visibility |
| 89.19.96.0/20 | No ROA | RIR databaseRIPE | 3 0%low visibility |
AS-SET
AS25505 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 22 are in fix.csv.
- ROA: none11
- Route object: not announced11
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 89.19.105.0/24 | No ROA covers it. Add a ROA for AS25505, maxLength 24. |
| ROA: none | 89.19.101.0/24 | No ROA covers it. Add a ROA for AS25505, maxLength 24. |
| ROA: none | 89.19.112.0/21 | No ROA covers it. Add a ROA for AS25505, maxLength 21. |
| ROA: none | 89.19.104.0/22 | No ROA covers it. Add a ROA for AS25505, maxLength 22. |
| ROA: none | 195.43.40.0/22 | No ROA covers it. Add a ROA for AS25505, maxLength 22. |
| ROA: none | 195.43.40.0/23 | No ROA covers it. Add a ROA for AS25505, maxLength 23. |
| ROA: none | 195.43.42.0/23 | No ROA covers it. Add a ROA for AS25505, maxLength 23. |
| ROA: none | 89.19.100.0/22 | No ROA covers it. Add a ROA for AS25505, maxLength 22. |
| ROA: none | 89.19.96.0/23 | No ROA covers it. Add a ROA for AS25505, maxLength 23. |
| ROA: none | 89.19.108.0/24 | No ROA covers it. Add a ROA for AS25505, maxLength 24. |
| ROA: none | 89.19.96.0/20 | No ROA covers it. Add a ROA for AS25505, maxLength 20. |
Route objects not announced
Route objects with origin AS25505 whose prefix no peer sees AS25505 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 89.19.96.0/24 | RIPE | No ROA |
| 89.19.97.0/24 | RIPE | Invalid: origin |
| 89.19.100.0/24 | RIPE | No ROA |
| 89.19.102.0/24 | RIPE | No ROA |
| 89.19.103.0/24 | RIPE | No ROA |
| 89.19.104.0/24 | RIPE | No ROA |
| 89.19.106.0/24 | RIPE | No ROA |
| 89.19.107.0/24 | RIPE | No ROA |
| 89.19.109.0/24 | RIPE | No ROA |
| 89.19.110.0/24 | RIPE | No ROA |
| 89.19.111.0/24 | RIPE | 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.