bgpreport

Network · data from 2026-11-12

AS329475 KONNECT DATA NETWORKS LTD

Registry name: KONNECT DATA NETWORKS LTD - KONNECT DATA NETWORKS LTD, KE · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS329475, 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.201.8.0/22 No ROA None 672 100% 67
102.201.8.0/24 No ROA None 96 14% 37
102.201.9.0/24 No ROA None 96 14% 37
102.201.10.0/24 No ROA None 96 14% 37
102.201.11.0/24 No ROA None 96 14% 37
102.208.44.0/22 Valid RIR databaseAFRINIC 671 100% 68
102.208.44.0/24 Valid RIR databaseAFRINIC 96 14% 37
102.208.45.0/24 Valid RIR databaseAFRINIC 96 14% 37
102.208.46.0/24 Valid RIR databaseAFRINIC 96 14% 37
102.208.47.0/24 Valid RIR databaseAFRINIC 96 14% 37

AS-SET

AS329475'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 17 are in fix.csv.

  • ROA: none5
  • Route object: none5
  • Route object: not announced7
ChangePrefix or setDetailFull-table peers
ROA: none102.201.8.0/22No ROA covers it. Add a ROA for AS329475, maxLength 22.672 of 673
Route object: none102.201.8.0/22No route object for it. Add a route object with origin AS329475 in the RIR database for the space.672 of 673
ROA: none102.201.8.0/24No ROA covers it. Add a ROA for AS329475, maxLength 24.96 of 673
Route object: none102.201.8.0/24No route object for it. Add a route object with origin AS329475 in the RIR database for the space.96 of 673
ROA: none102.201.9.0/24No ROA covers it. Add a ROA for AS329475, maxLength 24.96 of 673
Route object: none102.201.9.0/24No route object for it. Add a route object with origin AS329475 in the RIR database for the space.96 of 673
ROA: none102.201.10.0/24No ROA covers it. Add a ROA for AS329475, maxLength 24.96 of 673
Route object: none102.201.10.0/24No route object for it. Add a route object with origin AS329475 in the RIR database for the space.96 of 673
ROA: none102.201.11.0/24No ROA covers it. Add a ROA for AS329475, maxLength 24.96 of 673
Route object: none102.201.11.0/24No route object for it. Add a route object with origin AS329475 in the RIR database for the space.96 of 673

Route objects not announced

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

102.208.44.0/23AFRINICInvalid: maxLength
102.208.46.0/23AFRINICInvalid: maxLength
2c0f:4c0::/32AFRINICValid
2c0f:4c0::/36AFRINICValid
2c0f:4c0::/40AFRINICValid
2c0f:4c0::/44AFRINICValid
2c0f:4c0::/48AFRINICValid

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.