Network · data from 2026-11-12
AS2115 OPEGIEKA-PL OPEGIEKA Sp. z o.o.
Registry name: OPEGIEKA-PL OPEGIEKA Sp. z o.o., PL · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS2115, 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.
| 91.241.5.0/24 | No ROA | Other origin only | 26 4%low visibility |
| 91.223.68.0/24 | No ROA | RIR databaseRIPE | 646 96% |
| 83.168.93.0/24 | No ROA | RIR databaseRIPE | 643 96% |
| 2001:67c:f78::/48 | No ROA | RIR databaseRIPE | 634 100% |
AS-SET
AS2115 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 5 are in fix.csv.
- ROA: none4
- Route object: none1
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 91.241.5.0/24 | No ROA covers it. Add a ROA for AS2115, maxLength 24. |
| Route object: none | 91.241.5.0/24 | Route objects for it name AS198999. Add a route object with origin AS2115 in the RIR database for the space. |
| ROA: none | 91.223.68.0/24 | No ROA covers it. Add a ROA for AS2115, maxLength 24. |
| ROA: none | 83.168.93.0/24 | No ROA covers it. Add a ROA for AS2115, maxLength 24. |
| ROA: none | 2001:67c:f78::/48 | No ROA covers it. Add a ROA for AS2115, maxLength 48. |
Route objects not announced
Every route object with origin AS2115 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.