Skip to main content
Akamai

Content Purge and Edge Delivery Issues for Customers Using Enforced mTLS settings

Degraded Lasted 2d 7h · started · Akamai's page

Level
confirmed
Worst impact
Degraded
Components
Edge Delivery, Content Purge
Regions
us
Down Index
37of 100

What to do

  • Check whether you use Akamai Edge Delivery, Content Purge in us. Check your stack

    Paste a package.json, lockfile, Terraform or a list of domains at down.guide/stack to see every provider you depend on.
  • Confirm your retries, queues and scheduled jobs caught up after the 2d 7h it lasted.

    Anything that failed between 2026-03-31 07:03 UTC and 2026-04-02 14:13 UTC may need a replay.
  • Subscribe to Akamai's feed to hear about the next one first. RSS feed

    https://down.guide/feed?provider=akamai works in Slack (/feed subscribe), Discord feed bots and any RSS reader.

Updates from Akamai 6

  1. investigating

    We are investigating an issue with purge and edge delivery related to intermittent failures, latency and/or errors. We are actively investigating the issue and will provide another update within the next 30 minutes. We will soon be posting more details for customers and partners with a valid Control Center login at https://community.akamai.com/customers/s/group/0F90f000000DFgx/service-incident-notifications. If you have questions or are experiencing an impact due to this issue, please use the Support Center on Akamai Community (https://community.akamai.com/customers/s/support), or Akamai Control Center to contact Akamai Technical Support. Contact information is available at https://www.akamai.com/us/en/support/.

    provider

  2. investigating

    We are continuing to investigate this issue. Customers and partners can find more details on the Akamai Community: https://community.akamai.com/customers/s/feed/0D5a7000011IxVDCA0. We will provide the next update as we make progress.

    provider

  3. investigating

    We are continuing to investigate this issue. Customers and partners can find more details on the Akamai Community: https://community.akamai.com/customers/s/feed/0D5a7000011IxVDCA0.

    provider

  4. investigating

    We are continuing to investigate this issue. Customers and partners can find more details on the Akamai Community: https://community.akamai.com/customers/s/feed/0D5a7000011IxVDCA0.

    provider

  5. investigating

    We are continuing to investigate this issue. Customers and partners can find more details on the Akamai Community: https://community.akamai.com/customers/s/feed/0D5a7000011IxVDCA0.

    provider

  6. resolved

    We can confirm that the issue was mitigated at 14:00 UTC on April 2, 2026, and the service has resumed normal operation. Customers and partners can view additional details about the incident by logging in to: https://community.akamai.com/customers/s/feed/0D5a7000011IxVDCA0 or reaching out to Akamai Support. We apologize for the impact and thank you for your patience and continued support. We are committed to making continuous improvements to make our systems better and prevent a recurrence of this issue.

    provider

Reports count in aggregate; nothing about you is shown.

Corrections

None so far.

Something wrong on this page? Report an error or send us a note. Every fix is listed here.

Questions about DWN-677a543804

Is Akamai still down?

No, this incident was resolved 2026-04-02 14:13 UTC. For Akamai's live state, see https://down.guide/akamai.

How long did it last?

2d 7h, from 2026-03-31 07:03 UTC to 2026-04-02 14:13 UTC, by the times Akamai posted.

What was affected?

Akamai named Edge Delivery, Content Purge in us.

What caused it?

Akamai hasn't published a root cause. If it does, it shows here.

Where does this come from?

Akamai's official status page, https://www.akamaistatus.com, quoted verbatim. down.guide's own probes, reports and social counts are labeled as ours.