bgpreport

Network · data from 2026-11-12

AS25640 HAWAII-DEPT-OF-EDUC - Hawaii Department of Education

Registry name: HAWAII-DEPT-OF-EDUC - Hawaii Department of Education, US · not in PeeringDB

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

Announced routes

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

165.248.128.0/24 No ROA Nonecovered by 165.248.0.0/16 673 100% 68
165.248.194.0/24 No ROA Nonecovered by 165.248.0.0/16 673 100% 68
165.248.195.0/24 No ROA Nonecovered by 165.248.0.0/16 673 100% 68
165.248.249.0/24 No ROA Nonecovered by 165.248.0.0/16 673 100% 68
165.248.0.0/16 No ROA Other IRR onlyALTDB, RADB 671 100% 68

AS-SET

AS25640 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 12 are in fix.csv.

  • ROA: none5
  • Route object: none4
  • Route object: RIR1
  • Route object: not announced2
ChangePrefix or setDetailFull-table peers
ROA: none165.248.128.0/24No ROA covers it. Add a ROA for AS25640, maxLength 24.673 of 673
Route object: none165.248.128.0/24No route object for it. A route object for 165.248.0.0/16 with origin AS25640 covers it (filters allowing more-specifics accept it). Add a route object with origin AS25640 in the RIR database for the space.673 of 673
ROA: none165.248.194.0/24No ROA covers it. Add a ROA for AS25640, maxLength 24.673 of 673
Route object: none165.248.194.0/24No route object for it. A route object for 165.248.0.0/16 with origin AS25640 covers it (filters allowing more-specifics accept it). Add a route object with origin AS25640 in the RIR database for the space.673 of 673
ROA: none165.248.195.0/24No ROA covers it. Add a ROA for AS25640, maxLength 24.673 of 673
Route object: none165.248.195.0/24No route object for it. A route object for 165.248.0.0/16 with origin AS25640 covers it (filters allowing more-specifics accept it). Add a route object with origin AS25640 in the RIR database for the space.673 of 673
ROA: none165.248.249.0/24No ROA covers it. Add a ROA for AS25640, maxLength 24.673 of 673
Route object: none165.248.249.0/24No route object for it. A route object for 165.248.0.0/16 with origin AS25640 covers it (filters allowing more-specifics accept it). Add a route object with origin AS25640 in the RIR database for the space.673 of 673
ROA: none165.248.0.0/16No ROA covers it. Add a ROA for AS25640, maxLength 16.671 of 673
Route object: RIR165.248.0.0/16Route object only in ALTDB, RADB. Add it in the RIR database for the space.671 of 673

Route objects not announced

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

66.27.46.0/24RADBValid
66.27.47.0/24RADBValid

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.