Network · data from 2026-11-12
AS216067 BHS Solutions GmbH
Registry name: AS216067 BHS Solutions GmbH, DE · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS216067, 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.
| 176.116.4.0/24 | No ROA | None | 673 100% |
| 217.114.35.0/24 | No ROA | None | 672 100% |
| 104.167.26.0/23 | Valid | RIR databaseRIPE | 1 0%low visibility |
| 185.188.16.0/24 | Valid | RIR databaseRIPE | 1 0%low visibility |
AS-SET
AS216067'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 8 are in fix.csv.
- ROA: none2
- Route object: none2
- Route object: not announced4
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 176.116.4.0/24 | No ROA covers it. Add a ROA for AS216067, maxLength 24. |
| Route object: none | 176.116.4.0/24 | No route object for it. Add a route object with origin AS216067 in the RIR database for the space. |
| ROA: none | 217.114.35.0/24 | No ROA covers it. Add a ROA for AS216067, maxLength 24. |
| Route object: none | 217.114.35.0/24 | No route object for it. Add a route object with origin AS216067 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS216067 whose prefix no peer sees AS216067 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 74.122.24.0/24 | RIPE | Valid |
| 104.167.17.0/24 | RIPE | Valid |
| 185.77.23.0/24 | RIPE | Valid |
| 2a14:3600::/29 | RIPE | No ROA |
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.