bgpreport

Network · data from 2026-11-12

AS328847 THE KONZA TECHNOPOLIS DEVELOPMENT AUTHORITY - THE KONZA TECHNOPOLIS DEVELOPMENT AUTHORITY

Registry name: THE KONZA TECHNOPOLIS DEVELOPMENT AUTHORITY - THE KONZA TECHNOPOLIS DEVELOPMENT AUTHORITY, KE · not in PeeringDB

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

Announced routes

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

102.210.148.0/24 No ROA Other IRR onlyRADB 672 100% 69
102.210.149.0/24 No ROA Other IRR onlyRADB 672 100% 69
102.210.150.0/24 No ROA Other IRR onlyRADB 672 100% 69
102.210.151.0/24 No ROA Other IRR onlyRADB 672 100% 69
102.220.23.0/24 No ROA Other IRR onlyRADB 672 100% 69
102.220.22.0/24 No ROA Other IRR onlyRADB 671 100% 69

AS-SET

AS328847 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: none6
  • Route object: RIR6
  • Route object: not announced3
ChangePrefix or setDetailFull-table peers
ROA: none102.210.148.0/24No ROA covers it. Add a ROA for AS328847, maxLength 24.672 of 673
Route object: RIR102.210.148.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
ROA: none102.210.149.0/24No ROA covers it. Add a ROA for AS328847, maxLength 24.672 of 673
Route object: RIR102.210.149.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
ROA: none102.210.150.0/24No ROA covers it. Add a ROA for AS328847, maxLength 24.672 of 673
Route object: RIR102.210.150.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
ROA: none102.210.151.0/24No ROA covers it. Add a ROA for AS328847, maxLength 24.672 of 673
Route object: RIR102.210.151.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
ROA: none102.220.23.0/24No ROA covers it. Add a ROA for AS328847, maxLength 24.672 of 673
Route object: RIR102.220.23.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
ROA: none102.220.22.0/24No ROA covers it. Add a ROA for AS328847, maxLength 24.671 of 673
Route object: RIR102.220.22.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673

Route objects not announced

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

102.210.148.0/22AFRINIC, RADBNo ROA
102.220.22.0/23AFRINIC, RADBNo ROA
2c0f:1e00::/32AFRINIC, RADBNo 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.