bgpreport

Network · data from 2026-11-12

AS23068 MEIJERNET - MEIJER

Registry name: MEIJERNET - MEIJER, US · not in PeeringDB

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

Announced routes

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

204.74.191.0/24 No ROA Nonecovered by 204.74.128.0/18 671 100% 68
204.74.192.0/23 No ROA Nonecovered by 204.74.192.0/21 671 100% 68
204.74.194.0/23 No ROA Nonecovered by 204.74.192.0/21 671 100% 68
204.74.196.0/22 No ROA Nonecovered by 204.74.192.0/21 663 99% 67
204.74.205.0/24 No ROA Nonecovered by 204.74.204.0/23 663 99% 67
204.74.128.0/18 No ROA Other IRR onlyRADB 663 99% 67
204.74.160.0/20 No ROA Other IRR onlyRADB 663 99% 67
204.74.176.0/21 No ROA Other IRR onlyRADB 663 99% 67
204.74.206.0/24 No ROA Other IRR onlyRADB 663 99% 67

AS-SET

AS23068 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 25 are in fix.csv.

  • ROA: none9
  • Route object: none5
  • Route object: RIR4
  • Route object: not announced7
ChangePrefix or setDetailFull-table peers
ROA: none204.74.191.0/24No ROA covers it. Add a ROA for AS23068, maxLength 24.671 of 673
Route object: none204.74.191.0/24No route object for it. A route object for 204.74.128.0/18 with origin AS23068 covers it (filters allowing more-specifics accept it). Add a route object with origin AS23068 in the RIR database for the space.671 of 673
ROA: none204.74.192.0/23No ROA covers it. Add a ROA for AS23068, maxLength 23.671 of 673
Route object: none204.74.192.0/23No route object for it. A route object for 204.74.192.0/21 with origin AS23068 covers it (filters allowing more-specifics accept it). Add a route object with origin AS23068 in the RIR database for the space.671 of 673
ROA: none204.74.194.0/23No ROA covers it. Add a ROA for AS23068, maxLength 23.671 of 673
Route object: none204.74.194.0/23No route object for it. A route object for 204.74.192.0/21 with origin AS23068 covers it (filters allowing more-specifics accept it). Add a route object with origin AS23068 in the RIR database for the space.671 of 673
ROA: none204.74.196.0/22No ROA covers it. Add a ROA for AS23068, maxLength 22.663 of 673
Route object: none204.74.196.0/22No route object for it. A route object for 204.74.192.0/21 with origin AS23068 covers it (filters allowing more-specifics accept it). Add a route object with origin AS23068 in the RIR database for the space.663 of 673
ROA: none204.74.205.0/24No ROA covers it. Add a ROA for AS23068, maxLength 24.663 of 673
Route object: none204.74.205.0/24No route object for it. A route object for 204.74.204.0/23 with origin AS23068 covers it (filters allowing more-specifics accept it). Add a route object with origin AS23068 in the RIR database for the space.663 of 673
ROA: none204.74.128.0/18No ROA covers it. Add a ROA for AS23068, maxLength 18.663 of 673
Route object: RIR204.74.128.0/18Route object only in RADB. Add it in the RIR database for the space.663 of 673
ROA: none204.74.160.0/20No ROA covers it. Add a ROA for AS23068, maxLength 20.663 of 673
Route object: RIR204.74.160.0/20Route object only in RADB. Add it in the RIR database for the space.663 of 673
ROA: none204.74.176.0/21No ROA covers it. Add a ROA for AS23068, maxLength 21.663 of 673
Route object: RIR204.74.176.0/21Route object only in RADB. Add it in the RIR database for the space.663 of 673
ROA: none204.74.206.0/24No ROA covers it. Add a ROA for AS23068, maxLength 24.663 of 673
Route object: RIR204.74.206.0/24Route object only in RADB. Add it in the RIR database for the space.663 of 673

Route objects not announced

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

204.74.128.0/19RADBNo ROA
204.74.184.0/22RADBNo ROA
204.74.188.0/23RADBNo ROA
204.74.190.0/24RADBNo ROA
204.74.192.0/21RADBNo ROA
204.74.200.0/22RADBNo ROA
204.74.204.0/23RADBNo 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.