Network · data from 2026-11-12
AS59866 AKD AKD d.o.o.
Registry name: AKD AKD d.o.o., HR · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS59866, 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.68.132.0/24 | No ROA | RIR databaseRIPE | 671 100% |
| 185.68.134.0/23 | Valid | RIR databaseRIPE | 668 99% |
| 185.68.134.0/24 | Valid | RIR databaseRIPE | 668 99% |
| 185.68.135.0/24 | Valid | RIR databaseRIPE | 668 99% |
AS-SET
AS59866 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 6 are in fix.csv.
- ROA: none1
- Route object: not announced5
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 185.68.132.0/24 | No ROA covers it. Add a ROA for AS59866, maxLength 24. |
Route objects not announced
Route objects with origin AS59866 whose prefix no peer sees AS59866 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 185.68.132.0/22 | RIPE | No ROA |
| 185.68.132.0/23 | RIPE | No ROA |
| 185.68.133.0/24 | RIPE | No ROA |
| 2a05:1840::/29 | RIPE | Valid |
| 2a05:1844::/32 | 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.