Akamai Status

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

Resolved: We can confirm that the issue was mitigated at 02:40 UTC on 29 October 2025, 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/0D5a700000gBYHwCAO 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.

Monitoring: We have implemented a fix for this issue as of 02:40 UTC on 29 October 2025; 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/0D5a700000gBYHwCAO. We will continue to monitor to ensure that the impact has been fully mitigated.

Investigating: 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/0D5a700000gBYHwCAO. We will provide the next update as we make progress.

Investigating: We are investigating an issue with the HTTPS edge delivery network related to latency or availability issues. 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 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/.

Resolved: We became aware of an issue with Content Protector related to availability with Rule ID # 3903402. The issue lasted from around 22:30 UTC on 22 October 2025 to 07:00 UTC on 23 October 2025, and 19:15-20:45 UTC on 27 October 2025. We can confirm that the issue is now resolved, 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/0D5a700000g44I2CAI 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.

Resolved: We can confirm that the issue was mitigated at 01:04 UTC on October 27, 2025, 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/0D5a700000fIcE8CAK 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.01:04 UTC

Monitoring: We have implemented a fix for what we believe may have caused this issue as of 01:04 UTC on October 27, 2025; 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/0D5a700000fIcE8CAK. We will continue to monitor to ensure that the impact has been fully mitigated

Identified: We are continuing to work on the fix for this issue. Subsequent updates will be posted as progress is made. Customers and partners can find more details on the Akamai Community: https://community.akamai.com/customers/s/feed/0D5a700000fIcE8CAK.

Identified: We are continuing to work on the fix for this issue. Subsequent updates will be posted as progress is made. Customers and partners can find more details on the Akamai Community: https://community.akamai.com/customers/s/feed/0D5a700000fIcE8CAK.

Identified: We are continuing to work on the fix for this issue. Subsequence updates will be posted as progress is made. 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/.

Identified: We have identified an issue with Web Security Analytics and Bot Endpoint Protection reports related to degradation in those reports. 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/0D5a700000fIcE8CAK. Subsequence updates will be posted as progress is made.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/.

Resolved: We can confirm that the issue was mitigated at 01:04 UTC on October 27, 2025, 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/0D5a700000fIcE8CAK 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.01:04 UTC

Monitoring: We have implemented a fix for what we believe may have caused this issue as of 01:04 UTC on October 27, 2025; 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/0D5a700000fIcE8CAK. We will continue to monitor to ensure that the impact has been fully mitigated

Identified: We are continuing to work on the fix for this issue. Subsequent updates will be posted as progress is made. Customers and partners can find more details on the Akamai Community: https://community.akamai.com/customers/s/feed/0D5a700000fIcE8CAK.

Identified: We are continuing to work on the fix for this issue. Subsequent updates will be posted as progress is made. Customers and partners can find more details on the Akamai Community: https://community.akamai.com/customers/s/feed/0D5a700000fIcE8CAK.

Identified: We are continuing to work on the fix for this issue. Subsequence updates will be posted as progress is made. 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/.

Identified: We have identified an issue with Web Security Analytics and Bot Endpoint Protection reports related to degradation in those reports. 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/0D5a700000fIcE8CAK. Subsequence updates will be posted as progress is made.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/.