Minor impactResolvedCDN

Akamai incident: Configuration Deployment issues with EdgeWorkers and mPulse configuration activations

Akamai reported this minor-impact incident on its official status page on May 20, 2026, 14:29 UTC. It was resolved after 22h 7m.

Right now Akamai is operational. Live Akamai status →

🔔 Get alerted when Akamai has issuesFree · email alerts · no credit card
May 20, 2026, 14:29 UTC
started
May 21, 2026, 12:36 UTC
resolved
22h 7m
duration
Minor
impact

Affected components

  • Configuration Deployment
  1. postmortemMay 25, 2026, 23:08 UTC

    Starting around 12:00 UTC on May 20, 2026, users experienced difficulties with configuration deployments for mPulse and EdgeWorkers. During this period, activations within Property Manager were impacted, preventing affected customers from successfully updating or deploying these configurations. Akamai initiated an investigation and determined that the issue was caused by a tripped circuit breaker, which resulted in multiple racks in the data center losing power. We responded with a series of coordinated actions to address both the immediate power outage and its downstream effects on critical services. At 14:45 UTC on May 20, 2026, a failover was completed, and by 14:55 UTC on May 20, 2026, error rates in the Akamai Control Center began to decrease, and the issue was mitigated. We will continue to investigate the root cause and will take appropriate preventive actions. We apologize for the impact. We appreciate your patience as we worked to resolve this issue. If you have further ques

  2. resolvedMay 21, 2026, 12:36 UTC

    We can confirm that the issue was mitigated at 14:55 UTC on May 20, 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/0D5a7000019DgxBCAS 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.

  3. monitoringMay 20, 2026, 23:23 UTC

    We are continuing to monitor this issue. Customers and partners can find more details on the Akamai Community: https://community.akamai.com/customers/s/feed/0D5a7000019DgxBCAS. We will continue to monitor to ensure that the impact has been fully mitigated.

  4. monitoringMay 20, 2026, 20:25 UTC

    We have implemented a fix for this issue as of 14:55 UTC on May 20, 2026; based on current observations, the service is resuming normal operations. Customers and partners can find more details on the Akamai Community: https://community.akamai.com/customers/s/feed/0D5a7000019DgxBCAS. We will continue to monitor to ensure that the impact has been fully mitigated.

  5. identifiedMay 20, 2026, 20:00 UTC

    We are continuing to work on a fix for this issue. Customers and partners can find more details on the Akamai Community: https://community.akamai.com/customers/s/feed/0D5a7000019DgxBCAS. We will provide an update within the next 30minutes.

  6. identifiedMay 20, 2026, 19:35 UTC

    We are continuing to work on a fix for this issue. Customers and partners can find more details on the Akamai Community: https://community.akamai.com/customers/s/feed/0D5a7000019DgxBCAS. We will provide an update within the next 30minutes.

  7. identifiedMay 20, 2026, 19:09 UTC

    We are continuing to work on a fix for this issue. Customers and partners can find more details on the Akamai Community: https://community.akamai.com/customers/s/feed/0D5a7000019DgxBCAS. We will provide an update within the next 30minutes.

  8. identifiedMay 20, 2026, 18:45 UTC

    We are continuing to work on a fix for this issue. Customers and partners can find more details on the Akamai Community: https://community.akamai.com/customers/s/feed/0D5a7000019DgxBCAS. We will provide an update within the next 30minutes.

  9. identifiedMay 20, 2026, 18:17 UTC

    We are continuing to work on a fix for this issue. Customers and partners can find more details on the Akamai Community: https://community.akamai.com/customers/s/feed/0D5a7000019DgxBCAS. We will provide an update within the next 30minutes.

  10. identifiedMay 20, 2026, 17:53 UTC

    We are continuing to work on a fix for this issue. Customers and partners can find more details on the Akamai Community: https://community.akamai.com/customers/s/feed/0D5a7000019DgxBCAS. We will provide an update within the next 30minutes.

  11. identifiedMay 20, 2026, 17:28 UTC

    We are continuing to work on a fix for this issue. Customers and partners can find more details on the Akamai Community: https://community.akamai.com/customers/s/feed/0D5a7000019DgxBCAS. We will provide an update within the next 30minutes.

  12. identifiedMay 20, 2026, 17:02 UTC

    We are continuing to work on a fix for this issue. Customers and partners can find more details on the Akamai Community: https://community.akamai.com/customers/s/feed/0D5a7000019DgxBCAS. We will provide an update within the next 30minutes.

  13. identifiedMay 20, 2026, 16:36 UTC

    We are continuing to work on a fix for this issue. Customers and partners can find more details on the Akamai Community: https://community.akamai.com/customers/s/feed/0D5a7000019DgxBCAS. We will provide an update within the next 30minutes.

  14. identifiedMay 20, 2026, 16:16 UTC

    We are continuing to work on a fix for this issue. Customers and partners can find more details on the Akamai Community: https://community.akamai.com/customers/s/feed/0D5a7000019DgxBCAS. We will provide an update within the next 30minutes.

  15. identifiedMay 20, 2026, 15:55 UTC

    We are continuing to work on a fix for this issue. Customers and partners can find more details on the Akamai Community: https://community.akamai.com/customers/s/feed/0D5a7000019DgxBCAS. We will provide an update within the next 30minutes.

  16. identifiedMay 20, 2026, 15:37 UTC

    We are continuing to work on a fix for this issue. Customers and partners can find more details on the Akamai Community: https://community.akamai.com/customers/s/feed/0D5a7000019DgxBCAS. We will provide an update within the next 30minutes.

  17. identifiedMay 20, 2026, 15:18 UTC

    We are continuing to work on a fix for this issue. Customers and partners can find more details on the Akamai Community: https://community.akamai.com/customers/s/feed/0D5a7000019DgxBCAS. We will provide an update within the next 30minutes.

  18. identifiedMay 20, 2026, 14:50 UTC

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

  19. investigatingMay 20, 2026, 14:29 UTC

    We are investigating an emerging issue with Configuration Deployment related to EdgeWorkers and mPulse configuration activations. 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/.

What APIStatus.watch saw

Our 5-minute checks didn't record a change in Akamai's overall status around this incident. Smaller or regional incidents often leave a provider's overall status green.

Other services with incidents at the same time

Overlapping incidents aren't necessarily related.

How often does Akamai have incidents?

Akamai reported 21 incidents in the last 90 days. A typical incident lasted 13h 47m. See Akamai's uptime and incident history

Akamai incident on May 20, 2026: Configuration Deployment issues with EdgeWorkers and mPulse configuration activations · APIStatus.watch