Akamai: Edge Delivery Issues
Affected components: Content Delivery - Edge DeliveryEdge Delivery
Timeline of updates
- investigating
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 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/.
- investigating
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.
- monitoring
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: https://community.akamai.com/customers/s/feed/0D5a700001KQ2QQCA1We will continue to monitor to ensure that the impact has been fully mitigated.
- resolved
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 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.
Archive proof
Rewindex commits each version of an incident it captures to a daily checkpoint, chains it to the day before, and has the checkpoint timestamped by FreeTSA and DigiCert. That proves this record existed by then and has not been changed since, by anyone, Rewindex included.
How the archive is checked, and what it cannot prove.
First version captured 17:03 UTC
In the 2026-10-19 checkpoint, timestamped by FreeTSA and DigiCert on Oct 20, 00:41 UTC. Record hash
c98b18b94139ef1b…
Impact, status and times are the vendor’s own, as last archived. View on stspg.io (opens in new tab).