Akamai Outage History

Akamai experienced an issue with their Email Exchange server that caused delays in external email delivery, affecting telephony components for 2.9 hours on May 21, 2026. The team identified the root cause and implemented a fix at 13:00 UTC, with the service fully restored to normal operation by 14:50 UTC.

Akamai experienced a 22.1-hour outage affecting Configuration Deployment services, specifically preventing EdgeWorkers and mPulse configuration activations from being deployed. The issue was identified and a fix was implemented at 14:55 UTC on May 20, 2026, with services resuming normal operations after continued monitoring to ensure full mitigation.

Akamai experienced a reporting data unavailability issue affecting the 'URL Traffic' and 'URL Responses' reports for approximately 13 days. The incident impacted customers' ability to access reporting data through these specific report types. Akamai identified the root cause, implemented a fix, and gradually restored data availability before confirming full service restoration.

Akamai experienced issues with Cloudlets policy activation that prevented customers from activating their Cloudlets policies for 38 minutes. The problem was caused by a problematic release that affected the Cloudlets service. Akamai resolved the incident by rolling back the release at 18:21 UTC, restoring normal service operations.

Akamai experienced general performance degradation with their Edge Delivery service in Amsterdam, Netherlands for 54 minutes on May 13, 2026. The issue was mitigated at approximately 09:40 UTC and normal service operations resumed.

Akamai experienced an 8-hour Edge Delivery performance degradation between India and Europe caused by a third-party service provider connectivity issue. The incident affected Akamai's Edge Delivery service, causing reduced performance for traffic routing between these regions. The issue was resolved by implementing alternative routing paths while the upstream provider addressed their underlying connectivity problem.

Akamai's Bot Manager Premier experienced an issue where valid traffic was incorrectly blocked due to false positives, affecting the Bot Management service for 27.3 hours. The problem was caused by a software release, which Akamai rolled back at 17:13 UTC on May 11, 2026, and the issue was fully mitigated by 23:13 UTC the same day. The service has since resumed normal operations.

Akamai's Certificate Provisioning System (CPS) experienced issues that prevented users from making changes through the Akamai Control Center, affecting TLS provisioning capabilities. The incident lasted 40 minutes and was mitigated at approximately 11:30 UTC on May 6, 2026, with normal service operations resuming.

Akamai's Bot Manager experienced elevated false positives that incorrectly blocked legitimate user traffic for 1.3 hours on April 30, 2026. The issue affected the Bot Management service, preventing valid end users from accessing websites and applications protected by the service. Akamai implemented a fix at 19:00 UTC and confirmed full service restoration by 20:00 UTC the same day.

Akamai experienced a reporting issue that caused data unavailability in the 'URL Traffic' and 'URL Responses' reports for over 5 days. The incident affected the reporting components of Akamai's service, preventing customers from accessing traffic analytics data. The issue was resolved on May 4, 2026 at 06:50 UTC, restoring normal operation to the reporting services.