bgpreport

Network · data from 2026-11-12

AS13167 Merck-KGaA Merck KGaA

Registry name: Merck-KGaA Merck KGaA, DE · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS13167, 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.
85.238.140.0/24 No ROA Nonecovered by 85.238.140.0/22 671 100% 67
2001:4cf8:6000::/36 No ROA Nonecovered by 2001:4cf8::/32 636 100% 69
2001:4cf8:6000::/48 No ROA Nonecovered by 2001:4cf8::/32 635 100% 69
85.238.136.0/22 No ROA RIR databaseRIPE 673 100% 66
85.238.140.0/22 No ROA RIR databaseRIPE 673 100% 67
155.250.0.0/16 No ROA RIR databaseRIPE 673 100% 66
2001:4cf8::/32 No ROA RIR databaseRIPE 634 100% 68

AS-SET

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

  • ROA: none7
  • Route object: none3
  • Route object: not announced1
ChangePrefix or setDetailFull-table peers
ROA: none85.238.140.0/24No ROA covers it. Add a ROA for AS13167, maxLength 24.671 of 673
Route object: none85.238.140.0/24No route object for it. A route object for 85.238.140.0/22 with origin AS13167 covers it (filters allowing more-specifics accept it). Add a route object with origin AS13167 in the RIR database for the space.671 of 673
ROA: none2001:4cf8:6000::/36No ROA covers it. Add a ROA for AS13167, maxLength 36.636 of 636
Route object: none2001:4cf8:6000::/36No route object for it. A route object for 2001:4cf8::/32 with origin AS13167 covers it (filters allowing more-specifics accept it). Add a route object with origin AS13167 in the RIR database for the space.636 of 636
ROA: none2001:4cf8:6000::/48No ROA covers it. Add a ROA for AS13167, maxLength 48.635 of 636
Route object: none2001:4cf8:6000::/48No route object for it. A route object for 2001:4cf8::/32 with origin AS13167 covers it (filters allowing more-specifics accept it). Add a route object with origin AS13167 in the RIR database for the space.635 of 636
ROA: none85.238.136.0/22No ROA covers it. Add a ROA for AS13167, maxLength 22.673 of 673
ROA: none85.238.140.0/22No ROA covers it. Add a ROA for AS13167, maxLength 22.673 of 673
ROA: none155.250.0.0/16No ROA covers it. Add a ROA for AS13167, maxLength 16.673 of 673
ROA: none2001:4cf8::/32No ROA covers it. Add a ROA for AS13167, maxLength 32.634 of 636

Route objects not announced

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

85.238.132.0/22RIPENo 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.