Akamai incident: Edge Delivery - HTTP Content Delivery in Europe

Affected components

• Edge Delivery

1. resolvedJun 19, 2026, 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: https://community.akamai.com/customers/s/feed/0D5a7000015iVQMCA2, 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.

2. investigatingJun 11, 2026, 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.

3. investigatingJun 8, 2026, 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. investigatingJun 5, 2026, 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.

5. investigatingJun 5, 2026, 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 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/.

What APIStatus.watch saw

Our 5-minute checks didn't record a change in Akamai's overall status around this incident. Smaller or regional incidents often leave a provider's overall status green.

Other services with incidents at the same time

Overlapping incidents aren't necessarily related.

• Snowflake: INC20000030Critical · Jun 8, 2026, 15:23 UTC
• Snowflake: INC20000032Critical · Jun 11, 2026, 00:30 UTC
• 1Password: Device Trust Authentication Service Experiencing Timeout ErrorsCritical · Jun 11, 2026, 21:49 UTC
• Snowflake: INC20000034Critical · Jun 15, 2026, 14:30 UTC
• Render: Issues with GitHub connectionsMajor · Jun 5, 2026, 16:21 UTC
• Pinecone: [Serverless][AWS][us-west-2] 5xx errors for some requests on some indexesMajor · Jun 6, 2026, 17:05 UTC
• CircleCI: macOS jobs failing to startMajor · Jun 7, 2026, 04:20 UTC
• Cloudinary: DAM View Assets ErrorMajor · Jun 7, 2026, 13:30 UTC
• Expo: EAS OutageMajor · Jun 9, 2026, 02:35 UTC
• Snyk: Degradation Affecting app.snyk.ioMajor · Jun 9, 2026, 11:22 UTC

How often does Akamai have incidents?

Akamai reported 21 incidents in the last 90 days. A typical incident lasted 13h 47m. See Akamai's uptime and incident history