Network · data from 2026-11-12
AS51420 CYRILEK-AS cyrilek.net z.s.
Registry name: CYRILEK-AS cyrilek.net z.s., CZ · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS51420, 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.
| 109.164.83.0/24 | Valid | Nonecovered by 109.164.80.0/20 | 673 100% |
| 109.164.89.0/24 | Valid | Nonecovered by 109.164.80.0/20 | 673 100% |
| 109.164.90.0/24 | Valid | Nonecovered by 109.164.80.0/20 | 673 100% |
| 109.164.95.0/24 | Valid | Nonecovered by 109.164.80.0/20 | 673 100% |
| 109.164.64.0/19 | Valid | RIR databaseRIPE | 673 100% |
| 109.164.64.0/20 | Valid | RIR databaseRIPE | 673 100% |
| 109.164.80.0/20 | Valid | RIR databaseRIPE | 673 100% |
| 109.164.84.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 109.164.85.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 109.164.87.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 109.164.88.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 109.164.91.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 109.164.92.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 109.164.93.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 109.164.94.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 109.164.96.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 109.164.97.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 109.164.96.0/23 | Valid | RIR databaseRIPE | 672 100% |
AS-SET
AS51420 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 8 are in fix.csv.
- Route object: none4
- Route object: not announced4
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: none | 109.164.83.0/24 | No route object for it. A route object for 109.164.80.0/20 with origin AS51420 covers it (filters allowing more-specifics accept it). Add a route object with origin AS51420 in the RIR database for the space. |
| Route object: none | 109.164.89.0/24 | No route object for it. A route object for 109.164.80.0/20 with origin AS51420 covers it (filters allowing more-specifics accept it). Add a route object with origin AS51420 in the RIR database for the space. |
| Route object: none | 109.164.90.0/24 | No route object for it. A route object for 109.164.80.0/20 with origin AS51420 covers it (filters allowing more-specifics accept it). Add a route object with origin AS51420 in the RIR database for the space. |
| Route object: none | 109.164.95.0/24 | No route object for it. A route object for 109.164.80.0/20 with origin AS51420 covers it (filters allowing more-specifics accept it). Add a route object with origin AS51420 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS51420 whose prefix no peer sees AS51420 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 185.48.7.0/24 | RIPE | No ROA |
| 2a03:3a05::/32 | RIPE | Invalid: origin |
| 2a03:3a06::/32 | RIPE | Invalid: origin |
| 2a14:1240::/29 | 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.