bgpreport

Network · data from 2026-11-12

AS204109 Hillenbrand Germany Holding

Registry name: Hillenbrand Hillenbrand Germany Holding GmbH, DE · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS204109, 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.

143.62.0.0/17 No ROA Other IRR onlyRADB 673 100% 66
143.62.64.0/20 No ROA RIR databaseARIN, RADB 673 100% 66
185.114.132.0/22 No ROA RIR databaseRADB, RIPE 673 100% 66
185.114.134.0/24 No ROA RIR databaseRADB, RIPE 673 100% 67
185.114.135.0/24 No ROA RIR databaseRADB, RIPE 673 100% 67
2a06:6f40::/29 No ROA RIR databaseRIPE 634 100% 69

AS-SET

PeeringDB's irr_as_set for AS204109: AS-HIGH. Expanded from the day's IRR dumps the way bgpq4 does against whois.radb.net: a name with a database is read from that database only, one without from the first database in RADB's order. "Not covered" = this network's own routes that a filter built from the set would leave out (AS204109 isn't in the set, or no route object for AS204109 covers the route; more-specifics of a route object are accepted down to /24 and /48, as with bgpq4 -A -R 24 / -R 48). Customers' routes aren't counted: the collectors show each route's origin, not which network it came through.

NameDatabaseASNsSets Route objectsAS204109 in itNot covered
AS-HIGH RIPE 2114 Yes 0

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 10 are in fix.csv.

  • ROA: none6
  • Route object: RIR1
  • Route object: not announced3
ChangePrefix or setDetailFull-table peers
ROA: none143.62.0.0/17No ROA covers it. Add a ROA for AS204109, maxLength 17.673 of 673
Route object: RIR143.62.0.0/17Route object only in RADB. Add it in the RIR database for the space.673 of 673
ROA: none143.62.64.0/20No ROA covers it. Add a ROA for AS204109, maxLength 20.673 of 673
ROA: none185.114.132.0/22No ROA covers it. Add a ROA for AS204109, maxLength 22.673 of 673
ROA: none185.114.134.0/24No ROA covers it. Add a ROA for AS204109, maxLength 24.673 of 673
ROA: none185.114.135.0/24No ROA covers it. Add a ROA for AS204109, maxLength 24.673 of 673
ROA: none2a06:6f40::/29No ROA covers it. Add a ROA for AS204109, maxLength 29.634 of 636

Route objects not announced

Route objects with origin AS204109 whose prefix no peer sees AS204109 announce. Many are kept on purpose (backup routes, space announced only in some places).

143.62.0.0/16ARIN, RADBNo ROA
199.182.75.0/24RIPE-NONAUTHNo ROA
2620:10d:4000::/40RADBNo 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.