Network · data from 2026-11-12
AS149294 CHAKTOMUK DATA CENTER CO. LTD.
Registry name: CDCCL-AS-AP - CHAKTOMUK DATA CENTER CO. LTD., KH · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS149294, 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.178.19.0/24 | Valid | RIR databaseAPNIC, RADB | 673 100% |
| 103.178.18.0/23 | Valid | RIR databaseAPNIC | 672 100% |
| 103.178.18.0/24 | Valid | RIR databaseAPNIC, RADB | 672 100% |
| 2400:3ee0::/32 | Valid | RIR databaseAPNIC, RADB | 340 53% |
| 2400:3ee0::/48 | Valid | RIR databaseAPNIC | 336 53% |
| 2400:3ee0:1::/48 | Valid | RIR databaseAPNIC | 336 53% |
AS-SET
AS149294's PeeringDB record names no AS-SET.
Fix list
Nothing to change: every route is RPKI valid with a route object in an RIR database, and every route object is announced.
Route objects not announced
Every route object with origin AS149294 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.