bgpreport

Network · data from 2026-11-12

AS3714 Kentucky Educational Computing Network

Registry name: KEC-NET - Kentucky Educational Computing Network, US · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS3714, 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.
66.209.160.0/24 No ROA Nonecovered by 66.209.160.0/20 673 100% 67
216.249.138.0/24 No ROA Nonecovered by 216.249.136.0/22 673 100% 67
66.209.160.0/20 No ROA RIR databaseARIN 673 100% 67
199.120.154.0/24 No ROA RIR databaseARIN 673 100% 68
216.249.128.0/22 No ROA RIR databaseARIN 673 100% 68
216.249.136.0/22 No ROA RIR databaseARIN 673 100% 67
216.249.140.0/22 No ROA RIR databaseARIN 673 100% 68
2610:1e0::/32 No ROA RIR databaseARIN 606 95% 68
2610:1e0:1f00::/48 No ROA RIR databaseARIN 606 95% 68

AS-SET

AS3714'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 16 are in fix.csv.

  • ROA: none9
  • Route object: none2
  • Route object: not announced5
ChangePrefix or setDetailFull-table peers
ROA: none66.209.160.0/24No ROA covers it. Add a ROA for AS3714, maxLength 24.673 of 673
Route object: none66.209.160.0/24No route object for it. A route object for 66.209.160.0/20 with origin AS3714 covers it (filters allowing more-specifics accept it). Add a route object with origin AS3714 in the RIR database for the space.673 of 673
ROA: none216.249.138.0/24No ROA covers it. Add a ROA for AS3714, maxLength 24.673 of 673
Route object: none216.249.138.0/24No route object for it. A route object for 216.249.136.0/22 with origin AS3714 covers it (filters allowing more-specifics accept it). Add a route object with origin AS3714 in the RIR database for the space.673 of 673
ROA: none66.209.160.0/20No ROA covers it. Add a ROA for AS3714, maxLength 20.673 of 673
ROA: none199.120.154.0/24No ROA covers it. Add a ROA for AS3714, maxLength 24.673 of 673
ROA: none216.249.128.0/22No ROA covers it. Add a ROA for AS3714, maxLength 22.673 of 673
ROA: none216.249.136.0/22No ROA covers it. Add a ROA for AS3714, maxLength 22.673 of 673
ROA: none216.249.140.0/22No ROA covers it. Add a ROA for AS3714, maxLength 22.673 of 673
ROA: none2610:1e0::/32No ROA covers it. Add a ROA for AS3714, maxLength 32.606 of 636
ROA: none2610:1e0:1f00::/48No ROA covers it. Add a ROA for AS3714, maxLength 48.606 of 636

Route objects not announced

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

216.249.128.0/18ARINNo ROA
216.249.132.0/22ARINNo ROA
216.249.140.0/24ARINNo ROA
216.249.141.0/24ARINNo ROA
216.249.141.0/27ARINNo 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.