bgpreport

Network · data from 2026-11-12

AS329797 ISP COZA (PTY) LTD - ISP COZA (PTY) LTD

Registry name: ISP COZA (PTY) LTD - ISP COZA (PTY) LTD, ZA · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS329797, 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.120.0/22 Valid None 672 100% 66
102.201.120.0/23 Valid None 46 7%low visibility 19
102.201.122.0/23 Valid None 46 7%low visibility 19

AS-SET

AS329797 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 3 are in fix.csv.

  • Route object: none3
ChangePrefix or setDetailFull-table peers
Route object: none102.201.120.0/22No route object for it. Add a route object with origin AS329797 in the RIR database for the space.672 of 673
Route object: none102.201.120.0/23No route object for it. Add a route object with origin AS329797 in the RIR database for the space.46 of 673
Route object: none102.201.122.0/23No route object for it. Add a route object with origin AS329797 in the RIR database for the space.46 of 673

Route objects not announced

Every route object with origin AS329797 is announced.

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.