Akamai Status

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

Monitoring: 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 the next update as we make progress.

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

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

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/0D5a700001LizHpCAJWe will provide an update as we progress.

Investigating: 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 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/.