bgpreport

Network · data from 2026-11-12

AS209871 Infomedics Infomedics BV

Registry name: Infomedics Infomedics BV, NL · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS209871, 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.252.124.0/23 No ROA Nonecovered by 84.252.124.0/22 672 100% 67
84.252.126.0/23 No ROA Nonecovered by 84.252.124.0/22 672 100% 66
84.252.126.0/24 No ROA Nonecovered by 84.252.124.0/22 672 100% 66
84.252.127.0/24 No ROA Nonecovered by 84.252.124.0/22 672 100% 66
84.252.125.0/24 No ROA Nonecovered by 84.252.124.0/22 671 100% 67
2a09:6d00::/30 No ROA Nonecovered by 2a09:6d00::/29 634 100% 67
2a09:6d02::/31 No ROA Nonecovered by 2a09:6d00::/29 634 100% 67
2a09:6d04::/30 No ROA Nonecovered by 2a09:6d00::/29 633 100% 67
2a09:6d04::/31 No ROA Nonecovered by 2a09:6d00::/29 633 100% 67
2a09:6d06::/31 No ROA Nonecovered by 2a09:6d00::/29 633 100% 67
84.252.124.0/22 No ROA RIR databaseRIPE 673 100% 67
2a09:6d00::/29 No ROA RIR databaseRIPE 633 100% 67

AS-SET

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

  • ROA: none12
  • Route object: none10
ChangePrefix or setDetailFull-table peers
ROA: none84.252.124.0/23No ROA covers it. Add a ROA for AS209871, maxLength 23.672 of 673
Route object: none84.252.124.0/23No route object for it. A route object for 84.252.124.0/22 with origin AS209871 covers it (filters allowing more-specifics accept it). Add a route object with origin AS209871 in the RIR database for the space.672 of 673
ROA: none84.252.126.0/23No ROA covers it. Add a ROA for AS209871, maxLength 23.672 of 673
Route object: none84.252.126.0/23No route object for it. A route object for 84.252.124.0/22 with origin AS209871 covers it (filters allowing more-specifics accept it). Add a route object with origin AS209871 in the RIR database for the space.672 of 673
ROA: none84.252.126.0/24No ROA covers it. Add a ROA for AS209871, maxLength 24.672 of 673
Route object: none84.252.126.0/24No route object for it. A route object for 84.252.124.0/22 with origin AS209871 covers it (filters allowing more-specifics accept it). Add a route object with origin AS209871 in the RIR database for the space.672 of 673
ROA: none84.252.127.0/24No ROA covers it. Add a ROA for AS209871, maxLength 24.672 of 673
Route object: none84.252.127.0/24No route object for it. A route object for 84.252.124.0/22 with origin AS209871 covers it (filters allowing more-specifics accept it). Add a route object with origin AS209871 in the RIR database for the space.672 of 673
ROA: none84.252.125.0/24No ROA covers it. Add a ROA for AS209871, maxLength 24.671 of 673
Route object: none84.252.125.0/24No route object for it. A route object for 84.252.124.0/22 with origin AS209871 covers it (filters allowing more-specifics accept it). Add a route object with origin AS209871 in the RIR database for the space.671 of 673
ROA: none2a09:6d00::/30No ROA covers it. Add a ROA for AS209871, maxLength 30.634 of 636
Route object: none2a09:6d00::/30No route object for it. A route object for 2a09:6d00::/29 with origin AS209871 covers it (filters allowing more-specifics accept it). Add a route object with origin AS209871 in the RIR database for the space.634 of 636
ROA: none2a09:6d02::/31No ROA covers it. Add a ROA for AS209871, maxLength 31.634 of 636
Route object: none2a09:6d02::/31No route object for it. A route object for 2a09:6d00::/29 with origin AS209871 covers it (filters allowing more-specifics accept it). Add a route object with origin AS209871 in the RIR database for the space.634 of 636
ROA: none2a09:6d04::/30No ROA covers it. Add a ROA for AS209871, maxLength 30.633 of 636
Route object: none2a09:6d04::/30No route object for it. A route object for 2a09:6d00::/29 with origin AS209871 covers it (filters allowing more-specifics accept it). Add a route object with origin AS209871 in the RIR database for the space.633 of 636
ROA: none2a09:6d04::/31No ROA covers it. Add a ROA for AS209871, maxLength 31.633 of 636
Route object: none2a09:6d04::/31No route object for it. A route object for 2a09:6d00::/29 with origin AS209871 covers it (filters allowing more-specifics accept it). Add a route object with origin AS209871 in the RIR database for the space.633 of 636
ROA: none2a09:6d06::/31No ROA covers it. Add a ROA for AS209871, maxLength 31.633 of 636
Route object: none2a09:6d06::/31No route object for it. A route object for 2a09:6d00::/29 with origin AS209871 covers it (filters allowing more-specifics accept it). Add a route object with origin AS209871 in the RIR database for the space.633 of 636
ROA: none84.252.124.0/22No ROA covers it. Add a ROA for AS209871, maxLength 22.673 of 673
ROA: none2a09:6d00::/29No ROA covers it. Add a ROA for AS209871, maxLength 29.633 of 636

Route objects not announced

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