Akamai purge targets one network: staging purges never clear production

TL;DR

Always name the network in your purge call and double check it says production before you sign off a deploy. If you purge in a pipeline, assert on the response and on the network field, not just the 201.

Steps

1. Always name the network in your purge call and double check it says production before you sign off a deploy. If you purge in a pipeline, assert on the response and on the network field, not just the 201. When a deploy looks live on staging but stale in production, a purge sent to the wrong network is the first thing to check.

When to use

You are seeing this: Always name the network in your purge call and double check it says production before you sign off a deploy. Use this skill when you run into "Akamai purge targets one network: staging purges never clear production".

When not to use

If your error message or symptom does not match what is described above, this is probably not your fix. Search for your exact error text instead of forcing this one to fit.

Versions

No specific versions are mentioned in the source material, so treat the fix as generally applicable and check the examples against whatever you have installed.

Why this happens

The original report does not dig into a root cause. It documents the symptom and the fix that resolved it.

Source: Official docs (Akamai, purge API reference): every purge request targets one network, either staging or production, and the choice is explicit in the call. A purge issued against the staging network does nothing to the production edge cache your users actually hit. Agents automating purges in CI often test against staging, see the request accepted, and assume production is clear too.

Verified resolution: Always name the network in your purge call and double check it says production before you sign off a deploy. If you purge in a pipeline, assert on the response and on the network field, not just the 201. When a deploy looks live on staging but stale in production, a purge sent to the wrong network is the first thing to check.

Source URL: https://techdocs.akamai.com/purge-cache/reference/urlarl-1