Network · data from 2026-11-12
AS198935 Cybernet_WMW-AS CYBERNET WMW Sp. z o.o.
Registry name: Cybernet_WMW-AS CYBERNET WMW Sp. z o.o., PL · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS198935, 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.
| 45.149.208.0/24 | No ROA | RIR databaseRIPE | 671 100% |
| 45.149.209.0/24 | No ROA | RIR databaseRIPE | 671 100% |
| 45.149.210.0/24 | No ROA | RIR databaseRIPE | 671 100% |
| 176.111.120.0/21 | No ROA | RIR databaseRIPE | 671 100% |
| 176.111.120.0/22 | No ROA | RIR databaseRIPE | 671 100% |
| 176.111.124.0/23 | No ROA | RIR databaseRIPE | 671 100% |
| 176.111.126.0/23 | No ROA | RIR databaseRIPE | 671 100% |
| 185.37.9.0/24 | No ROA | RIR databaseRIPE | 671 100% |
| 185.48.128.0/24 | No ROA | RIR databaseRIPE | 671 100% |
| 185.48.129.0/24 | No ROA | RIR databaseRIPE | 671 100% |
| 185.48.130.0/24 | No ROA | RIR databaseRIPE | 671 100% |
| 185.48.131.0/24 | No ROA | RIR databaseRIPE | 671 100% |
AS-SET
AS198935 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 15 are in fix.csv.
- ROA: none12
- Route object: not announced3
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 45.149.208.0/24 | No ROA covers it. Add a ROA for AS198935, maxLength 24. |
| ROA: none | 45.149.209.0/24 | No ROA covers it. Add a ROA for AS198935, maxLength 24. |
| ROA: none | 45.149.210.0/24 | No ROA covers it. Add a ROA for AS198935, maxLength 24. |
| ROA: none | 176.111.120.0/21 | No ROA covers it. Add a ROA for AS198935, maxLength 21. |
| ROA: none | 176.111.120.0/22 | No ROA covers it. Add a ROA for AS198935, maxLength 22. |
| ROA: none | 176.111.124.0/23 | No ROA covers it. Add a ROA for AS198935, maxLength 23. |
| ROA: none | 176.111.126.0/23 | No ROA covers it. Add a ROA for AS198935, maxLength 23. |
| ROA: none | 185.37.9.0/24 | No ROA covers it. Add a ROA for AS198935, maxLength 24. |
| ROA: none | 185.48.128.0/24 | No ROA covers it. Add a ROA for AS198935, maxLength 24. |
| ROA: none | 185.48.129.0/24 | No ROA covers it. Add a ROA for AS198935, maxLength 24. |
| ROA: none | 185.48.130.0/24 | No ROA covers it. Add a ROA for AS198935, maxLength 24. |
| ROA: none | 185.48.131.0/24 | No ROA covers it. Add a ROA for AS198935, maxLength 24. |
Route objects not announced
Route objects with origin AS198935 whose prefix no peer sees AS198935 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 45.149.208.0/22 | RIPE | No ROA |
| 45.149.211.0/24 | RIPE | No ROA |
| 2a10:f781:10:159a::/64 | 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.