bgpreport

Network · data from 2026-11-12

AS26818 COL-PUB-SCHOOLS-OH - Columbus Public Schools

Registry name: COL-PUB-SCHOOLS-OH - Columbus Public Schools, US · not in PeeringDB

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

Announced routes

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

164.83.240.0/22 No ROA Nonecovered by 164.83.128.0/17 673 100% 67
164.83.1.0/24 No ROA Nonecovered by 164.83.0.0/17 671 100% 68
164.83.61.0/24 No ROA Nonecovered by 164.83.0.0/17 671 100% 68
164.83.62.0/24 No ROA Nonecovered by 164.83.0.0/17 671 100% 68
164.83.0.0/18 No ROA Nonecovered by 164.83.0.0/17 20 3%low visibility 18
164.83.64.0/23 No ROA Nonecovered by 164.83.0.0/17 20 3%low visibility 18
164.83.111.0/24 No ROA Nonecovered by 164.83.0.0/17 20 3%low visibility 18
164.83.112.0/22 No ROA Nonecovered by 164.83.0.0/17 20 3%low visibility 18
164.83.116.0/24 No ROA Nonecovered by 164.83.0.0/17 20 3%low visibility 18
164.83.122.0/24 No ROA Nonecovered by 164.83.0.0/17 20 3%low visibility 18
164.83.0.0/16 No ROA Other IRR onlyRADB 671 100% 69
164.83.0.0/17 No ROA Other IRR onlyRADB 671 100% 69

AS-SET

AS26818 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 27 are in fix.csv.

  • ROA: none12
  • Route object: none10
  • Route object: RIR2
  • Route object: not announced3
ChangePrefix or setDetailFull-table peers
ROA: none164.83.240.0/22No ROA covers it. Add a ROA for AS26818, maxLength 22.673 of 673
Route object: none164.83.240.0/22No route object for it. A route object for 164.83.128.0/17 with origin AS26818 covers it (filters allowing more-specifics accept it). Add a route object with origin AS26818 in the RIR database for the space.673 of 673
ROA: none164.83.1.0/24No ROA covers it. Add a ROA for AS26818, maxLength 24.671 of 673
Route object: none164.83.1.0/24No route object for it. A route object for 164.83.0.0/17 with origin AS26818 covers it (filters allowing more-specifics accept it). Add a route object with origin AS26818 in the RIR database for the space.671 of 673
ROA: none164.83.61.0/24No ROA covers it. Add a ROA for AS26818, maxLength 24.671 of 673
Route object: none164.83.61.0/24No route object for it. A route object for 164.83.0.0/17 with origin AS26818 covers it (filters allowing more-specifics accept it). Add a route object with origin AS26818 in the RIR database for the space.671 of 673
ROA: none164.83.62.0/24No ROA covers it. Add a ROA for AS26818, maxLength 24.671 of 673
Route object: none164.83.62.0/24No route object for it. A route object for 164.83.0.0/17 with origin AS26818 covers it (filters allowing more-specifics accept it). Add a route object with origin AS26818 in the RIR database for the space.671 of 673
ROA: none164.83.0.0/18No ROA covers it. Add a ROA for AS26818, maxLength 18.20 of 673
Route object: none164.83.0.0/18No route object for it. A route object for 164.83.0.0/17 with origin AS26818 covers it (filters allowing more-specifics accept it). Add a route object with origin AS26818 in the RIR database for the space.20 of 673
ROA: none164.83.64.0/23No ROA covers it. Add a ROA for AS26818, maxLength 23.20 of 673
Route object: none164.83.64.0/23No route object for it. A route object for 164.83.0.0/17 with origin AS26818 covers it (filters allowing more-specifics accept it). Add a route object with origin AS26818 in the RIR database for the space.20 of 673
ROA: none164.83.111.0/24No ROA covers it. Add a ROA for AS26818, maxLength 24.20 of 673
Route object: none164.83.111.0/24No route object for it. A route object for 164.83.0.0/17 with origin AS26818 covers it (filters allowing more-specifics accept it). Add a route object with origin AS26818 in the RIR database for the space.20 of 673
ROA: none164.83.112.0/22No ROA covers it. Add a ROA for AS26818, maxLength 22.20 of 673
Route object: none164.83.112.0/22No route object for it. A route object for 164.83.0.0/17 with origin AS26818 covers it (filters allowing more-specifics accept it). Add a route object with origin AS26818 in the RIR database for the space.20 of 673
ROA: none164.83.116.0/24No ROA covers it. Add a ROA for AS26818, maxLength 24.20 of 673
Route object: none164.83.116.0/24No route object for it. A route object for 164.83.0.0/17 with origin AS26818 covers it (filters allowing more-specifics accept it). Add a route object with origin AS26818 in the RIR database for the space.20 of 673
ROA: none164.83.122.0/24No ROA covers it. Add a ROA for AS26818, maxLength 24.20 of 673
Route object: none164.83.122.0/24No route object for it. A route object for 164.83.0.0/17 with origin AS26818 covers it (filters allowing more-specifics accept it). Add a route object with origin AS26818 in the RIR database for the space.20 of 673
ROA: none164.83.0.0/16No ROA covers it. Add a ROA for AS26818, maxLength 16.671 of 673
Route object: RIR164.83.0.0/16Route object only in RADB. Add it in the RIR database for the space.671 of 673
ROA: none164.83.0.0/17No ROA covers it. Add a ROA for AS26818, maxLength 17.671 of 673
Route object: RIR164.83.0.0/17Route object only in RADB. Add it in the RIR database for the space.671 of 673

Route objects not announced

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

164.83.128.0/17RADBNo ROA
167.83.128.0/17RADBNo ROA
192.5.222.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.