bgpreport

Network · data from 2026-11-12

AS206266 HanseMerkur Krankenversicherung AG

Registry name: HanseMerkur-AS HanseMerkur Krankenversicherung AG, 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
0Route objects not announced registered with origin AS206266, seen from no peer

Announced routes

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

185.190.192.0/22 No ROA RIR databaseRIPE 672 100% 67
185.190.192.0/24 No ROA RIR databaseRIPE 672 100% 67
185.190.194.0/24 No ROA RIR databaseRIPE 672 100% 67
185.190.195.0/24 No ROA RIR databaseRIPE 672 100% 67
185.190.193.0/24 No ROA RIR databaseRIPE 671 100% 67
2a0a:1840::/29 No ROA RIR databaseRIPE 627 99% 67

AS-SET

AS206266'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 6 are in fix.csv.

  • ROA: none6
ChangePrefix or setDetailFull-table peers
ROA: none185.190.192.0/22No ROA covers it. Add a ROA for AS206266, maxLength 22.672 of 673
ROA: none185.190.192.0/24No ROA covers it. Add a ROA for AS206266, maxLength 24.672 of 673
ROA: none185.190.194.0/24No ROA covers it. Add a ROA for AS206266, maxLength 24.672 of 673
ROA: none185.190.195.0/24No ROA covers it. Add a ROA for AS206266, maxLength 24.672 of 673
ROA: none185.190.193.0/24No ROA covers it. Add a ROA for AS206266, maxLength 24.671 of 673
ROA: none2a0a:1840::/29No ROA covers it. Add a ROA for AS206266, maxLength 29.627 of 636

Route objects not announced

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