Akamai

Affected: Configuration Deployment, Reporting, Web Security Analytics

1. investigating 2026-10-21 15:30 UTC

   We are investigating an emerging issue with Web Security Application, Reporting, and Configuration Deployment related to latency and errors. We are actively investigating the issue and will provide another update within the next 30 minutes. We will soon be posting more details...

2. identified 2026-10-21 15:46 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/0D5a700001aPoFkCAK. We will provide an update within the next 30 minutes.

3. identified 2026-10-21 16:08 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/0D5a700001aPoFkCAK. We will provide an update within the next 60 minutes.

4. identified 2026-10-21 17: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/0D5a700001aPoFkCAK. We will provide an update within the next 60 minutes.

5. identified 2026-10-21 18:02 UTC

   Based on our observations, WSA and Reporting are working as expected. Configuration Deployments are experiencing higher latency and may take longer in the "pending" state than usual. However, these configurations will eventually be deployed to production after a...

Excerpts are shortened. Read the full incident on Akamai's status page.

Affected: Akamai Customer Community

Knock-on incidents at other vendors that started during this one and name Akamai:

• Linode: Customer Security Advisory: PHP Remote Code Execution Vulnerabilities

1. investigating 2026-10-21 15:03 UTC

   Akamai is aware of the recently published remote code execution vulnerabilities CVE-2026-109618 and CVE-2026-10961). Our subject matter experts are actively investigating and taking the appropriate measures. We have released security updates to address these CVEs and monitor for...

Excerpts are shortened. Read the full incident on Akamai's status page.

Affected: NetStorage

Knock-on incidents at other vendors that started during this one and name Akamai:

• Linode: Customer Security Advisory: PHP Remote Code Execution Vulnerabilities

1. investigating 2026-10-21 14:52 UTC

   We are investigating an emerging issue with NetStorage related to performance degradation and timeouts in the Los Angeles area. We are actively investigating the issue and will provide another update within the next 60 minutes. We will soon be posting more details for customers...

2. investigating 2026-10-21 16:01 UTC

   We continue investigating this issue. Customers and partners can find more details on the Akamai Community: https://community.akamai.com/customers/s/feed/0D5a700001aOfDBCA0. We will provide an update within the next 120 minutes.

3. investigating 2026-10-21 17:56 UTC

   We are continuing to work with our third-party service provider to investigate this issue. Customers and partners can find more details on the Akamai Community: https://community.akamai.com/customers/s/feed/0D5a700001aOfDBCA0. We will provide an update as we progress.

Excerpts are shortened. Read the full incident on Akamai's status page.

Affected: Edge Delivery

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-10-02 13:24 UTC

   We are investigating an emerging issue with Edge Delivery related to Edge DNS report with record change on master DNS server not reflected to Akamai Edge DNS. We are actively investigating the issue and will provide another update within the next 30 minutes. We will soon be...

2. investigating 2026-10-02 13:53 UTC

   We are continuing to investigate this issue. Customers and partners can find more details on the Akamai Community: https://community.akamai.com/customers/s/feed/0D5a700001WrkrnCAB. We will provide an update as we progress.

3. investigating 2026-10-02 14:35 UTC

   We are continuing to investigate this issue. Customers and partners can find more details on the Akamai Community: https://community.akamai.com/customers/s/feed/0D5a700001WrkrnCAB. We will provide an update as we progress.

4. resolved 2026-10-02 15:08 UTC

   We can confirm that the issue was mitigated at 14:45 UTC on October 2, 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/0D5a700001WrkrnCAB or...

Excerpts are shortened. Read the full incident on Akamai's status page.

Affected: Akamai Control Center, Configuration Deployment

Failure mode: Orchestration, control plane, service discovery or load balancing failed. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. resolved 2026-09-30 15:03 UTC

   We became aware of an issue with Configuration Deployment and Akamai Control Center related to errors when activating delivery configurations in Property Manager and an inability to access Identity Manager in Akamai Control Center to manage users. The issue lasted between 14:13...

Excerpts are shortened. Read the full incident on Akamai's status page.

Affected: Akamai Control Center, Configuration Deployment

Failure mode: A configuration change caused the failure. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-09-29 20:28 UTC

   We are investigating an emerging issue with Configuration Deployment related to errors while activating delivery configurations in Property Manager. We are actively investigating the issue and will provide another update within the next 30 minutes. We will soon be posting more...

2. investigating 2026-09-29 20:48 UTC

   We are continuing to investigate the issue. We identified another issue in Identity Manager where customers can't access to manage their users in Akamai Control Center. Customers and partners can find more details on the Akamai Community:...

3. resolved 2026-09-29 21:22 UTC

   We can confirm that the issue was mitigated at 20:25 UTC on September 29, 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/0D5a700001WM3dyCAD...

Excerpts are shortened. Read the full incident on Akamai's status page.

Affected: Edge Delivery

Failure mode: CDN or edge layer failed or served bad content. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-09-28 16:22 UTC

   We are investigating an emerging issue in Canada with Edge Delivery related to performance degradation with 0xx error. 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...

2. investigating 2026-09-28 16:41 UTC

   We are continuing to investigate this issue. Customers and partners can find more details on the Akamai Community: https://community.akamai.com/customers/s/feed/0D5a700001W3hnvCABWe will provide an update as we progress.

3. investigating 2026-09-28 18:48 UTC

   We are continuing to investigate this issue. Customers and partners can find more details on the Akamai Community: https://community.akamai.com/customers/s/feed/0D5a700001W3hnvCABWe will provide an update as we progress.

4. investigating 2026-09-28 23:01 UTC

   We are continuing to investigate this issue. Customers and partners can find more details on the Akamai Community: https://community.akamai.com/customers/s/feed/0D5a700001W3hnvCABWe will provide an update as we progress.

5. resolved 2026-09-29 15:43 UTC

   Our third-party service provider has confirmed that the issue was mitigated at 16:08 UTC on September 28, 2026 and the service has resumed normal operation. Customers and partners can view additional details about the incident by logging in to:...

Excerpts are shortened. Read the full incident on Akamai's status page.

Affected: Account Protector

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-09-23 21:30 UTC

   We are investigating an emerging issue with Account Protector. 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...

2. investigating 2026-09-23 22:01 UTC

   We are continuing to investigate this issue. Customers and partners can find more details on the Akamai Community: https://community.akamai.com/customers/s/feed/0D5a700001VNuHQCA1. We will provide an update within the next 60 minutes.

3. investigating 2026-09-23 23:03 UTC

   We are continuing to investigate this issue. We will provide an update within the next 60 minutes.

4. monitoring 2026-09-23 23:25 UTC

   We have implemented a fix for this issue as of 22:45 UTC on September 23, 2026; based on current observations, the service is resuming normal operations. We will continue to monitor to ensure that the impact has been fully mitigated.

5. resolved 2026-09-24 09:44 UTC

   We can confirm that the issue was mitigated at 22:45 UTC on September 23, 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/0D5a700001VNuHQCA1...

Excerpts are shortened. Read the full incident on Akamai's status page.

Affected: Edge Delivery

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. monitoring 2026-09-22 13:19 UTC

   We became aware of an issue with origin server connectivity that caused intermittent connectivity issues and elevated errors for some customers in affected regions. The issue was resolved at approximately 11:41 UTC on 22 September, 2026. The issue appears to have self-corrected;...

2. monitoring 2026-09-22 14:28 UTC

   We have identified that this issue was likely due to upstream congestion related to unexpected maintenance on subsea cables. The impact was primarily observed when requests from outside the APAC region were routed to origins in the APAC region, and when requests from the APAC...

3. monitoring 2026-09-22 21:06 UTC

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

4. monitoring 2026-09-28 10:01 UTC

   Our upstream carrier continues to work on the maintenance of the impacted subsea cables. Although immediate impact has subsided, customers may still experience intermittent impact until the repair works are completed - the current estimate points to early October, 2026, subject...

5. resolved 2026-10-12 23:08 UTC

   We can confirm that the issue was mitigated at 11:41 UTC on 22 September 2026, and the service has resumed normal operation. We have not observed any related impact to the Akamai platform since the issue self-corrected.We remain in contact with our upstream providers and...

Excerpts are shortened. Read the full incident on Akamai's status page.

Affected: Edge Delivery

Failure mode: Network, DNS, routing or connectivity failure. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-09-22 00:30 UTC

   Scheduled upstream provider maintenance is currently taking place along network routes connecting Singapore, Hong Kong, and Japan from September 18, 2026 at 06:30 UTC through October 3, 2026 at 23:59 UTC. While core service remains operational, customers in the affected regions...

2. investigating 2026-09-22 07:41 UTC

   We will continue to monitor the network performance until the maintenance concludes. Customers and partners can find more details on the Akamai Community: https://community.akamai.com/customers/s/feed/0D5a700001V0be8CAB. We will provide the next update as we make progress.

3. resolved 2026-09-30 11:11 UTC

   We can confirm that the issue was mitigated on September 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/0D5a700001V0be8CAB or reaching...

Excerpts are shortened. Read the full incident on Akamai's status page.

Affected: Case Ticketing

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. investigating 2026-09-16 10:51 UTC

   We are investigating an emerging issue with a third-party service provider where users might experience issues creating new tickets with Akamai Support. The issue appears to have started around 08:00 UTC on Sep 16, 2026. The customers can use...

2. investigating 2026-09-16 12:09 UTC

   We are continuing to work our third-party service provider to investigate this issue. Customers and partners can find more details on the Akamai Community: https://community.akamai.com/customers/s/feed/0D5a700001U5jVxCAJ.

3. monitoring 2026-09-16 12:44 UTC

   The third-party provider has implemented a fix for this issue as of 12:20 UTC on 16 Sep,2026; based on current observations, the service is resuming normal operations. Customers and partners can find more details on the Akamai Community:...

4. resolved 2026-09-16 13:58 UTC

   We can confirm that the issue was mitigated at 12:20 UTC on Sep 16, 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/0D5a700001U5jVxCAJ or...

Excerpts are shortened. Read the full incident on Akamai's status page.

Affected: Edge Delivery

Failure mode: CDN or edge layer failed or served bad content. Root cause: A bug in the vendor's own code. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. monitoring 2026-09-15 03:21 UTC

   We became aware of an issue with the HTTPS edge delivery network related to performance issues. The issue lasted between 00:45 UTC and 00:57 UTC on 15 September 2026. We have implemented a fix for this issue, which we believe may have caused the issue; based on current...

2. monitoring 2026-09-15 09:24 UTC

   We are continuing to monitor the issue to ensure that the impact is fully mitigated. We will provide the next update as we make progress. We apologize for the impact.

3. monitoring 2026-09-15 12:59 UTC

   We are continuing to monitor the issue to ensure that the impact is fully mitigated. We will provide the next update as we make progress. We apologize for the impact.

4. resolved 2026-09-16 01:36 UTC

   We can confirm that the issue was mitigated at 00:57 UTC on 15 September 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/0D5a700001TpkinCAB or...

Excerpts are shortened. Read the full incident on Akamai's status page.

Affected: Edge Delivery

Failure mode: CDN or edge layer failed or served bad content. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-09-10 17:37 UTC

   We are investigating an emerging issue with Edge Delivery related to increased latency and elevated end user 403 errors. We are actively investigating the issue and will provide another update within the next 60 minutes. We will soon be posting more details for customers and...

2. identified 2026-09-10 17:58 UTC

   We have identified the cause of the issue and are implementing a fix. We initially mentioned elevated 403 errors in this status page post as an additional symptom of the incident. That was incorrect, and we have removed the reference. Customers and partners can find more details...

3. monitoring 2026-09-10 18:21 UTC

   We have implemented a fix for this issue as of 18:10 UTC on 10 September 2026; based on current observations, the service is resuming normal operations. We will continue to monitor to ensure that the impact has been fully mitigated.

4. resolved 2026-09-11 10:24 UTC

   We can confirm that the issue was mitigated at 00:10 UTC on 11 September 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/0D5a700001T8d9uCAB or...

Excerpts are shortened. Read the full incident on Akamai's status page.

Affected: Edge Delivery, TLS Provisioning (Certificates, CPS)

Failure mode: Network, DNS, routing or connectivity failure. Root cause: Network or DNS. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. resolved 2026-09-04 16:06 UTC

   We became aware of an issue with a network component related to connectivity in the Atlanta, GA region which impacted the Certificate Provisioning System as well as potential impact to other Edge traffic through the region. The issue lasted between 12:21 UTC and 14:19 UTC on...

Excerpts are shortened. Read the full incident on Akamai's status page.

Affected: Reporting

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-09-04 06:15 UTC

   We are investigating an issue with Application Load Balancer (ALB) reporting related to availability with errors. We are actively investigating the issue and will provide another update within the next 60 minutes. We will soon be posting more details for customers and partners...

2. investigating 2026-09-04 07:02 UTC

   We are continuing to investigate this issue. Customers and partners can find more details on the Akamai Community: https://community.akamai.com/customers/s/feed/0D5a700001S7tYbCAJ. We will provide the next update as we make progress.

3. monitoring 2026-09-04 15:48 UTC

   We have implemented a fix for this issue as of 14:20 UTC on 4 September, 2026; based on current observations, the service is resuming normal operations. Customers and partners can find more details on the Akamai Community:...

4. resolved 2026-09-04 21:34 UTC

   We can confirm that the issue was mitigated at 14:20 UTC on 4 September, 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/0D5a700001S7tYbCAJ or...

Excerpts are shortened. Read the full incident on Akamai's status page.

Affected: Reporting

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-08-28 01:33 UTC

   We are investigating an issue with Event Center related to the reporting dashboard being inaccessible with data unavailability. We are actively investigating the issue and will provide another update within the next 60 minutes. We will soon be posting more details for customers...

2. investigating 2026-08-28 02:18 UTC

   We are continuing to investigate this issue. Customers and partners can find more details on the Akamai Community: https://community.akamai.com/customers/s/feed/0D5a700001QvOI6CAN. We will provide the next update as we make progress.

3. monitoring 2026-08-28 03:51 UTC

   We have implemented a fix for this issue as of 03:30 UTC on 28 August 2026; based on current observations, the service is resuming normal operations. Customers and partners can find more details on the Akamai Community:...

4. resolved 2026-08-28 04:52 UTC

   We can confirm that the issue was mitigated at 03:30 UTC on 28 August 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/0D5a700001QvOI6CAN or...

Excerpts are shortened. Read the full incident on Akamai's status page.

Affected: Edge Delivery

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-08-25 16:52 UTC

   We are investigating an emerging issue with Media Services Live 4 related to live streaming with 502 bad gateway errors. 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...

2. investigating 2026-08-25 17:20 UTC

   We are continuing to investigate this issue. Customers and partners can find more details on the Akamai Community: https://community.akamai.com/customers/s/feed/0D5a700001QPRcTCAX?language=en_US. We will provide an update within the next 30 minutes.

3. investigating 2026-08-25 17:52 UTC

   We are continuing to investigate this issue and work towards mitigation. Customers and partners can find more details on the Akamai Community: https://community.akamai.com/customers/s/feed/0D5a700001QPRcTCAX?language=en_US. We will provide an update within the next 30 minutes.

4. identified 2026-08-25 18:13 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/0D5a700001QPRcTCAX. We will provide an update within the next 30 minutes.

5. monitoring 2026-08-25 18:27 UTC

   We have implemented a fix for this issue as of 18:15 UTC on August 25, 2026; based on current observations, the service is resuming normal operations. Customers and partners can find more details on the Akamai Community:...

6. resolved 2026-08-26 10:16 UTC

   We can confirm that the issue was mitigated at 18:15 UTC on August 25, 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/0D5a700001QPRcTCAX or...

7. postmortem 2026-08-26 10:18 UTC

   Customers and partners can find an incident summary report, here: https://community.akamai.com/customers/s/feed/0D5a700001QPRcTCAX

Excerpts are shortened. Read the full incident on Akamai's status page.

Affected: Edge Delivery

Failure mode: CDN or edge layer failed or served bad content. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-08-22 11:21 UTC

   We are investigating an emerging issue with a third-party service provider causing Edge Delivery issues in India. We are working with the service provider and actively investigating the issue and will provide another update within the next 60 minutes. We will soon be posting...

2. investigating 2026-08-22 11:40 UTC

   We are continuing to investigate the issue. After further investigation the issue appears to not be caused by a third-party service provider. Customers and partners can find more details on the Akamai Community: https://community.akamai.com/customers/s/feed/0D5a700001Psh2gCAB....

3. investigating 2026-08-22 12:25 UTC

   We are continuing to investigate this issue. Customers and partners can find more details on the Akamai Community: https://community.akamai.com/customers/s/feed/0D5a700001Psh2gCAB. We will provide an update as we make progress.

4. investigating 2026-08-22 13:16 UTC

   We are continuing to investigate this issue. Customers and partners can find more details on the Akamai Community: https://community.akamai.com/customers/s/feed/0D5a700001Psh2gCAB. We will provide an update as we make progress.

5. investigating 2026-08-22 14:00 UTC

   We are continuing to investigate this issue. Customers and partners can find more details on the Akamai Community: https://community.akamai.com/customers/s/feed/0D5a700001Psh2gCAB. We will provide an update as we make progress.

6. investigating 2026-08-22 15:00 UTC

   We are continuing to investigate this issue. Customers and partners can find more details on the Akamai Community: https://community.akamai.com/customers/s/feed/0D5a700001Psh2gCAB. We will provide an update as we make progress.

7. monitoring 2026-08-22 15:47 UTC

   We have implemented a fix for this issue; 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/0D5a700001Psh2gCAB. We will continue to monitor...

8. resolved 2026-08-24 18:50 UTC

   We can confirm that the issue was mitigated at 14:25 UTC on August 22, 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/0D5a700001Psh2gCAB or...

Excerpts are shortened. Read the full incident on Akamai's status page.

Affected: Reporting

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-08-20 16:43 UTC

   We are investigating an emerging issue with "Traffic by Hostname" related to reporting data availability. We are actively investigating the issue and will provide another update within the next 60 minutes. We will soon be posting more details for customers and partners with a...

2. investigating 2026-08-20 17:34 UTC

   We are continuing to investigate this issue. Customers and partners can find more details on the Akamai Community: https://community.akamai.com/customers/s/group/0F90f000000DFgxCAG/service-incident-notifications. We will provide an update within the next 60 minutes.

3. identified 2026-08-20 18:32 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/group/0F90f000000DFgxCAG/. We will provide an update within the next 60 minutes.

4. identified 2026-08-20 20:12 UTC

   We are continuing working on mitigating the issue and will provide another update as progress is made. We thank you for your patience.Customers and partners can find more details on the Akamai Community: https://community.akamai.com/customers/s/feed/0D5a700001PVMc9CAH

5. investigating 2026-08-24 17:11 UTC

   We are investigating a recurrence of this issue. Customers and partners can find more details on the Akamai Community: https://community.akamai.com/customers/s/feed/0D5a700001PVMc9CAH. We will provide an update within the next 60 minutes.

6. investigating 2026-08-24 18:02 UTC

   We are continuing working on mitigating the issue and will provide another update as progress is made. We thank you for your patience.Customers and partners can find more details on the Akamai Community: https://community.akamai.com/customers/s/feed/0D5a700001PVMc9CAH.

7. monitoring 2026-08-25 14:58 UTC

   We have implemented a fix for this issue as of 14:50 UTC on 25 August, 2026; based on current observations, the service has resumed normal operations. Customers and partners can find more details on the Akamai Community:...

8. monitoring 2026-08-25 20:43 UTC

   Service operations remain in a stable state. We will continue to monitor to ensure that the impact has been fully mitigated.Customers and partners can find more details on the Akamai Community: https://community.akamai.com/customers/s/feed/0D5a700001PVMc9CAH.

9. resolved 2026-08-28 21:59 UTC

   We can confirm that the issue was mitigated at 23:50 UTC on August 24, 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/0D5a700001PVMc9CAH or...

Excerpts are shortened. Read the full incident on Akamai's status page.

Affected: TLS Provisioning (Certificates, CPS)

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. monitoring 2026-08-19 16:10 UTC

   We became aware of an issue with the Certificate Provisioning System (CPS) involving timeouts in the User Interface of Akamai Control Center, as well as errors when using the API. The issue lasted between 03:12 UTC on 19 August 2026 and 03:34 UTC on 19 August 2026; based on...

2. monitoring 2026-08-20 00:20 UTC

   We are continuing to monitor for any further issues.

3. resolved 2026-08-20 14:46 UTC

   We can confirm that the issue was mitigated at 03:34 UTC on 19 August, 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/0D5a700001PHy9qCAD or...

Excerpts are shortened. Read the full incident on Akamai's status page.

Affected: Email

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-08-14 14:53 UTC

   We are investigating an emerging issue with Email Services that may have caused customers to experience bounced emails or email delays when emailing Akamai. We are actively investigating the issue and will provide another update within the next 30 minutes. We will soon be...

2. monitoring 2026-08-14 15:03 UTC

   We have implemented a fix for this issue as of 14:48 UTC on August 14, 2026; based on current observations, the service is resuming normal operations. Customers and partners can find more details on the Akamai Community:...

3. resolved 2026-08-14 19:40 UTC

   We can confirm that the issue was mitigated at 14:48 UTC on August 14, 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/0D5a700001NmwELCAZ or...

Excerpts are shortened. Read the full incident on Akamai's status page.

Affected: Edge Delivery

Failure mode: CDN or edge layer failed or served bad content. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

Knock-on incidents at other vendors that started during this one and name Akamai:

• Linode: Service Issue - Linode Kubernetes Engine Enterprise (LKE-E)- IAD2 (Washington)

1. investigating 2026-08-13 19:31 UTC

   We are investigating an emerging issue with connection drops and increased latency for services in the Miami region. The issue appears to have started at 16:39 UTC on August 13, 2026. We are actively investigating the issue and will provide another update within the next 60...

2. identified 2026-08-13 20:18 UTC

   We have identified the cause of the issue, and a fix is being implemented. Customers should not currently see any impact from the issue. Customers and partners can find more details on the Akamai Community: https://community.akamai.com/customers/s/feed/0D5a700001Nh4U3CAJWe will...

3. identified 2026-08-17 20:07 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/0D5a700001Nh4U3CAJ. We will provide an update when more information becomes available.

4. resolved 2026-08-18 21:29 UTC

   We can confirm that the issue was confirmed mitigated at 20:42 UTC on August 18, 2026 and the service has resumed normal operation. Customers and partners can view additional details about the incident by logging in to:...

Excerpts are shortened. Read the full incident on Akamai's status page.

Affected: Edge Delivery

Failure mode: CDN or edge layer failed or served bad content. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. monitoring 2026-08-12 13:02 UTC

   We became aware of an issue with Edge Delivery in India related to connectivity issues in the form of latency or connection timeouts that impacted traffic flowing from India to multiple geos. The issue lasted between 11:15 UTC on August 12, 2026, and 11:50 UTC on August 12,...

2. resolved 2026-08-13 13:52 UTC

   We can confirm that the issue was mitigated at 11:50 UTC on August 12, 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/0D5a700001NOXC4CAP or...

Excerpts are shortened. Read the full incident on Akamai's status page.

Affected: TLS Provisioning (Certificates, CPS)

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-08-11 10:11 UTC

   We are investigating an emerging issue with the Certificate Provisioning System (CPS) related to delays in domain validation and/or UI mismatches where active enrollments will display no status. We are actively investigating the issue and will provide another update within the...

2. investigating 2026-08-11 10:51 UTC

   We are continuing to investigate this issue. Customers and partners can find more details on the Akamai Community: https://community.akamai.com/customers/s/feed/0D5a700001NAvXBCA1. We will provide an update within the next 60 minutes.

3. investigating 2026-08-11 12:05 UTC

   We are continuing to investigate this issue. Customers and partners can find more details on the Akamai Community: https://community.akamai.com/customers/s/feed/0D5a700001NAvXBCA1. We will provide an update as we make progress.

4. investigating 2026-08-12 13:16 UTC

   We are continuing to investigate this issue. Customers and partners can find more details on the Akamai Community: https://community.akamai.com/customers/s/feed/0D5a700001NAvXBCA1. We will provide an update as we make progress.

5. investigating 2026-08-13 14:17 UTC

   We are continuing to investigate this issue. Customers and partners can find more details on the Akamai Community: https://community.akamai.com/customers/s/feed/0D5a700001NAvXBCA1. We will provide an update as we make progress.

6. resolved 2026-08-14 17:08 UTC

   We can confirm that the issue was mitigated at 08:30 UTC on August 14, 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/0D5a700001NAvXBCA1 or...

Excerpts are shortened. Read the full incident on Akamai's status page.

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. resolved 2026-08-04 14:00 UTC

   We became aware of an issue with Web Security Analytics related to Empty HTTP Accept Language and Content Length header values being logged. The issue lasted between 11:30 UTC on August 3, 2026, and 14:00 UTC on August 4, 2026. We can confirm that the issue is now resolved, and...

Excerpts are shortened. Read the full incident on Akamai's status page.

Affected: Reporting

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. monitoring 2026-08-04 07:54 UTC

   We became aware of an issue with "Traffic by Hostname" related to reporting data availability. The issue lasted between 15:00 UTC on 3 August 2026 and 00:20 UTC on 4 August 2026. We have implemented a fix for this issue as of 00:20 UTC on 4 August 2026; based on current...

2. monitoring 2026-08-04 09:14 UTC

   We are continuing to monitor to ensure that the impact has been fully mitigated. Customers and partners can find more details on the Akamai Community: https://community.akamai.com/customers/s/feed/0D5a700001M2nELCAZ. We will provide the next update as we make progress.

3. monitoring 2026-08-05 00:05 UTC

   Service remains operational. We are continuing to monitor the environment to ensure performance and stability are maintained.Customers and partners can find more details on the Akamai Community: https://community.akamai.com/customers/s/feed/0D5a700001M2nELCAZ. We will provide...

4. monitoring 2026-08-05 08:59 UTC

   We are continuing to monitor the issue to ensure performance and stability are maintained. Customers and partners can find more details on the Akamai Community: https://community.akamai.com/customers/s/feed/0D5a700001M2nELCAZ. We will provide the next update as we make progress.

5. resolved 2026-08-05 14:33 UTC

   We can confirm that the issue was mitigated at 00:20 UTC on August 4, 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/0D5a700001M2nELCAZ or...

Excerpts are shortened. Read the full incident on Akamai's status page.

Affected: Edge Delivery

Failure mode: CDN or edge layer failed or served bad content. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-08-01 10:54 UTC

   We are investigating an emerging issue with HTTP and HTTPS related to partial disruption of service with 400 errors. 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...

2. investigating 2026-08-01 11:12 UTC

   We are continuing to investigate this issue. Customers and partners can find more details on the Akamai Community: https://community.akamai.com/customers/s/feed/0D5a700001LizHpCAJWe will provide an update as we progress.

3. resolved 2026-08-01 12:14 UTC

   We can confirm that the issue was mitigated at 09:05 UTC on August 1, 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/0D5a700001LizHpCAJ or...

Excerpts are shortened. Read the full incident on Akamai's status page.

Affected: NetStorage

Failure mode: A zone, region or data center became unavailable. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-07-29 14:48 UTC

   We are investigating an emerging issue with NetStorage related to observed 5XX errors due to an offline storage region. We are actively investigating the issue and will provide another update within the next 60 minutes. We will soon be posting more details for customers and...

2. investigating 2026-07-29 15:36 UTC

   We are continuing to investigate this issue. Customers and partners can find more details on the Akamai Community: https://community.akamai.com/customers/s/feed/0D5a700001LBrwDCAT. We will provide an update within the next 60 minutes.

3. identified 2026-07-29 16:28 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/0D5a700001LBrwDCAT. We will provide an update within the next 60 minutes.

4. resolved 2026-07-29 17:06 UTC

   We can confirm that the issue was mitigated at 14:21 UTC on 29 July 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/0D5a700001LBrwDCAT, or...

Excerpts are shortened. Read the full incident on Akamai's status page.

Affected: Bot Management

Failure mode: A configuration change caused the failure. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-07-27 01:46 UTC

   We are investigating an issue with Bot Manager related to false positive issues with availability. We are actively investigating the issue and will provide another update within the next 60 minutes. We will soon be posting more details for customers and partners with a valid...

2. monitoring 2026-07-27 02:11 UTC

   We have implemented a fix for this issue as of 01:30 UTC on 27 July 2026; based on current observations, the service is resuming normal operations. Customers and partners can find more details on the Akamai Community:...

3. resolved 2026-07-27 06:07 UTC

   We can confirm that the issue was mitigated at 01:30 UTC on 27 July 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/0D5a700001Kh1F0CAJ or...

Excerpts are shortened. Read the full incident on Akamai's status page.

Affected: Edge Delivery

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. investigating 2026-07-24 12:21 UTC

   We are investigating an emerging issue with HTTP and HTTPS network related to latency issues with 5xx error. 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...

2. investigating 2026-07-24 12:40 UTC

   We are continuing to work with our third-party service provider to investigate this issue. Customers and partners can find more details on the Akamai Community: https://community.akamai.com/customers/s/feed/0D5a700001KQ2QQCA1We will provide an update as we progress.

3. monitoring 2026-07-24 12:56 UTC

   The third-party provider has implemented a fix for this issue as of 12:00 UTC on July 24, 2026: based on current observations, the service is resuming normal operations. Customers and partners can find more details on the Akamai Community:...

4. resolved 2026-07-24 18:45 UTC

   We can confirm that the issue was mitigated at 12:00 UTC on July 24, 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/0D5a700001KQ2QQCA1 or...

Excerpts are shortened. Read the full incident on Akamai's status page.

Affected: Edge Delivery

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-07-19 07:40 UTC

   We are investigating an issue with Edge Delivery where users may have experienced delivery errors and connection time outs. The issue is not occurring at this time. We are actively investigating the cause and will provide the details of the investigation as we make progress. We...

2. investigating 2026-07-19 11:06 UTC

   We are continuing to investigate the cause. Customers and partners can find more details on the Akamai Community: https://community.akamai.com/customers/s/feed/0D5a700001JVmHpCAL We will provide an update as we make progress.

3. monitoring 2026-07-19 13:58 UTC

   The third-party service provider has identified the cause of the issue and implemented a fix as of 04:10 UTC on July 19, 2026; based on current observations, the service is resuming normal operations. Customers and partners can find more details on the Akamai Community:...

4. resolved 2026-07-20 14:46 UTC

   We can confirm that the issue was mitigated at 04:10 UTC on July 19, 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/0D5a700001JVmHpCAL or...

Excerpts are shortened. Read the full incident on Akamai's status page.

Affected: Reporting

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-07-16 04:21 UTC

   We are investigating an issue with Application Load Balancer (ALB) reporting related to availability with errors. We are actively investigating the issue and will provide another update within the next 60 minutes. We will soon be posting more details for customers and partners...

2. investigating 2026-07-16 05:01 UTC

   We are continuing to investigate this issue. Customers and partners can find more details on the Akamai Community: https://community.akamai.com/customers/s/feed/0D5a700001J1h4UCAR. We will provide the next update as we make progress.

3. monitoring 2026-07-16 07:27 UTC

   We have implemented a fix for this issue as of 04:36 UTC on 16 July 2026; based on current observations, the service is resuming normal operations. Customers and partners can find more details on the Akamai Community:...

4. monitoring 2026-07-17 04:45 UTC

   We did not observe a recurrence, and the system looks stable. We continue to monitor to ensure that the impact has been fully mitigated. We will provide the next update as we make progress.

5. resolved 2026-07-23 02:06 UTC

   We can confirm that the issue was mitigated at 04:36 UTC on 16 July 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/0D5a700001J1h4UCAR or...

Excerpts are shortened. Read the full incident on Akamai's status page.

Affected: Edge Delivery

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. investigating 2026-07-02 14:40 UTC

   We are investigating an emerging issue with Edge Delivery involving timeouts and performance degradation in the Pakistan region. 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...

2. investigating 2026-07-02 15:05 UTC

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

3. investigating 2026-07-02 15:34 UTC

   We are continuing to investigate this issue. Customers and partners can find more details on the Akamai Community: https://community.akamai.com/customers/s/feed/0D5a700001GuST3CAN. We will provide an update as we progress.

4. identified 2026-07-02 17:51 UTC

   The issue has been identified as related to a submarine cable issue affecting traffic to/from Pakistan. Customers and partners can find more details on the Akamai Community: https://community.akamai.com/customers/s/feed/0D5a700001GuST3CAN. We will provide an update as we...

5. monitoring 2026-07-02 21:42 UTC

   We have implemented network changes to route traffic away from the affected areas while the ISP continues to work on the submarine cable issue; based on current observations, the service has resumed normal operations. Customers and partners can find more details on the Akamai...

6. resolved 2026-07-06 04:11 UTC

   We can confirm that the issue was mitigated at 4:20 UTC on July 2, 2026 and the service has resumed normal operation. Customers and partners can view additional details about the incident by logging in to: or reaching out to Akamai Support. We apologize for the impact and thank...

Excerpts are shortened. Read the full incident on Akamai's status page.

Affected: Configuration Deployment

Failure mode: A configuration change caused the failure. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-06-30 21:15 UTC

   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...

2. identified 2026-06-30 21:23 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 https://community.akamai.com/customers/s/feed/0D5a700001GabcKCAR. We will provide an update within the next 60 minutes.

3. resolved 2026-06-30 22:02 UTC

   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...

Excerpts are shortened. Read the full incident on Akamai's status page.

Affected: Cloudlets

Failure mode: A configuration change caused the failure. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-06-28 14:45 UTC

   We are investigating an emerging issue with Cloudlets related to issues while activating Application Load Balancing configurations. We are actively investigating the issue and will provide another update within the next 30 minutes. We will soon be posting more details for...

2. investigating 2026-06-28 15:10 UTC

   We are continuing to investigate this issue. Customers and partners can find more details on the Akamai Community: https://community.akamai.com/customers/s/feed/0D5a700001GB7HRCA1. We will provide an update within the next 60 minutes.

3. investigating 2026-06-28 15:57 UTC

   We are continuing to investigate this issue. Customers and partners can find more details on the Akamai Community: https://community.akamai.com/customers/s/feed/0D5a700001GB7HRCA1. We will provide an update within the next 120 minutes.

4. monitoring 2026-06-28 17:22 UTC

   We have implemented a fix for this issue as of 16:50 UTC on June 28, 2026; based on current observations, the service is resuming normal operations. Customers and partners can find more details on the Akamai Community:...

5. monitoring 2026-06-29 00:42 UTC

   We are continuing to monitor for any further issues; 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/0D5a700001GB7HRCA1. We will continue...

6. resolved 2026-06-29 15:42 UTC

   We can confirm that the issue was mitigated at 16:50 UTC on June 28, 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/0D5a700001GB7HRCA1 or...

Excerpts are shortened. Read the full incident on Akamai's status page.

Affected: Log Delivery

Failure mode: A code release introduced the failure. Root cause: A bug in the vendor's own code. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-06-25 18:14 UTC

   We are investigating an emerging issue with DataStream related to configuring and editing DataStream configurations with users possibly running into the following errors: "There are no eligible properties available to clone the stream.", "One or more properties are invalid....

2. investigating 2026-06-25 18:58 UTC

   We are continuing to investigate this issue. Customers and partners can find more details on the Akamai Community: https://community.akamai.com/customers/s/feed/0D5a700001FiyHGCAZ. We will provide an update within the next 60 minutes.

3. investigating 2026-06-25 19:54 UTC

   We are continuing to investigate this issue. Customers and partners can find more details on the Akamai Community: https://community.akamai.com/customers/s/feed/0D5a700001FiyHGCAZ. Subsequent updates around mitigation status will be posted as progress is made.

4. monitoring 2026-06-25 21:59 UTC

   We have rolled back a release which we believe may have caused this issue as of 20:55 UTC on 25 June 2026; based on current observations, the service is resuming normal operations. Customers and partners can find more details on the Akamai Community:...

5. monitoring 2026-06-26 00:45 UTC

   We are actively monitoring the fix for this issue and will share updates on mitigation status as progress continues. Thank you for your patience.

6. resolved 2026-06-26 23:35 UTC

   We can confirm that the issue was mitigated at 20:55 UTC on 25 June 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/0D5a700001FiyHGCAZ, or...

Excerpts are shortened. Read the full incident on Akamai's status page.

Affected: Edge Delivery

Failure mode: CDN or edge layer failed or served bad content. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. resolved 2026-06-16 15:45 UTC

   We became aware of an issue with HTTP and HTTPS related to latency and performance degradation while accessing the applications. The issue lasted between 13:37 UTC and 14:20 UTC on June 16, 2026. We can confirm that the issue is now resolved, and the service has resumed normal...

Excerpts are shortened. Read the full incident on Akamai's status page.

Affected: Log Delivery

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. resolved 2026-06-12 14:58 UTC

   We identified an issue with the Datastream service where between 10:00 UTC and 21:00 UTC on June 11, 2026, customers may have experienced degraded fidelity on CDN observability streams. We can confirm that the issue is now mitigated as of 21:00 UTC on June 11, 2026, and no...

Excerpts are shortened. Read the full incident on Akamai's status page.

Affected: Bot Management

Failure mode: A configuration change caused the failure. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-06-10 18:38 UTC

   We are investigating an emerging issue with Bot Manager Premier related to some legitimate users utilizing a specific rule to be denied. We are actively investigating the issue and will provide another update within the next 30 minutes. We will soon be posting more details for...

2. monitoring 2026-06-10 18:51 UTC

   We have implemented a fix for this issue as of 18:41 UTC on June 10, 2026; based on current observations, the service is resuming normal operations. Customers and partners can find more details on the Akamai Community:...

3. resolved 2026-06-11 16:41 UTC

   We can confirm that the issue was mitigated at 18:41 UTC on June 10, 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/0D5a700001D7uShCAJ or...

Excerpts are shortened. Read the full incident on Akamai's status page.

Affected: Edge Delivery

Failure mode: CDN or edge layer failed or served bad content. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-06-06 04:29 UTC

   We became aware of an issue with Edge Delivery in Americas Region related to elevated request denials and service degradation between 1:00 UTC and 1:30 UTC on June 6, 2026. We are actively investigating the cause of the service degradation within the affected environment and...

2. resolved 2026-06-06 07:21 UTC

   We can confirm that the issue was mitigated at 1:30 UTC on June 6, 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/0D5a700001CQ6lqCAD or...

Excerpts are shortened. Read the full incident on Akamai's status page.

Affected: Edge Delivery

Failure mode: CDN or edge layer failed or served bad content. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-06-05 16:16 UTC

   We are investigating an emerging issue with HTTP Edge IP binding related to API timeouts and transaction failures. 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...

2. investigating 2026-06-05 16:36 UTC

   We are continuing to investigate this issue. Customers and partners can find more details on the Akamai Community: https://community.akamai.com/customers/s/feed/0D5a700001CJCMpCAP. We will provide an update as we progress.

3. investigating 2026-06-08 19:56 UTC

   We are continuing to investigate this issue. Customers and partners can find more details on the Akamai Community: https://community.akamai.com/customers/s/feed/0D5a7000015iVQMCA2 We will provide an update as we progress.

4. investigating 2026-06-11 18:54 UTC

   We are continuing to investigate this issue. Customers and partners can find more details on the Akamai Community: https://community.akamai.com/customers/s/feed/0D5a700001CJCMpCAP. We will provide an update as we progress.

5. resolved 2026-06-19 11:07 UTC

   We can confirm that the issue was mitigated at 17:30 UTC on June 12, 2026, 2026, and the service has resumed normal operation. Customers and partners can view additional details about the incident by logging in to:...

Excerpts are shortened. Read the full incident on Akamai's status page.

Affected: Edge Delivery

Failure mode: CDN or edge layer failed or served bad content. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. resolved 2026-05-27 13:28 UTC

   We became aware of an issue with HTTP and HTTPS related to latency while accessing the applications. The issue lasted between 11:18 UTC and 12:22 UTC on May 27, 2026. We can confirm that the issue is now resolved, and the service has resumed normal operation. Customers and...

Excerpts are shortened. Read the full incident on Akamai's status page.

Affected: Telephony

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-05-21 13:58 UTC

   We are investigating an emerging issue with Email Exchange server related to delay with the emails. 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...

2. identified 2026-05-21 14:00 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/0D5a7000019St8yCAC .We will provide an update within the next 60 minutes.

3. monitoring 2026-05-21 14:04 UTC

   We have implemented a fix for this issue as of 13:00 UTC on May 21, 2026, based on current observations, the service is resuming normal operations. Customers and partners can find more details on the Akamai Community:...

4. resolved 2026-05-21 16:52 UTC

   We can confirm that the issue was mitigated at 14:50 UTC on May 21, 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/0D5a7000019St8yCAC or...

Excerpts are shortened. Read the full incident on Akamai's status page.

Affected: Configuration Deployment

Failure mode: Hardware, power, cooling or another physical failure. Root cause: Hardware or facility. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. investigating 2026-05-20 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...

2. identified 2026-05-20 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.

3. identified 2026-05-20 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.

4. identified 2026-05-20 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.

5. identified 2026-05-20 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.

6. identified 2026-05-20 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.

7. identified 2026-05-20 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.

8. identified 2026-05-20 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.

9. identified 2026-05-20 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.

10. identified 2026-05-20 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. identified 2026-05-20 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.

12. identified 2026-05-20 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.

13. identified 2026-05-20 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.

14. identified 2026-05-20 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.

15. identified 2026-05-20 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.

16. monitoring 2026-05-20 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:...

17. monitoring 2026-05-20 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.

18. resolved 2026-05-21 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...

19. postmortem 2026-05-25 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...

Excerpts are shortened. Read the full incident on Akamai's status page.

Affected: Reporting

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. identified 2026-05-19 10:13 UTC

   We are aware of an issue with the 'URL Traffic' and ‘URL Responses’ report related to reporting data unavailability. We have identified the cause of the issue, and a fix is being implemented. We will soon be posting more details for customers and partners with a valid Control...

2. identified 2026-05-20 08:07 UTC

   The data is slowly getting updated. Customers and partners can find more details on the Akamai Community: https://community.akamai.com/customers/s/feed/0D5a7000018q2TuCAI. We will provide an update once the data catches up.

3. identified 2026-05-22 05:20 UTC

   The data is getting updated. Customers and partners can find more details on the Akamai Community: https://community.akamai.com/customers/s/feed/0D5a7000018q2TuCAI. We will provide an update once the data catches up.

4. monitoring 2026-05-28 09:50 UTC

   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/0D5a7000018q2TuCAI. We will continue to monitor to ensure that the impact has been fully...

5. resolved 2026-06-01 07:46 UTC

   We can confirm that the issue was mitigated 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/0D5a7000018q2TuCAI or reaching out to Akamai Support....

Excerpts are shortened. Read the full incident on Akamai's status page.

Affected: Cloudlets

Failure mode: A code release introduced the failure. Root cause: A bug in the vendor's own code. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-05-14 18:08 UTC

   We are investigating an emerging issue with Cloudlets related to issues with activating Cloudlets policies. We are actively investigating the issue and will provide another update within the next 60 minutes. We will soon be posting more details for customers and partners with a...

2. identified 2026-05-14 18:28 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/0D5a70000189Hk3CAE. We will provide an update within the next 30 minutes.

3. monitoring 2026-05-14 18:37 UTC

   We have rolled back a release which we believe may have caused this issue as of 18:21 UTC on May 14th, 2026; based on current observations, the service is resuming normal operations. Customers and partners can find more details on the Akamai Community:...

4. resolved 2026-05-14 18:45 UTC

   We can confirm that the issue was mitigated at 18:21 UTC on May 14th, 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/0D5a70000189Hk3CAE, or...

Excerpts are shortened. Read the full incident on Akamai's status page.

Affected: Edge Delivery

Failure mode: CDN or edge layer failed or served bad content. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-05-13 09:33 UTC

   We are investigating an emerging issue with Edge Delivery related to general performance degratation in Amsterdam, Netherlands. We are actively investigating the issue and will provide another update within the next 60 minutes. We will soon be posting more details for customers...

2. resolved 2026-05-13 10:25 UTC

   We can confirm that the issue was mitigated at approximately 09:40 UTC on May 13, 2026, and the service has resumed normal operation. Customers and partners can view additional details about the incident by logging in to:...

Excerpts are shortened. Read the full incident on Akamai's status page.

Affected: Edge Delivery

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. investigating 2026-05-12 17:08 UTC

   We are investigating an emerging issue with a third-party service provider, causing performance degradation with Edge Delivery between India and Europe. We are working with the service provider and actively investigating the issue, and will provide another update within the next...

2. investigating 2026-05-12 17:29 UTC

   We are continuing to work with our third-party service provider to investigate this issue. Customers and partners can find more details on the Akamai Community: https://community.akamai.com/customers/s/feed/0D5a7000017mjDUCAY. We will provide an update within the next 60 minutes.

3. investigating 2026-05-12 18:39 UTC

   We are continuing to work with our third-party service provider to investigate this issue. Customers and partners can find more details on the Akamai Community: https://community.akamai.com/customers/s/feed/0D5a7000017mjDUCAY. We will provide an update within the next 120...

4. identified 2026-05-12 19:50 UTC

   Our third-party service provider has 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/0D5a7000017mjDUCAY. Subsequent updates around mitigation...

5. investigating 2026-05-12 22:44 UTC

   We are continuing to work with our third-party service provider to mitigate this issue. Customers and partners can find more details on the Akamai Community: https://community.akamai.com/customers/s/feed/0D5a7000017mjDUCAY. Subsequent updates around mitigation status will be...

6. resolved 2026-05-13 01:08 UTC

   We can confirm that the issue was mitigated at 00:25 UTC on May 13, 2026 and the service has resumed normal operation. While we continue to monitor the upstream provider's progress on their underlying connectivity issue, our services are now stable on alternative paths....

7. postmortem 2026-05-14 15:15 UTC

   Customers and partners can find an incident summary report here: https://community.akamai.com/customers/s/feed/0D5a7000017mjDUCAY

Excerpts are shortened. Read the full incident on Akamai's status page.

Affected: Bot Management

Failure mode: A code release introduced the failure. Root cause: A bug in the vendor's own code. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-05-11 16:03 UTC

   We are investigating an emerging issue with Bot Manager Premier related to false positives with valid traffic being blocked. 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...

2. investigating 2026-05-11 16:29 UTC

   Updating to clarify that the issue appears to be impacting Bot Manager Premier. We are continuing to investigate this issue. Customers and partners can find more details on the Akamai Community: https://community.akamai.com/customers/s/feed/0D5a7000017a38WCAQ. We will provide an...

3. monitoring 2026-05-11 17:23 UTC

   We have rolled back a release which we believe may have caused this issue as of 17:13 UTC on May 11, 2026; based on current observations, the service is resuming normal operations. Customers and partners can find more details on the Akamai Community:...

4. resolved 2026-05-12 19:18 UTC

   We can confirm that the issue was mitigated at 23:13 UTC on May 11, 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/0D5a7000017a38WCAQ or...

Excerpts are shortened. Read the full incident on Akamai's status page.

Affected: TLS Provisioning (Certificates, CPS)

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-05-06 11:21 UTC

   We are investigating an emerging issue with the Certificate Provisioning System (CPS) in the Akamai Control Center related to users being unable to perform changes. We are actively investigating the issue and will provide another update within the next 60 minutes. We will soon...

2. resolved 2026-05-06 12:01 UTC

   We can confirm that the issue was mitigated at approximately 11:30 UTC on May 6, 2026, and the service has resumed normal operation. Customers and partners can view additional details about the incident by logging in to:...

Excerpts are shortened. Read the full incident on Akamai's status page.

Affected: Bot Management

Failure mode: A configuration change caused the failure. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-04-30 18:41 UTC

   We are investigating an emerging issue with Bot Manager related to elevated false positives leading to denied legitimate traffic for end users. We are actively investigating the issue and will provide another update within the next 60 minutes. We will soon be posting more...

2. monitoring 2026-04-30 19:02 UTC

   We have implemented a fix for Bot Manager which addresses the issue we believe may have caused the elevated false positives as of 19:00 UTC on April 30, 2026; based on current observations, the service is resuming normal operations. Customers and partners can find more details...

3. resolved 2026-04-30 20:00 UTC

   We can confirm that the issue was mitigated at 19:00 UTC on April 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/0D5a70000168PJsCAM, or...

Excerpts are shortened. Read the full incident on Akamai's status page.

Affected: Reporting

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-04-29 05:19 UTC

   We are investigating an issue with the 'URL Traffic' report related to reporting data unavailability. We are actively investigating the issue and will provide another update within the next 60 minutes. We will soon be posting more details for customers and partners with a valid...

2. investigating 2026-04-29 05:56 UTC

   We are continuing to investigate this issue. Customers and partners can find more details on the Akamai Community: https://community.akamai.com/customers/s/feed/0D5a7000015pThhCAE. We will provide further updates as we make progress.

3. investigating 2026-04-29 14:31 UTC

   We are continuing to investigate this issue. Customers and partners can find more details on the Akamai Community: https://community.akamai.com/customers/s/feed/0D5a7000015pThhCAE. We will provide further updates as we make progress.

4. investigating 2026-04-30 05:31 UTC

   We are continuing to investigate this issue. Customers and partners can find more details on the Akamai Community: https://community.akamai.com/customers/s/feed/0D5a7000015pThhCAE. We will provide further updates as we make progress.

5. investigating 2026-05-01 08:14 UTC

   We are continuing to investigate this issue. Customers and partners can find more details on the Akamai Community: https://community.akamai.com/customers/s/feed/0D5a7000015pThhCAE. We will provide further updates as we make progress.

6. resolved 2026-05-04 12:24 UTC

   We can confirm that the issue was mitigated at 06:50 UTC on May 4, 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/0D5a7000015pThhCAE or...

Excerpts are shortened. Read the full incident on Akamai's status page.

Affected: Edge Delivery, Bot Management

Failure mode: A zone, region or data center became unavailable. Root cause: Hardware or facility. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-04-28 16:42 UTC

   We have identified an issue with a network resource failure in the MAA (Chennai, IN) region related to intermittent delays and timeouts during peak traffic hours with Delivery and other Akamai services that traverse into/through the MAA region. We are actively investigating...

2. identified 2026-04-28 17:44 UTC

   We are continuing to work to identify opportunities for increasing capacity in the Chennai, IN (MAA) region to prevent issues during peak traffic hours. The current ETA for the hardware replacement effort is end of day on April 29, 2026. Customers and partners can find more...

3. identified 2026-04-28 21:02 UTC

   We have optimized capacity in the Chennai, IN (MAA) region to the best of our abilities. At this time there is no degradation to services in the region, but we do expect that intermittent delays and timeouts for Edge Delivery and other services such as Bot Manager Premier may...

4. identified 2026-04-29 22:13 UTC

   We were able to identify a solution which resulted in additional capacity for the Chennai, IN region and did not experience any degradation over the peak hours on April 29, 2026. The replacement of the network component has been briefly delayed. Customers and partners can find...

5. resolved 2026-05-04 03:05 UTC

   We can confirm that the issue was mitigated at 12:00 UTC on 2 May, 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/0D5a7000015jW2OCAU or...

Excerpts are shortened. Read the full incident on Akamai's status page.