bgpreport

Network · data from 2026-11-12

AS208988 Buchholz Digital

Registry name: Buchholz-Digital Buchholz Digital GmbH, DE · PeeringDB

16IPv4 routes 100.0% RPKI valid · 100.0% with a route object
1IPv6 routes 100.0% RPKI valid · 100.0% with a route object
0RPKI invalid 0 origin · 0 maxLength
0No ROA 0 with no route object for this origin
0Low visibility seen by under 10% of full-table peers
0Route objects not announced registered with origin AS208988, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS208988, 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.
31.214.150.0/23 Valid RIR databaseRIPE 673 100% 66
37.10.68.0/23 Valid RIR databaseRIPE 673 100% 66
37.10.110.0/23 Valid RIR databaseRIPE 673 100% 66
62.221.228.0/22 Valid RIR databaseRIPE 673 100% 66
85.190.184.0/21 Valid RIR databaseRIPE 673 100% 66
85.222.208.0/20 Valid RIR databaseRIPE 673 100% 66
91.208.17.0/24 Valid RIR databaseRIPE 673 100% 66
94.126.36.0/22 Valid RIR databaseRIPE 673 100% 66
109.169.120.0/21 Valid RIR databaseRIPE 673 100% 66
185.44.4.0/22 Valid RIR databaseRIPE 673 100% 66
185.50.108.0/22 Valid RIR databaseRIPE 673 100% 66
185.68.240.0/22 Valid RIR databaseRIPE 673 100% 66
185.123.4.0/22 Valid RIR databaseRIPE 673 100% 66
185.125.232.0/22 Valid RIR databaseRIPE 673 100% 66
185.195.120.0/22 Valid RIR databaseRIPE 673 100% 66
128.0.120.0/23 Valid RIR databaseRIPE 672 100% 66
2a01:71a0::/32 Valid RIR databaseRIPE 635 100% 67

AS-SET

AS208988's PeeringDB record names no AS-SET.

Fix list

Nothing to change: every route is RPKI valid with a route object in an RIR database, and every route object is announced.

Route objects not announced

Every route object with origin AS208988 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.