Network · data from 2026-11-12
AS211689 BLUENET HMZ RADIOKOMUNIKACIE, spol. s r.o.
Registry name: BLUENET HMZ RADIOKOMUNIKACIE, spol. s r.o., SK · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS211689, 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.
| 158.255.16.0/24 | No ROA | Nonecovered by 158.255.16.0/21 | 671 100% |
| 158.255.17.0/24 | No ROA | Nonecovered by 158.255.16.0/21 | 671 100% |
| 158.255.18.0/24 | No ROA | Nonecovered by 158.255.16.0/21 | 671 100% |
| 158.255.19.0/24 | No ROA | Nonecovered by 158.255.16.0/21 | 671 100% |
| 158.255.20.0/22 | No ROA | Nonecovered by 158.255.16.0/21 | 671 100% |
| 158.255.24.0/21 | No ROA | RIR databaseRIPE | 671 100% |
| 185.222.208.0/24 | No ROA | RIR databaseRIPE | 671 100% |
AS-SET
AS211689 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 14 are in fix.csv.
- ROA: none7
- Route object: none5
- Route object: not announced2
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 158.255.16.0/24 | No ROA covers it. Add a ROA for AS211689, maxLength 24. |
| Route object: none | 158.255.16.0/24 | No route object for it. A route object for 158.255.16.0/21 with origin AS211689 covers it (filters allowing more-specifics accept it). Add a route object with origin AS211689 in the RIR database for the space. |
| ROA: none | 158.255.17.0/24 | No ROA covers it. Add a ROA for AS211689, maxLength 24. |
| Route object: none | 158.255.17.0/24 | No route object for it. A route object for 158.255.16.0/21 with origin AS211689 covers it (filters allowing more-specifics accept it). Add a route object with origin AS211689 in the RIR database for the space. |
| ROA: none | 158.255.18.0/24 | No ROA covers it. Add a ROA for AS211689, maxLength 24. |
| Route object: none | 158.255.18.0/24 | No route object for it. A route object for 158.255.16.0/21 with origin AS211689 covers it (filters allowing more-specifics accept it). Add a route object with origin AS211689 in the RIR database for the space. |
| ROA: none | 158.255.19.0/24 | No ROA covers it. Add a ROA for AS211689, maxLength 24. |
| Route object: none | 158.255.19.0/24 | No route object for it. A route object for 158.255.16.0/21 with origin AS211689 covers it (filters allowing more-specifics accept it). Add a route object with origin AS211689 in the RIR database for the space. |
| ROA: none | 158.255.20.0/22 | No ROA covers it. Add a ROA for AS211689, maxLength 22. |
| Route object: none | 158.255.20.0/22 | No route object for it. A route object for 158.255.16.0/21 with origin AS211689 covers it (filters allowing more-specifics accept it). Add a route object with origin AS211689 in the RIR database for the space. |
| ROA: none | 158.255.24.0/21 | No ROA covers it. Add a ROA for AS211689, maxLength 21. |
| ROA: none | 185.222.208.0/24 | No ROA covers it. Add a ROA for AS211689, maxLength 24. |
Route objects not announced
Route objects with origin AS211689 whose prefix no peer sees AS211689 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 158.255.16.0/21 | RIPE | No ROA |
| 2a0c:1300::/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.