Network · data from 2026-11-12
AS204690 olimsk PLAYMAX s.r.o.
Registry name: olimsk PLAYMAX s.r.o., SK · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS204690, 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.
| 2a0c:e186::/32 | No ROA | Nonecovered by 2a0c:e186::/31 | 635 100% |
| 2a0c:e186:c000::/34 | No ROA | Nonecovered by 2a0c:e186::/31 | 635 100% |
| 185.242.188.0/24 | No ROA | RIR databaseRIPE | 671 100% |
| 2a0c:e186::/31 | No ROA | RIR databaseRIPE | 634 100% |
AS-SET
AS204690 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 6 are in fix.csv.
- ROA: none4
- Route object: none2
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 2a0c:e186::/32 | No ROA covers it. Add a ROA for AS204690, maxLength 32. |
| Route object: none | 2a0c:e186::/32 | No route object for it. A route object for 2a0c:e186::/31 with origin AS204690 covers it (filters allowing more-specifics accept it). Add a route object with origin AS204690 in the RIR database for the space. |
| ROA: none | 2a0c:e186:c000::/34 | No ROA covers it. Add a ROA for AS204690, maxLength 34. |
| Route object: none | 2a0c:e186:c000::/34 | No route object for it. A route object for 2a0c:e186::/31 with origin AS204690 covers it (filters allowing more-specifics accept it). Add a route object with origin AS204690 in the RIR database for the space. |
| ROA: none | 185.242.188.0/24 | No ROA covers it. Add a ROA for AS204690, maxLength 24. |
| ROA: none | 2a0c:e186::/31 | No ROA covers it. Add a ROA for AS204690, maxLength 31. |
Route objects not announced
Every route object with origin AS204690 is announced.
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.