Network · data from 2026-11-12

AS55476 CPALL-AS-AP - CP All Public Co., Ltd.

Registry name: CPALL-AS-AP - CP All Public Co., Ltd., TH · not in PeeringDB

3IPv4 routes 100.0% RPKI valid · 100.0% with a route object

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

0RPKI invalid 0 origin · 0 maxLength

0No ROA 0 with no route object for this origin

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

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

Announced routes

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


202.80.233.0/24	Valid	Other IRR onlyNTTCOM, RADB	673 100%	66
2405:9800:c909::/48	Valid	Other IRR onlyRADB	635 100%	70
110.170.246.0/24	Valid	RIR databaseAPNIC, RADB	670 100%	67
203.144.129.0/24	Valid	RIR databaseAPNIC, NTTCOM, RADB	670 100%	67
2001:fb0:101c::/48	Valid	RIR databaseAPNIC, RADB	635 100%	70
2001:fb0:109e::/48	Valid	RIR databaseAPNIC, RADB	635 100%	70

AS-SET

AS55476 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 2 are in fix.csv.

Route object: RIR2

Change	Prefix or set	Detail	Full-table peers
Route object: RIR	202.80.233.0/24	Route object only in NTTCOM, RADB. Add it in the RIR database for the space.	673 of 673
Route object: RIR	2405:9800:c909::/48	Route object only in RADB. Add it in the RIR database for the space.	635 of 636

Change

Prefix or set

Detail

Full-table peers

Route object: RIR

202.80.233.0/24

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

673 of 673

Route object: RIR

2405:9800:c909::/48

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

635 of 636

Route objects not announced

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