bgpreport

Network · data from 2026-11-12

AS46621 SCRIC - Broome - Tioga BOCES

Registry name: SCRIC - Broome - Tioga BOCES, US · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS46621, 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.
216.162.16.0/21 Valid Nonecovered by 216.162.16.0/20 673 100% 70
216.162.24.0/21 Valid Nonecovered by 216.162.16.0/20 673 100% 70
216.162.16.0/22 Valid Nonecovered by 216.162.16.0/20 40 6%low visibility 28
216.162.20.0/22 Valid Nonecovered by 216.162.16.0/20 40 6%low visibility 28
216.162.24.0/22 Valid Nonecovered by 216.162.16.0/20 40 6%low visibility 28
216.162.28.0/22 Valid Nonecovered by 216.162.16.0/20 40 6%low visibility 28
216.162.16.0/20 Valid RIR databaseARIN, RADB 671 100% 68

AS-SET

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

  • Route object: none6
ChangePrefix or setDetailFull-table peers
Route object: none216.162.16.0/21No route object for it. A route object for 216.162.16.0/20 with origin AS46621 covers it (filters allowing more-specifics accept it). Add a route object with origin AS46621 in the RIR database for the space.673 of 673
Route object: none216.162.24.0/21No route object for it. A route object for 216.162.16.0/20 with origin AS46621 covers it (filters allowing more-specifics accept it). Add a route object with origin AS46621 in the RIR database for the space.673 of 673
Route object: none216.162.16.0/22No route object for it. A route object for 216.162.16.0/20 with origin AS46621 covers it (filters allowing more-specifics accept it). Add a route object with origin AS46621 in the RIR database for the space.40 of 673
Route object: none216.162.20.0/22No route object for it. A route object for 216.162.16.0/20 with origin AS46621 covers it (filters allowing more-specifics accept it). Add a route object with origin AS46621 in the RIR database for the space.40 of 673
Route object: none216.162.24.0/22No route object for it. A route object for 216.162.16.0/20 with origin AS46621 covers it (filters allowing more-specifics accept it). Add a route object with origin AS46621 in the RIR database for the space.40 of 673
Route object: none216.162.28.0/22No route object for it. A route object for 216.162.16.0/20 with origin AS46621 covers it (filters allowing more-specifics accept it). Add a route object with origin AS46621 in the RIR database for the space.40 of 673

Route objects not announced

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