bgpreport

Network · data from 2026-11-12

AS22944 KCTCS-INTERNET2 - Kentucky Community and Technical College System

Registry name: KCTCS-INTERNET2 - Kentucky Community and Technical College System, US · not in PeeringDB

3IPv4 routes 66.7% RPKI valid · 33.3% with a route object
0IPv6 routes
0RPKI invalid 0 origin · 0 maxLength
1No ROA 2 with no route object for this origin
0Low visibility seen by under 10% of full-table peers
45Route objects not announced registered with origin AS22944, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS22944, 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.69.0.0/18 No ROA Other IRR onlyRADB 671 100% 68
67.140.186.0/24 Valid None 670 100% 67
67.140.189.0/24 Valid None 670 100% 67

AS-SET

AS22944 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 49 are in fix.csv.

  • ROA: none1
  • Route object: none2
  • Route object: RIR1
  • Route object: not announced45
ChangePrefix or setDetailFull-table peers
ROA: none216.69.0.0/18No ROA covers it. Add a ROA for AS22944, maxLength 18.671 of 673
Route object: RIR216.69.0.0/18Route object only in RADB. Add it in the RIR database for the space.671 of 673
Route object: none67.140.186.0/24No route object for it. Add a route object with origin AS22944 in the RIR database for the space.670 of 673
Route object: none67.140.189.0/24No route object for it. Add a route object with origin AS22944 in the RIR database for the space.670 of 673

Route objects not announced

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

2404:f4c0:10e8::/45APNICValid
2404:f4c0:10e8::/46APNICValid
2404:f4c0:10e8::/47APNICValid
2404:f4c0:10e9::/48APNICValid
2404:f4c0:10ea::/47APNICValid
2404:f4c0:10ea::/48APNICValid
2404:f4c0:10eb::/48APNICValid
2404:f4c0:10ec::/46APNICValid
2404:f4c0:10ec::/47APNICValid
2404:f4c0:10ec::/48APNICValid
2404:f4c0:10ed::/48APNICValid
2404:f4c0:10ee::/47APNICValid
2404:f4c0:10ee::/48APNICValid
2404:f4c0:10ef::/48APNICValid
2404:f4c0:10f0::/44APNICValid
2404:f4c0:10f0::/45APNICValid
2404:f4c0:10f0::/46APNICValid
2404:f4c0:10f0::/47APNICValid
2404:f4c0:10f0::/48APNICValid
2404:f4c0:10f1::/48APNICValid
2404:f4c0:10f2::/47APNICValid
2404:f4c0:10f2::/48APNICValid
2404:f4c0:10f3::/48APNICValid
2404:f4c0:10f4::/46APNICValid
2404:f4c0:10f4::/47APNICValid
2404:f4c0:10f4::/48APNICValid
2404:f4c0:10f5::/48APNICValid
2404:f4c0:10f6::/47APNICValid
2404:f4c0:10f6::/48APNICValid
2404:f4c0:10f7::/48APNICValid
2404:f4c0:10f8::/45APNICValid
2404:f4c0:10f8::/46APNICValid
2404:f4c0:10f8::/47APNICValid
2404:f4c0:10f8::/48APNICValid
2404:f4c0:10f9::/48APNICValid
2404:f4c0:10fa::/47APNICValid
2404:f4c0:10fa::/48APNICValid
2404:f4c0:10fb::/48APNICValid
2404:f4c0:10fc::/46APNICValid
2404:f4c0:10fc::/47APNICValid
2404:f4c0:10fc::/48APNICValid
2404:f4c0:10fd::/48APNICValid
2404:f4c0:10fe::/47APNICValid
2404:f4c0:10fe::/48APNICValid
2404:f4c0:10ff::/48APNICValid

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.