bgpreport

Network · data from 2026-11-12

AS32360 MONROE-1-BOCES - Monroe #1 BOCES

Registry name: MONROE-1-BOCES - Monroe #1 BOCES, US · not in PeeringDB

6IPv4 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
7No ROA 0 with no route object for this origin
3Low visibility seen by under 10% of full-table peers
1Route objects not announced registered with origin AS32360, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS32360, 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.226.96.0/19 No ROA Other IRR onlyRADB 673 100% 68
198.180.129.0/24 No ROA Other IRR onlyRADB 671 100% 68
199.190.222.0/23 No ROA Other IRR onlyRADB 671 100% 68
199.190.224.0/23 No ROA Other IRR onlyRADB 671 100% 68
216.226.104.0/23 No ROA Other IRR onlyRADB 20 3%low visibility 15
216.226.127.0/24 No ROA Other IRR onlyRADB 20 3%low visibility 15
2620:0:1a50::/48 No ROA Other IRR onlyRADB 17 3%low visibility 18

AS-SET

AS32360 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 15 are in fix.csv.

  • ROA: none7
  • Route object: RIR7
  • Route object: not announced1
ChangePrefix or setDetailFull-table peers
ROA: none216.226.96.0/19No ROA covers it. Add a ROA for AS32360, maxLength 19.673 of 673
Route object: RIR216.226.96.0/19Route object only in RADB. Add it in the RIR database for the space.673 of 673
ROA: none198.180.129.0/24No ROA covers it. Add a ROA for AS32360, maxLength 24.671 of 673
Route object: RIR198.180.129.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
ROA: none199.190.222.0/23No ROA covers it. Add a ROA for AS32360, maxLength 23.671 of 673
Route object: RIR199.190.222.0/23Route object only in RADB. Add it in the RIR database for the space.671 of 673
ROA: none199.190.224.0/23No ROA covers it. Add a ROA for AS32360, maxLength 23.671 of 673
Route object: RIR199.190.224.0/23Route object only in RADB. Add it in the RIR database for the space.671 of 673
ROA: none216.226.104.0/23No ROA covers it. Add a ROA for AS32360, maxLength 23.20 of 673
Route object: RIR216.226.104.0/23Route object only in RADB. Add it in the RIR database for the space.20 of 673
ROA: none216.226.127.0/24No ROA covers it. Add a ROA for AS32360, maxLength 24.20 of 673
Route object: RIR216.226.127.0/24Route object only in RADB. Add it in the RIR database for the space.20 of 673
ROA: none2620:0:1a50::/48No ROA covers it. Add a ROA for AS32360, maxLength 48.17 of 636
Route object: RIR2620:0:1a50::/48Route object only in RADB. Add it in the RIR database for the space.17 of 636

Route objects not announced

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

216.226.104.0/24RADBNo 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.