Akamai Outage History

Akamai experienced edge delivery issues in their Frankfurt (DE-FRA-2) data center, causing performance degradation for customers using Edge Delivery and Enterprise Application Access services. The incident lasted 12.7 hours, with a fix implemented at 13:12 UTC on April 20, 2026, after which services resumed normal operations.

Akamai's NetStorage service experienced issues preventing customers from creating new storage groups or making changes to existing storage groups for 3.5 hours. The incident affected NetStorage operations and was classified as a minor service disruption. Akamai identified the root cause, implemented a fix, and restored normal service operations by 04:57 UTC on April 16, 2026.

Akamai experienced configuration deployment issues in Property Manager where users encountered errors when trying to activate new properties or perform changes to properties related to EdgeWorkers. The incident affected the Akamai Control Center's configuration deployment functionality for 18.3 hours. Akamai identified the root cause, implemented a fix at 11:30 UTC on April 8, 2026, and confirmed the service resumed normal operation.

Akamai's Data Services experienced a reporting issue where "Traffic by Geography" and "URL Traffic" data was missing for dates after March 28, 2026, affecting the Reporting component for approximately 175.6 hours. The issue was identified on April 7th, a fix was implemented on April 13th at 11:00 UTC, and the service was confirmed fully resolved on April 14th with normal operations resumed.

Akamai's Certificate Provisioning System experienced issues for 3.5 hours, causing users to encounter errors when trying to access the application through Akamai Control Center. The incident affected both the Akamai Control Center and Configuration Deployment components. Akamai implemented a fix and confirmed the service resumed normal operations, with monitoring continuing to ensure full mitigation.

Akamai experienced Edge Delivery issues in the Chicago, Illinois region involving packet loss and performance degradation that lasted approximately 213 hours from April 6-10, 2026. The incident affected Akamai's Edge Delivery service, causing degraded performance for customers using content delivery services in that region. Akamai implemented temporary mitigations on April 6th to stabilize service, followed by permanent fixes that fully resolved the issue by April 10th at 23:12 UTC.

Akamai experienced activation failures affecting Cloudlets and NetStorage upload functionality for 77.1 hours starting April 3, 2026. The issue was caused by a system change that was subsequently rolled back at approximately 11:30 UTC on April 3rd, which restored normal service operations. The incident was fully mitigated by 11:29 UTC on April 3rd, with continued monitoring confirming complete resolution by April 6th.

Akamai experienced intermittent failures, latency, and errors affecting content purge and edge delivery services for customers using Enhanced mTLS. The incident lasted 55.2 hours from March 31 to April 2, 2026, impacting customers' ability to purge content and deliver content through Akamai's edge network. The issue was mitigated on April 2, 2026 at 14:00 UTC and services resumed normal operation.

Akamai experienced an 18.9-hour service incident where Cloudlets redirect links were not working properly, later expanded to affect DNS responses over 512 bytes and broader Edge Delivery services. The issue was caused by a system change that required rollback, impacting customers' redirect functionality and DNS resolution. The incident was resolved on March 25, 2026 at 17:24 UTC after the rollback was completed.

Akamai's Certificate Provisioning System (CPS) experienced an issue where the 'Select Cipher Profiles' section failed to update after internal users clicked 'Edit' and 'Save' when modifying deployment settings. The TLS Provisioning component was affected during the 2-hour investigation period. After further investigation, Akamai determined that the issue caused no actual customer impact or service disruption and resolved the incident.