bgpreport

Network · data from 2026-11-12

AS47340 Roche Diagnostics GmbH

Registry name: ROCHE-AS Roche Diagnostics GmbH, DE · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS47340, 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.
2a04:c440:2a00::/40 No ROA RIR databaseRIPE 635 100% 68

AS-SET

AS47340'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 3 are in fix.csv.

  • ROA: none1
  • Route object: not announced2
ChangePrefix or setDetailFull-table peers
ROA: none2a04:c440:2a00::/40No ROA covers it. Add a ROA for AS47340, maxLength 40.635 of 636

Route objects not announced

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

194.120.84.0/23RIPENo ROA
194.120.88.0/24RIPENo 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.