Akamai Fast Purge 429 Rate Limit Error

How to fix it

Try these in order — the most common fix is first.

1. 1. Reduce calls

   Copy steps
   1. Pack as many objects as possible into each request (one object type per request)
   2. Purge by cache tag or CP code instead of individual URLs
   3. Back off and retry after a 429; denied requests do not use tokens
   Did this fix it? Yes No

2. 2. Check your limits

   Copy steps
   1. Call POST /rate-limit-status/{purge-type} to see your current rate and object limits
   2. Make sure other scripts on the same account are not using the shared tokens
   Did this fix it? Yes No

Symptoms

Purge API calls return 429, or 413 for large bodies, so cached content stays stale.

Why it happens

• Request bucket holds 100 tokens and refills at 50 per second
• Per-request object buckets: URL/ARL 10,000 (12,000 per minute refill), CP code 300 (30 per minute), cache tag 5,000 (500 per minute)
• Limits are shared by all API clients in the account
• Request bodies are limited to 50KB (413 if larger)

This guide also covers

• akamai fast purge 429
• akamai purge rate limit
• akamai cache purge not working

The same problem in other apps

All plan limits, paywalls & watermarks guides →

• Cloudflare Error 1015: You Are Being Rate Limited (Cloudflare)

Other Akamai errors

• Akamai Access Denied: You Don't Have Permission to Access This Server
• Akamai Error Reference # Lookup: What the Number Means
• Akamai Gateway Timeout: Proxy Server Did Not Receive a Timely Response
• Akamai Property Validation Failed: Files Already Pending Activation
• Akamai "Unable to Perform Validation at This Time" Activation Error
• Akamai Property Activation Stuck, Slow or 409 Conflict
• Akamai Property Manager: Access Denied, No Edit Access or Name Already Exists
• Akamai Error: You Must Have the Enhanced TLS Module on Your Contract