CDN – KeyCDN Setup

KeyCDN Integration

KeyCDN is a high-performance content delivery network with straightforward per-bandwidth pricing. When Cyclone Static regenerates a cached page, it automatically purges that URL from the KeyCDN edge so visitors always receive current content.

What You Need

  • A KeyCDN account with a Pull Zone configured for your site
  • Your KeyCDN API Key
  • Your Zone ID

Step 1: Get Your API Key

  1. Log in to the KeyCDN dashboard.
  2. Click your name in the top-right corner and select Account.
  3. Scroll to the API Keys section.
  4. If you don’t have an API key yet, click Add API Key, give it a name (e.g. “Cyclone Static”), and save.
  5. Copy the API key value. Store it securely — KeyCDN shows it once.

Step 2: Get Your Zone ID

  1. In the KeyCDN dashboard, go to Zones.
  2. Click on the zone that pulls from your WordPress site.
  3. The Zone ID is displayed on the zone detail page, and also appears in the URL: app.keycdn.com/zones/12345.

Step 3: Configure Cyclone Static

  1. Go to Cyclone Static → Settings.
  2. Under CDN Integration, set the provider dropdown to KeyCDN.
  3. Enter your API Key.
  4. Enter your Zone ID.
  5. Click Verify Connection. Cyclone will call the KeyCDN API and confirm the credentials are valid.
  6. Click Save Settings.

How Purging Works

When Cyclone regenerates a page, it calls the KeyCDN API to purge that URL from the edge. When you click Clear All Cache on the Dashboard, Cyclone sends a zone-wide flush request, purging all cached content in your zone.

Recommended KeyCDN Zone Settings

For best results:

  • Cache Expiry: Set to a week or longer. Because Cyclone purges actively on every change, you don’t need short TTLs to keep content fresh.
  • Ignore Cache-Control: Leave this off. You want the CDN to respect any cache headers WordPress sends for dynamic bypass scenarios.
  • Geo Protection / Auth / Hotlink: Configure these per your security requirements — they don’t affect Cyclone’s purge behavior.

Troubleshooting

Verify Connection fails: Double-check that you’re using an account-level API key, not an older read-only key. The API key must have permission to issue purge requests (purge is a write operation).

Zone flush fails but URL purge works: This can happen if your Zone ID is entered as a zone name (string) instead of the numeric Zone ID. Confirm you’re entering the number shown in the URL, not the zone’s display name.

Pages still stale after purge: KeyCDN purge propagation is typically fast (under 30 seconds globally). If you’re consistently seeing stale content after longer periods, check the KeyCDN API logs in your account under Statistics → API Logs to confirm purge requests are arriving and returning success responses.