Network · data from 2026-11-12

AS22935 Wayne Finger-Lakes BOCES

Registry name: WAYNE-BOCES - Wayne Finger-Lakes BOCES, US · PeeringDB

4IPv4 routes 0.0% RPKI valid · 75.0% with a route object

0IPv6 routes

0RPKI invalid 0 origin · 0 maxLength

4No ROA 1 with no route object for this origin

0Low visibility seen by under 10% of full-table peers

0Route objects not announced registered with origin AS22935, seen from no peer

Announced routes

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


209.68.86.0/24	No ROA	Nonecovered by 209.68.64.0/19	671 100%	67
209.68.96.0/19	No ROA	Other IRR onlyRADB	671 100%	68
209.68.64.0/18	No ROA	Other IRR onlyALTDB, RADB	670 100%	68
209.68.64.0/19	No ROA	Other IRR onlyRADB	670 100%	68

AS-SET

AS22935'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 8 are in fix.csv.

ROA: none4
Route object: none1
Route object: RIR3

Change	Prefix or set	Detail	Full-table peers
ROA: none	209.68.86.0/24	No ROA covers it. Add a ROA for AS22935, maxLength 24.	671 of 673
Route object: none	209.68.86.0/24	No route object for it. A route object for 209.68.64.0/19 with origin AS22935 covers it (filters allowing more-specifics accept it). Add a route object with origin AS22935 in the RIR database for the space.	671 of 673
ROA: none	209.68.96.0/19	No ROA covers it. Add a ROA for AS22935, maxLength 19.	671 of 673
Route object: RIR	209.68.96.0/19	Route object only in RADB. Add it in the RIR database for the space.	671 of 673
ROA: none	209.68.64.0/18	No ROA covers it. Add a ROA for AS22935, maxLength 18.	670 of 673
Route object: RIR	209.68.64.0/18	Route object only in ALTDB, RADB. Add it in the RIR database for the space.	670 of 673
ROA: none	209.68.64.0/19	No ROA covers it. Add a ROA for AS22935, maxLength 19.	670 of 673
Route object: RIR	209.68.64.0/19	Route object only in RADB. Add it in the RIR database for the space.	670 of 673

Change

Prefix or set

Detail

Full-table peers

ROA: none

209.68.86.0/24

No ROA covers it. Add a ROA for AS22935, maxLength 24.

671 of 673

Route object: none

209.68.86.0/24

No route object for it. A route object for 209.68.64.0/19 with origin AS22935 covers it (filters allowing more-specifics accept it). Add a route object with origin AS22935 in the RIR database for the space.

671 of 673

ROA: none

209.68.96.0/19

No ROA covers it. Add a ROA for AS22935, maxLength 19.

671 of 673

Route object: RIR

209.68.96.0/19

Route object only in RADB. Add it in the RIR database for the space.

671 of 673

ROA: none

209.68.64.0/18

No ROA covers it. Add a ROA for AS22935, maxLength 18.

670 of 673

Route object: RIR

209.68.64.0/18

Route object only in ALTDB, RADB. Add it in the RIR database for the space.

670 of 673

ROA: none

209.68.64.0/19

No ROA covers it. Add a ROA for AS22935, maxLength 19.

670 of 673

Route object: RIR

209.68.64.0/19

Route object only in RADB. Add it in the RIR database for the space.

670 of 673

Route objects not announced

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