bgpreport

Network · data from 2026-11-12

AS328434 Netovate

Registry name: Netovate (PTY) LTD - Netovate (PTY) LTD, ZA · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS328434, 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.68.47.0/24 Valid Nonecovered by 102.68.40.0/21 673 100% 67
102.68.40.0/24 Valid Nonecovered by 102.68.40.0/21 64 10%low visibility 21
102.68.41.0/24 Valid Nonecovered by 102.68.40.0/21 64 10%low visibility 21
102.68.42.0/24 Valid Nonecovered by 102.68.40.0/21 64 10%low visibility 21
102.68.43.0/24 Valid Nonecovered by 102.68.40.0/21 64 10%low visibility 21
102.68.44.0/24 Valid Nonecovered by 102.68.40.0/21 64 10%low visibility 21
102.68.40.0/21 Valid RIR databaseAFRINIC 671 100% 68
2c0f:ecd8::/32 Valid RIR databaseAFRINIC 635 100% 69

AS-SET

AS328434'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 6 are in fix.csv.

  • Route object: none6
ChangePrefix or setDetailFull-table peers
Route object: none102.68.47.0/24No route object for it. A route object for 102.68.40.0/21 with origin AS328434 covers it (filters allowing more-specifics accept it). Add a route object with origin AS328434 in the RIR database for the space.673 of 673
Route object: none102.68.40.0/24No route object for it. A route object for 102.68.40.0/21 with origin AS328434 covers it (filters allowing more-specifics accept it). Add a route object with origin AS328434 in the RIR database for the space.64 of 673
Route object: none102.68.41.0/24No route object for it. A route object for 102.68.40.0/21 with origin AS328434 covers it (filters allowing more-specifics accept it). Add a route object with origin AS328434 in the RIR database for the space.64 of 673
Route object: none102.68.42.0/24No route object for it. A route object for 102.68.40.0/21 with origin AS328434 covers it (filters allowing more-specifics accept it). Add a route object with origin AS328434 in the RIR database for the space.64 of 673
Route object: none102.68.43.0/24No route object for it. A route object for 102.68.40.0/21 with origin AS328434 covers it (filters allowing more-specifics accept it). Add a route object with origin AS328434 in the RIR database for the space.64 of 673
Route object: none102.68.44.0/24No route object for it. A route object for 102.68.40.0/21 with origin AS328434 covers it (filters allowing more-specifics accept it). Add a route object with origin AS328434 in the RIR database for the space.64 of 673

Route objects not announced

Every route object with origin AS328434 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.