bgpreport

Network · data from 2026-11-12

AS329135 Unicast Technology

Registry name: UNICAST TECHNOLOGY LTD - UNICAST TECHNOLOGY LTD, KE · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS329135, 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.214.84.0/22 No ROA RIR databaseAFRINIC, RADB 672 100% 66
102.214.84.0/24 No ROA RIR databaseAFRINIC 668 99% 66
102.214.85.0/24 No ROA RIR databaseAFRINIC 668 99% 66
102.214.86.0/24 No ROA RIR databaseAFRINIC 668 99% 66

AS-SET

AS329135'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 8 are in fix.csv.

  • ROA: none4
  • Route object: not announced4
ChangePrefix or setDetailFull-table peers
ROA: none102.214.84.0/22No ROA covers it. Add a ROA for AS329135, maxLength 22.672 of 673
ROA: none102.214.84.0/24No ROA covers it. Add a ROA for AS329135, maxLength 24.668 of 673
ROA: none102.214.85.0/24No ROA covers it. Add a ROA for AS329135, maxLength 24.668 of 673
ROA: none102.214.86.0/24No ROA covers it. Add a ROA for AS329135, maxLength 24.668 of 673

Route objects not announced

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

102.214.84.0/23AFRINICNo ROA
102.214.86.0/23AFRINICNo ROA
102.214.87.0/24AFRINICNo ROA
2c0f:7880::/32AFRINICNo 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.