Network · data from 2026-11-12
AS27291 CDS - Century Data Service, Inc
Registry name: CDS - Century Data Service, Inc, US · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS27291, 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.
| 38.246.126.0/24 | No ROA | RIR databaseARIN | 671 100% |
| 134.195.36.0/24 | Valid | RIR databaseARIN | 671 100% |
AS-SET
AS27291 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 23 are in fix.csv.
- ROA: none1
- Route object: not announced22
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 38.246.126.0/24 | No ROA covers it. Add a ROA for AS27291, maxLength 24. |
Route objects not announced
Route objects with origin AS27291 whose prefix no peer sees AS27291 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 64.71.152.0/24 | ARIN | Valid |
| 64.71.161.0/24 | ARIN | Valid |
| 64.71.171.0/24 | ARIN | Valid |
| 64.71.175.0/24 | ARIN | Valid |
| 64.71.179.0/24 | ARIN | Valid |
| 65.19.178.0/24 | ARIN | Valid |
| 65.19.188.0/24 | ARIN | Valid |
| 65.49.60.0/24 | ARIN | Valid |
| 65.49.65.0/24 | ARIN | Valid |
| 66.220.29.0/24 | ARIN | Valid |
| 74.82.63.0/24 | ARIN | Valid |
| 107.1.169.0/24 | RADB | Valid |
| 134.195.37.0/24 | ARIN | Valid |
| 134.195.38.0/24 | ARIN | Valid |
| 134.195.39.0/24 | ARIN | Valid |
| 184.105.7.0/24 | ARIN | Valid |
| 209.31.22.0/23 | RADB | No ROA |
| 209.118.198.0/24 | RADB | No ROA |
| 2001:470:182::/48 | ARIN | Valid |
| 2001:470:2ae::/48 | ARIN | Valid |
| 2001:470:459::/48 | ARIN | Valid |
| 2001:470:55f::/48 | ARIN | Valid |
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.