bgpreport

Network · data from 2026-11-12

AS8692 BRZ Bundesrechenzentrum GmbH

Registry name: BRZ Bundesrechenzentrum GmbH, AT · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS8692, 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.
84.38.116.0/24 No ROA None 1 0%low visibility 1
84.38.122.0/24 No ROA None 1 0%low visibility 1
84.38.124.0/25 No ROA None 1 0%low visibility 1
85.158.224.0/21 No ROA RIR databaseRIPE 671 100% 69
95.131.192.0/21 No ROA RIR databaseRIPE 671 100% 69
193.46.188.0/23 No ROA RIR databaseRIPE 671 100% 69
194.37.104.0/21 No ROA RIR databaseRIPE 671 100% 69
2a00:4400::/32 No ROA RIR databaseRIPE 636 100% 70

AS-SET

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

  • ROA: none8
  • Route object: none3
  • Route object: not announced1
ChangePrefix or setDetailFull-table peers
ROA: none84.38.116.0/24No ROA covers it. Add a ROA for AS8692, maxLength 24.1 of 673
Route object: none84.38.116.0/24No route object for it. Add a route object with origin AS8692 in the RIR database for the space.1 of 673
ROA: none84.38.122.0/24No ROA covers it. Add a ROA for AS8692, maxLength 24.1 of 673
Route object: none84.38.122.0/24No route object for it. Add a route object with origin AS8692 in the RIR database for the space.1 of 673
ROA: none84.38.124.0/25No ROA covers it. Add a ROA for AS8692, maxLength 25.1 of 673
Route object: none84.38.124.0/25No route object for it. Add a route object with origin AS8692 in the RIR database for the space.1 of 673
ROA: none85.158.224.0/21No ROA covers it. Add a ROA for AS8692, maxLength 21.671 of 673
ROA: none95.131.192.0/21No ROA covers it. Add a ROA for AS8692, maxLength 21.671 of 673
ROA: none193.46.188.0/23No ROA covers it. Add a ROA for AS8692, maxLength 23.671 of 673
ROA: none194.37.104.0/21No ROA covers it. Add a ROA for AS8692, maxLength 21.671 of 673
ROA: none2a00:4400::/32No ROA covers it. Add a ROA for AS8692, maxLength 32.636 of 636

Route objects not announced

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

194.37.192.0/19RIPENo 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.