Network · data from 2026-11-12
AS59720 BOFIBER Bofiber AS
Registry name: BOFIBER Bofiber AS, NO · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS59720, 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.
| 2a02:cd00::/29 | No ROA | RIR databaseRIPE | 635 100% |
| 185.5.232.0/22 | Valid | RIR databaseRIPE | 673 100% |
| 213.166.184.0/23 | Valid | RIR databaseRIPE | 673 100% |
AS-SET
AS59720 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 7 are in fix.csv.
- ROA: none1
- Route object: not announced6
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 2a02:cd00::/29 | No ROA covers it. Add a ROA for AS59720, maxLength 29. |
Route objects not announced
Route objects with origin AS59720 whose prefix no peer sees AS59720 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 185.5.232.0/24 | RIPE | Valid |
| 185.5.233.0/24 | RIPE | Valid |
| 185.5.234.0/24 | RIPE | Valid |
| 185.5.235.0/24 | RIPE | Valid |
| 213.166.184.0/24 | RIPE | Invalid: maxLength |
| 213.166.185.0/24 | RIPE | Invalid: maxLength |
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.