Network · data from 2026-11-12

AS23875 CSL-AS-AP - CSL Limited

Registry name: CSL-AS-AP - CSL Limited, HK · not in PeeringDB

7IPv4 routes 42.9% RPKI valid · 85.7% with a route object

0IPv6 routes

1RPKI invalid 1 origin · 0 maxLength

3No ROA 1 with no route object for this origin

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

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS23875, 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.


103.17.29.0/24	Invalid: origin	Other origin only	79 12%	38
203.29.222.0/24	No ROA	Other IRR onlyRADB, REACH	673 100%	67
202.6.94.0/24	No ROA	Other IRR onlyNTTCOM, RADB, REACH	670 100%	67
202.164.27.0/24	No ROA	Other IRR onlyRADB, REACH	670 100%	67
63.216.59.0/24	Valid	RIR databaseAPNIC	673 100%	67
63.216.61.0/24	Valid	RIR databaseAPNIC	673 100%	67
63.216.62.0/24	Valid	RIR databaseAPNIC	673 100%	67

AS-SET

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

ROA: origin1
ROA: none3
Route object: none1
Route object: RIR3

Change	Prefix or set	Detail	Full-table peers
ROA: origin	103.17.29.0/24	ROAs covering it name AS3491, AS31713, AS135426, not AS23875. If AS23875 should announce it, add a ROA for AS23875.	79 of 673
Route object: none	103.17.29.0/24	Route objects for it name AS31713, AS135426. Add a route object with origin AS23875 in the RIR database for the space.	79 of 673
ROA: none	203.29.222.0/24	No ROA covers it. Add a ROA for AS23875, maxLength 24.	673 of 673
Route object: RIR	203.29.222.0/24	Route object only in RADB, REACH. Add it in the RIR database for the space.	673 of 673
ROA: none	202.6.94.0/24	No ROA covers it. Add a ROA for AS23875, maxLength 24.	670 of 673
Route object: RIR	202.6.94.0/24	Route object only in NTTCOM, RADB, REACH. Add it in the RIR database for the space.	670 of 673
ROA: none	202.164.27.0/24	No ROA covers it. Add a ROA for AS23875, maxLength 24.	670 of 673
Route object: RIR	202.164.27.0/24	Route object only in RADB, REACH. Add it in the RIR database for the space.	670 of 673

Change

Prefix or set

Detail

Full-table peers

ROA: origin

103.17.29.0/24

ROAs covering it name AS3491, AS31713, AS135426, not AS23875. If AS23875 should announce it, add a ROA for AS23875.

79 of 673

Route object: none

103.17.29.0/24

Route objects for it name AS31713, AS135426. Add a route object with origin AS23875 in the RIR database for the space.

79 of 673

ROA: none

203.29.222.0/24

No ROA covers it. Add a ROA for AS23875, maxLength 24.

673 of 673

Route object: RIR

203.29.222.0/24

Route object only in RADB, REACH. Add it in the RIR database for the space.

673 of 673

ROA: none

202.6.94.0/24

No ROA covers it. Add a ROA for AS23875, maxLength 24.

670 of 673

Route object: RIR

202.6.94.0/24

Route object only in NTTCOM, RADB, REACH. Add it in the RIR database for the space.

670 of 673

ROA: none

202.164.27.0/24

No ROA covers it. Add a ROA for AS23875, maxLength 24.

670 of 673

Route object: RIR

202.164.27.0/24

Route object only in RADB, REACH. Add it in the RIR database for the space.

670 of 673

Route objects not announced

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