Skip to main content
Akamai

Configuration Deployment Issues in Property Manager

Degraded Lasted 48m · started · Akamai's page

Level
confirmed
Worst impact
Degraded
Components
Configuration Deployment
Regions
us
Down Index
31of 100

What to do

  • Check whether you use Akamai Configuration Deployment 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 48m it lasted.

    Anything that failed between 2026-06-30 21:15 UTC and 2026-06-30 22:02 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 3

  1. investigating

    We are investigating an emerging issue with Akamai Control Center related to Property Manager issues, where users may experience errors when trying to activate new properties or perform changes to their properties related to EdgeWorkers. 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/feed/0D5a700001GabcKCAR. 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. identified

    We have identified the cause of the issue, and a fix is being implemented. Customers and partners can find more details on the Akamai https://community.akamai.com/customers/s/feed/0D5a700001GabcKCAR. We will provide an update within the next 60 minutes.

    provider

  3. resolved

    We can confirm that the issue was mitigated at 21:14 UTC on June 30, 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/0D5a700001GabcKCAR 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-a41f62c3e0

Is Akamai still down?

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

How long did it last?

48m, from 2026-06-30 21:15 UTC to 2026-06-30 22:02 UTC, by the times Akamai posted.

What was affected?

Akamai named Configuration Deployment 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.