Network · data from 2026-11-12
AS208962 Nextremum
Registry name: nextremum Nextremum s.r.o., CZ · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS208962, 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.
| 193.239.177.0/24 | No ROA | RIR databaseRIPE | 673 100% |
| 2a12:fe40::/29 | No ROA | RIR databaseRIPE | 632 99% |
| 38.22.38.0/23 | Valid | RIR databaseARIN | 673 100% |
| 38.74.72.0/23 | Valid | RIR databaseARIN | 673 100% |
| 38.127.214.0/23 | Valid | RIR databaseARIN | 673 100% |
| 154.51.15.0/24 | Valid | RIR databaseARIN, RADB | 673 100% |
| 38.117.87.0/24 | Valid | RIR databaseARIN, RADB | 672 100% |
AS-SET
AS208962'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 3 are in fix.csv.
- ROA: none2
- Route object: not announced1
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 193.239.177.0/24 | No ROA covers it. Add a ROA for AS208962, maxLength 24. |
| ROA: none | 2a12:fe40::/29 | No ROA covers it. Add a ROA for AS208962, maxLength 29. |
Route objects not announced
Route objects with origin AS208962 whose prefix no peer sees AS208962 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 194.190.215.0/24 | 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.