Content Purge and Edge Delivery Issues for Customers Using Enforced mTLS settings

Update timeline

1. investigating Mar 31, 2026, 07:03 AM UTC

   We are investigating an issue with purge and edge delivery related to intermittent failures, latency and/or 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 partners with a valid Control Center login at https://community.akamai.com/customers/s/group/0F90f000000DFgx/service-incident-notifications. If you have questions or are experiencing an impact due to this issue, please use the Support Center on Akamai Community (https://community.akamai.com/customers/s/support), or Akamai Control Center to contact Akamai Technical Support. Contact information is available at https://www.akamai.com/us/en/support/.

2. investigating Mar 31, 2026, 07:17 AM 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/0D5a7000011IxVDCA0. We will provide the next update as we make progress.

3. investigating Mar 31, 2026, 11:10 AM 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/0D5a7000011IxVDCA0.

4. investigating Mar 31, 2026, 04:18 PM 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/0D5a7000011IxVDCA0.

5. investigating Mar 31, 2026, 09:56 PM 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/0D5a7000011IxVDCA0.

6. resolved Apr 02, 2026, 02:13 PM UTC

   We can confirm that the issue was mitigated at 14:00 UTC on April 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/0D5a7000011IxVDCA0 or reaching out to Akamai Support. We apologize for the impact and thank you for your patience and continued support. We are committed to making continuous improvements to make our systems better and prevent a recurrence of this issue.