Network · data from 2026-11-12

AS328661 C-Way Computers

Registry name: C-Way Computers CC - C-Way Computers CC, ZA · PeeringDB

12IPv4 routes 100.0% RPKI valid · 66.7% with a route object

1IPv6 routes 100.0% RPKI valid · 100.0% with a route object

0RPKI invalid 0 origin · 0 maxLength

0No ROA 4 with no route object for this origin

0Low visibility seen by under 10% of full-table peers

0Route objects not announced registered with origin AS328661, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS328661, 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.218.228.0/23	Valid	Nonecovered by 102.218.228.0/22	150 22%	44
102.218.230.0/23	Valid	Nonecovered by 102.218.228.0/22	150 22%	44
102.222.236.0/24	Valid	Nonecovered by 102.222.236.0/23	150 22%	44
102.222.237.0/24	Valid	Nonecovered by 102.222.236.0/23	150 22%	44
102.218.184.0/24	Valid	RIR databaseAFRINIC	673 100%	67
102.218.231.0/24	Valid	RIR databaseAFRINIC	673 100%	67
102.215.72.0/22	Valid	RIR databaseAFRINIC	672 100%	67
102.218.184.0/22	Valid	RIR databaseAFRINIC, RADB	672 100%	67
102.218.228.0/22	Valid	RIR databaseAFRINIC	672 100%	67
102.222.236.0/23	Valid	RIR databaseAFRINIC	672 100%	67
2c0f:e898::/32	Valid	RIR databaseAFRINIC	318 50%	63
102.218.184.0/23	Valid	RIR databaseAFRINIC	150 22%	44
102.218.186.0/23	Valid	RIR databaseAFRINIC	150 22%	44

AS-SET

AS328661'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 4 are in fix.csv.

Route object: none4

Change	Prefix or set	Detail	Full-table peers
Route object: none	102.218.228.0/23	No route object for it. A route object for 102.218.228.0/22 with origin AS328661 covers it (filters allowing more-specifics accept it). Add a route object with origin AS328661 in the RIR database for the space.	150 of 673
Route object: none	102.218.230.0/23	No route object for it. A route object for 102.218.228.0/22 with origin AS328661 covers it (filters allowing more-specifics accept it). Add a route object with origin AS328661 in the RIR database for the space.	150 of 673
Route object: none	102.222.236.0/24	No route object for it. A route object for 102.222.236.0/23 with origin AS328661 covers it (filters allowing more-specifics accept it). Add a route object with origin AS328661 in the RIR database for the space.	150 of 673
Route object: none	102.222.237.0/24	No route object for it. A route object for 102.222.236.0/23 with origin AS328661 covers it (filters allowing more-specifics accept it). Add a route object with origin AS328661 in the RIR database for the space.	150 of 673

Change

Prefix or set

Detail

Full-table peers

Route object: none

102.218.228.0/23

No route object for it. A route object for 102.218.228.0/22 with origin AS328661 covers it (filters allowing more-specifics accept it). Add a route object with origin AS328661 in the RIR database for the space.

150 of 673

Route object: none

102.218.230.0/23

150 of 673

Route object: none

102.222.236.0/24

No route object for it. A route object for 102.222.236.0/23 with origin AS328661 covers it (filters allowing more-specifics accept it). Add a route object with origin AS328661 in the RIR database for the space.

150 of 673

Route object: none

102.222.237.0/24

150 of 673

Route objects not announced

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