Network · data from 2026-11-12
AS60966 NIKEM-NET Nikem Net Ltd.
Registry name: NIKEM-NET Nikem Net Ltd., BG · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS60966, 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.
| 78.90.198.65/32 | Invalid: maxLength | Nonecovered by 78.90.198.0/23 | 3 0%low visibility |
| 95.111.39.161/32 | Invalid: maxLength | Nonecovered by 95.111.39.0/24 | 3 0%low visibility |
| 95.111.39.163/32 | Invalid: maxLength | Nonecovered by 95.111.39.0/24 | 3 0%low visibility |
| 95.111.92.70/32 | Invalid: maxLength | Nonecovered by 95.111.92.0/24 | 3 0%low visibility |
| 95.111.92.76/32 | Invalid: maxLength | Nonecovered by 95.111.92.0/24 | 3 0%low visibility |
| 78.83.156.0/23 | Valid | RIR databaseRIPE | 673 100% |
| 78.83.158.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 78.90.198.0/23 | Valid | RIR databaseRIPE | 673 100% |
| 78.90.200.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 95.111.39.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 95.111.40.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 95.111.92.0/24 | Valid | RIR databaseRIPE | 673 100% |
AS-SET
AS60966 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 10 are in fix.csv.
- ROA: maxLength5
- Route object: none5
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: maxLength | 78.90.198.65/32 | ROA 78.90.198.0/23 AS60966 has maxLength 23; the route is a /32. Raise the maxLength, or add a ROA for 78.90.198.65/32. |
| Route object: none | 78.90.198.65/32 | No route object for it. A route object for 78.90.198.0/23 with origin AS60966 covers it (too long for filters allowing more-specifics up to /24). Add a route object with origin AS60966 in the RIR database for the space. |
| ROA: maxLength | 95.111.39.161/32 | ROA 95.111.39.0/24 AS60966 has maxLength 24; the route is a /32. Raise the maxLength, or add a ROA for 95.111.39.161/32. |
| Route object: none | 95.111.39.161/32 | No route object for it. A route object for 95.111.39.0/24 with origin AS60966 covers it (too long for filters allowing more-specifics up to /24). Add a route object with origin AS60966 in the RIR database for the space. |
| ROA: maxLength | 95.111.39.163/32 | ROA 95.111.39.0/24 AS60966 has maxLength 24; the route is a /32. Raise the maxLength, or add a ROA for 95.111.39.163/32. |
| Route object: none | 95.111.39.163/32 | No route object for it. A route object for 95.111.39.0/24 with origin AS60966 covers it (too long for filters allowing more-specifics up to /24). Add a route object with origin AS60966 in the RIR database for the space. |
| ROA: maxLength | 95.111.92.70/32 | ROA 95.111.92.0/24 AS60966 has maxLength 24; the route is a /32. Raise the maxLength, or add a ROA for 95.111.92.70/32. |
| Route object: none | 95.111.92.70/32 | No route object for it. A route object for 95.111.92.0/24 with origin AS60966 covers it (too long for filters allowing more-specifics up to /24). Add a route object with origin AS60966 in the RIR database for the space. |
| ROA: maxLength | 95.111.92.76/32 | ROA 95.111.92.0/24 AS60966 has maxLength 24; the route is a /32. Raise the maxLength, or add a ROA for 95.111.92.76/32. |
| Route object: none | 95.111.92.76/32 | No route object for it. A route object for 95.111.92.0/24 with origin AS60966 covers it (too long for filters allowing more-specifics up to /24). Add a route object with origin AS60966 in the RIR database for the space. |
Route objects not announced
Every route object with origin AS60966 is announced.
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.