Akamai Outage History

Akamai's Enhanced TLS Delivery Network experienced intermittent TLS errors that specifically affected customers using OpenJDK when connecting to Akamaized hostnames. The Edge Delivery service was impacted for 97.4 hours before the issue was mitigated on March 20, 2026 at 18:35 UTC. The service has since resumed normal operation.

Akamai experienced issues with Enterprise Application Access (EAA) specifically related to device postures, affecting customers' ability to properly authenticate and access enterprise applications. The incident lasted 2.4 hours and was classified as a minor service disruption. The issue was mitigated at 12:00 UTC on March 17, 2026, and normal service operations resumed.

Akamai experienced connectivity issues at their Compute Washington Data Center starting at 18:00 UTC on March 13, 2026, affecting multiple services including Account Protector, Bot Manager Premier, Enterprise Application Access (EAA), and ETP/SIA components. The incident impacted various functionalities across these services including API services, web proxies, name servers, reporting, and configuration systems. The issue was identified and mitigated by 18:50 UTC, with normal service operations resuming after approximately 1.4 hours of disruption.

Akamai Control Center experienced an issue where users were unable to edit the thresholds of existing alerts in the platform's alerting system. The incident affected the Akamai Control Center's alert management functionality. The issue was resolved after 9 minutes of investigation and remediation efforts.

Akamai experienced a DNS malicious filtering issue where legitimate fully qualified domain names (FQDNs) were erroneously flagged as malicious, affecting multiple Akamai products including Global Traffic Management. The incident lasted 4.4 hours, with Akamai identifying the root cause and implementing a fix before confirming mitigation at 20:39 UTC on March 10, 2026.

Akamai experienced compute connectivity issues starting at 18:10 UTC that impacted multiple services including Account Protector, Bot Manager Premier, Enterprise Application Access (EAA), and ETP/SIA components. The incident affected various ETP/SIA functions including client access, configuration, connectors, name servers, reporting, and web proxy services. Akamai implemented a fix at 21:16 UTC and confirmed full service restoration after 3.2 hours of disruption.

Akamai's Bot Manager Premier experienced an issue where legitimate traffic was being incorrectly blocked due to elevated false positives. The incident affected the Bot Management component and lasted 7 minutes. Akamai investigated the issue and provided support channels for affected customers.

Akamai's Enterprise Application Access (EAA) service experienced issues with modifying existing third-party Identity Providers (IdPs) for approximately 1.4 hours. The problem was caused by a software release, which Akamai rolled back at 20:55 UTC on March 5, 2026 to restore normal service operations.

Akamai's compute and edge delivery services in the Mumbai, India region experienced degraded networking performance and packet loss due to issues with a third-party service provider's cable system restoration activities. The incident occurred in multiple phases between February 27-28, 2026, affecting customers connecting to the Mumbai region with network connectivity problems. Akamai applied mitigation measures and worked with the third-party provider to resolve the underlying cable system issues, with normal service operations resuming by February 28, 2026.

A third-party service provider issue caused degraded networking performance and packet loss affecting Akamai's compute and edge delivery services in the India region for 6.4 hours. Akamai implemented a temporary fix at 13:10 UTC on February 27, 2026, which restored normal operations while they continued working with the third-party provider for a permanent resolution. The incident was fully resolved at 19:48 UTC the same day.