Network · data from 2026-11-12
AS198023 Jessa
Registry name: yesNET-AS Grzegorz Jessa trading as "Jessa" Przedsiebiorstwo, PL · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS198023, 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.
| 178.239.0.0/20 | No ROA | RIR databaseRIPE | 671 100% |
| 178.239.10.0/23 | No ROA | RIR databaseRIPE | 671 100% |
| 178.239.12.0/23 | No ROA | RIR databaseRIPE | 671 100% |
| 178.239.14.0/23 | No ROA | RIR databaseRIPE | 671 100% |
| 185.60.184.0/22 | No ROA | RIR databaseRIPE | 671 100% |
AS-SET
AS198023's PeeringDB record names no 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 12 are in fix.csv.
- ROA: none5
- Route object: not announced7
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 178.239.0.0/20 | No ROA covers it. Add a ROA for AS198023, maxLength 20. |
| ROA: none | 178.239.10.0/23 | No ROA covers it. Add a ROA for AS198023, maxLength 23. |
| ROA: none | 178.239.12.0/23 | No ROA covers it. Add a ROA for AS198023, maxLength 23. |
| ROA: none | 178.239.14.0/23 | No ROA covers it. Add a ROA for AS198023, maxLength 23. |
| ROA: none | 185.60.184.0/22 | No ROA covers it. Add a ROA for AS198023, maxLength 22. |
Route objects not announced
Route objects with origin AS198023 whose prefix no peer sees AS198023 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 88.220.181.0/24 | RIPE | Valid |
| 178.239.0.0/21 | RIPE | No ROA |
| 178.239.1.0/24 | RIPE | No ROA |
| 178.239.8.0/21 | RIPE | No ROA |
| 178.239.8.0/23 | RIPE | No ROA |
| 178.239.12.0/22 | RIPE | No ROA |
| 2a04:e600::/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.