Network · data from 2026-11-12
AS206589 NSIX Data Center
Registry name: NSIX-Data-Center NSIX Data Center sp. z o.o., PL · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS206589, 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.
| 185.182.99.28/32 | Invalid: maxLength | Nonecovered by 185.182.96.0/22 | 4 1%low visibility |
| 185.182.96.0/22 | Valid | RIR databaseRIPE | 671 100% |
| 2a0a:ea80::/29 | Valid | RIR databaseRIPE | 633 100% |
AS-SET
AS206589'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: maxLength1
- Route object: none1
- Route object: not announced2
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: maxLength | 185.182.99.28/32 | ROA 185.182.96.0/22 AS206589 has maxLength 22; the route is a /32. Raise the maxLength, or add a ROA for 185.182.99.28/32. |
| Route object: none | 185.182.99.28/32 | No route object for it. A route object for 185.182.96.0/22 with origin AS206589 covers it (too long for filters allowing more-specifics up to /24). Add a route object with origin AS206589 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS206589 whose prefix no peer sees AS206589 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 77.65.144.0/24 | RIPE | No ROA |
| 85.202.50.0/24 | RIPE | Valid |
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.