Network · data from 2026-11-12
AS44525 NIKONETCOM-AS Niko Net Com Ltd.
Registry name: NIKONETCOM-AS Niko Net Com Ltd., BG · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS44525, 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.146.144.0/22 | No ROA | RIR databaseRIPE | 673 100% |
| 185.146.144.0/24 | No ROA | RIR databaseRIPE | 673 100% |
| 185.146.145.0/24 | No ROA | RIR databaseRIPE | 673 100% |
| 185.146.146.0/24 | No ROA | RIR databaseRIPE | 673 100% |
| 185.146.147.0/24 | No ROA | RIR databaseRIPE | 673 100% |
AS-SET
AS44525 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 12 are in fix.csv.
- ROA: none5
- Route object: not announced7
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 185.146.144.0/22 | No ROA covers it. Add a ROA for AS44525, maxLength 22. |
| ROA: none | 185.146.144.0/24 | No ROA covers it. Add a ROA for AS44525, maxLength 24. |
| ROA: none | 185.146.145.0/24 | No ROA covers it. Add a ROA for AS44525, maxLength 24. |
| ROA: none | 185.146.146.0/24 | No ROA covers it. Add a ROA for AS44525, maxLength 24. |
| ROA: none | 185.146.147.0/24 | No ROA covers it. Add a ROA for AS44525, maxLength 24. |
Route objects not announced
Route objects with origin AS44525 whose prefix no peer sees AS44525 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 109.160.57.0/24 | RIPE | Valid |
| 109.160.58.0/24 | RIPE | Valid |
| 109.160.60.0/24 | RIPE | Valid |
| 109.160.61.0/24 | RIPE | Valid |
| 109.160.86.0/24 | RIPE | Valid |
| 212.45.68.0/22 | RIPE | Valid |
| 212.45.69.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.