Network · data from 2026-11-12
AS198151 NCORE Sp. z o.o.
Registry name: NCORE-AS NETON Sp. z o.o., PL · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS198151, 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.
| 176.98.115.59/32 | No ROA | Nonecovered by 176.98.112.0/21 | 2 0%low visibility |
| 176.98.112.0/21 | No ROA | RIR databaseRIPE | 671 100% |
AS-SET
AS198151'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 4 are in fix.csv.
- ROA: none2
- Route object: none1
- Route object: not announced1
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 176.98.115.59/32 | No ROA covers it. Add a ROA for AS198151, maxLength 32. |
| Route object: none | 176.98.115.59/32 | No route object for it. A route object for 176.98.112.0/21 with origin AS198151 covers it (too long for filters allowing more-specifics up to /24). Add a route object with origin AS198151 in the RIR database for the space. |
| ROA: none | 176.98.112.0/21 | No ROA covers it. Add a ROA for AS198151, maxLength 21. |
Route objects not announced
Route objects with origin AS198151 whose prefix no peer sees AS198151 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 2a10:f781:10:869d::/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.