Running on Akamai?

Akamai property stuck or rules not applying? We clear the backlog.

Akamai is powerful and old enough that the console remembers mistakes made a decade ago. The common trouble is a property version that will not activate on production because of a rule that passed staging, an EdgeWorker build that exceeds the size limit, or a purge that returns success and leaves every POP serving the previous object anyway. We read the activation history, the behaviour tree and the Pragma debug headers until the issue is surfaced and resolved.

  • Since 2015Fixing technology
  • FreeEstimates
  • US teamReal engineers

akamai-activation.log

still broken

What it is

Akamai at a glance

Akamai is the oldest of the large content delivery networks, founded at MIT in 1998 and still one of the biggest capacity networks in the world. The company's bread and butter is the Intelligent Edge Platform, which packages caching, acceleration, security and edge compute into a set of products on top of a single network.

The main product for web acceleration is Ion, with Property Manager as the configuration surface. EdgeWorkers provides a JavaScript runtime on the edge, Image and Video Manager handle media, and the security side is covered by App & API Protector, Bot Manager and Kona. The platform is heavily used by regulated industries, large retailers and global media, and the pricing model and sales process reflect that audience.

Type
Enterprise CDN, edge security and edge compute
First released
1999
License
Proprietary enterprise contract
Maintained by
Akamai Technologies, Inc.
Typically used for
Large retail, banking, media, government, SaaS behind long-term contracts

The honest version

Akamai pros and cons

No technology is all upside. This is where Akamai earns its place and where it tends to cause trouble.

Where Akamai is strong

  • Largest footprint of edge POPsHundreds of thousands of servers across most reachable networks means an Akamai object is close to almost every user, which still matters in markets where other CDNs are thin.
  • Mature security product lineApp & API Protector, Bot Manager and Kona WAF have years of signature and ML data behind them, and security teams at banks are generally comfortable with the stack.
  • Deep configurabilityProperty Manager can model almost any caching, routing, header or origin failover scenario you can describe, which is the reason retailers use it for complex checkout flows.
  • GTM for global traffic steeringGlobal Traffic Management handles active-active origins and regional failover at the DNS layer with real health data, which is harder to replicate on simpler CDNs.
  • EdgeWorkers for programmable logicJavaScript at the edge, running on the same network as the cache, lets teams move header rewrites, auth and A/B logic off the origin.
  • Enterprise support and SLAsFor customers on the right contract, there is an architect on the account, incident response is human, and change windows are supported by people who know the configuration.

Where Akamai bites

  • Console is deep and shows its ageProperty Manager has decades of behaviour options layered on top of each other, and discovering why an older rule matters requires reading history, not just the current view.
  • Pricing is opaque and commit-heavyRate cards are negotiated, overage terms are not always obvious, and a growing workload can quietly consume the commit before anyone warns the business.
  • Activation times are slow by modern standardsStaging in minutes is fine; production can still take significantly longer than the newer edge networks, which affects incident response.
  • EdgeWorkers has hard size limitsA 512KB uncompressed bundle budget forces aggressive tree-shaking, and some common JavaScript libraries will not fit.
  • Smaller customers feel smallIf you are not on an enterprise tier, the self-service experience is noticeably thinner than on Fastly or Cloudflare, and support response times reflect the plan.
  • Migration into or out of Akamai is non-trivialProperty rules do not translate cleanly to another vendor's rule engine, and moving back the other way from a simpler CDN often expands into a longer engagement than planned.

Sound familiar?

Common Akamai problems we fix

The Akamai problems that bring people to us, and what you have once each one is fixed.

activation failed: rule validation error

A property will not activate on production

A rule that passed validation on staging because of a cached behaviour catalog, a behaviour that conflicts with an inherited one in a parent rule, or a user without the correct activation role.

Property active on production with history

EdgeWorker bundle exceeds 512KB

EdgeWorker will not deploy

A bundle that grew past the limit because of a heavy dependency, source maps that ended up in the shipped bundle, or a shared helper library that duplicates code across workers.

Worker fits and ships

Fast Purge: 403 Forbidden

Purge API calls are rejected

An OPEN API client that was created without CCU purge access, a client credential that was rotated and not pushed to the CMS, or a purge URL that is outside the account's authorised group.

Purges accepted and effective

Pragma debug: TCP_MISS from parent

Cache hit rate is lower than it should be

A cache key that varies on an unimportant query parameter, a Vary header from origin that fragments the cache, or a tiered distribution setting that never engaged.

Hit rate back where it should be

Ion: origin SSL CN mismatch

Origin fetches fail SSL validation

An origin certificate whose common name does not match the Host header Akamai forwards, or a certificate chain missing an intermediate that older origins did not need.

Origin SSL clean, no insecure override

CPS: deployment slot occupied

A certificate enrollment stalls

A prior CPS enrollment stuck in the pre-verification slot blocks a new one, often because the first one was abandoned and never cancelled.

CPS clear and enrollments moving

EdgeWorker runtime error

Worker throws under production traffic

An onClientResponse handler that assumes a header exists, or an onClientRequest hook that trips on a malformed URL only real traffic produces.

Worker resilient, errors surfaced

mPulse beacon above 20% sample

Monitoring rate is costing more than planned

A sample rate left at the default on a very high traffic site, pushing the mPulse bill above what was budgeted without anyone noticing until the invoice lands.

Sample rate right for the volume

What we do

Akamai help, from property rescue to EdgeWorkers

Pick up the phone for a blocked activation, or let us run the account day to day.

Rescue
Activations blocked, purges rejected, or EdgeWorkers throwing in production. We get the edge serving correctly first and clean the rules second.
Property Manager cleanup
Rule trees audited, dead behaviours retired, cache keys normalised, and configurations documented so the next engineer does not start from scratch.
EdgeWorkers development
JavaScript workers for header rewrites, auth checks, A/B logic and personalised responses, within the bundle size budget and with proper observability.
Security products
App & API Protector, Bot Manager and Kona tuned against your real traffic, with false-positive review on a cadence that fits your release pace.
Migrations
Moves from Akamai onto Fastly, Cloudflare or a multi-CDN setup, or in the other direction, handled with parallel staging and controlled DNS cutover.
Managed Tech
Property versions reviewed before activation, certificate renewals watched, a dashboard on cache hit rate, and engineers available when a Black Friday rule misfires.

How it works

From first message to fixed

  1. Look Free estimate

    Tell us what's going wrong. We look at it, then tell you plainly what's wrong and what it will cost.

  2. Fix

    We fix the cause, not the symptom. If something is down, getting it back up comes first.

  3. Harden

    Backups, monitoring, updates and access, so the same problem can't quietly come back.

  4. Hand back or stay on

    You get a plain-language write-up. Or we stay on for hosting, upkeep and new work.

Often found together

Running Akamai alongside something else?

We work on the whole stack, so the problem can be wherever it actually is.

Questions

Akamai questions

Something else? Call+1 737 727 7327

Why does my Akamai property activate on staging but fail on production?

Staging runs against a cached catalog of behaviours, so a rule can pass there while failing on production where the current catalog is applied. The second common cause is role based access; the user activating on production needs a role that may not be needed for staging. The activation history on the property shows exactly which rule or role tripped it.

How do we make EdgeWorker bundles fit the size limit?

The budget is 512KB uncompressed, and most overruns come from source maps, duplicated helper libraries across workers, or pulling in a full npm module for one small helper. A production build with tree shaking, bundle analysis, and shared helpers extracted into a lean library almost always brings a worker back under the limit.

Why do Fast Purge calls fail with 403?

The OPEN API client does not have CCU access on its credentials, or the URL being purged belongs to a contract group the client is not authorised on. Check the client's permissions and the group assignment on the purge target; the Akamai control centre will tell you both once you know where to look.

Can we move off Akamai onto Fastly or Cloudflare?

Yes, and we do this regularly. The main work is translating Property Manager behaviours into VCL or Cloudflare rules, verifying cache hit rate and security posture on a parallel hostname, and planning the DNS cutover with a rollback path. The size of the engagement scales with how much custom logic the Akamai property contains.

Is Akamai still the right choice if we are not an enterprise?

Often not. The platform rewards teams that use the deep configurability and have an account team to back them. Smaller workloads usually get better unit economics and a faster feedback loop on Fastly or Cloudflare. We give a plain-English recommendation after looking at your traffic and configuration.

How much does Akamai help cost?

The first conversation and estimate are at no cost. Send the account details and the issue, and a quote is written before any engineering time is booked.

Free estimate

Akamai giving you trouble?

Tell us what you're running and what's going wrong. A person reads it and comes back with an estimate.

  • No charge to find out what it will take
  • If it's urgent, say so

Replies come from a person. By sending, you authorize us to email you back. No marketing.