Akamai Incident History

1. resolvedOct 2 · 15:08 UTC

   We can confirm that the issue was mitigated at 14:45 UTC on October 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/0D5a700001WrkrnCAB 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.

Reported by Akamai on their status page.

1. resolvedSep 30 · 15:03 UTC

   We became aware of an issue with Configuration Deployment and Akamai Control Center related to errors when activating delivery configurations in Property Manager and an inability to access Identity Manager in Akamai Control Center to manage users. The issue lasted between 14:13 UTC and 14:34 UTC on September 30, 2026. 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/0D5a700001WM3dyCAD 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.

Reported by Akamai on their status page.

1. ResolvedSep 30 · 15:03 UTC

   We became aware of an issue with Configuration Deployment and Akamai Control Center related to errors when activating delivery configurations in Property Manager and an inability to access Identity Manager in Akamai Control Center to manage users. The issue lasted between 14:13 UTC and 14:34 UTC on September 30, 2026. 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/0D5a700001WM3dyCAD 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.

Reported by Akamai on their status page.

1. resolvedSep 29 · 21:22 UTC

   We can confirm that the issue was mitigated at 20:25 UTC on September 29, 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/0D5a700001WM3dyCAD 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.

Reported by Akamai on their status page.

1. resolvedSep 29 · 15:43 UTC

   Our third-party service provider has confirmed that the issue was mitigated at 16:08 UTC on September 28, 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/0D5a700001W3hnvCAB 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.

Reported by Akamai on their status page.

1. UpdateSep 28 · 23:01 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/0D5a700001W3hnvCABWe will provide an update as we progress.

Reported by Akamai on their status page.

1. resolvedSep 24 · 09:44 UTC

   We can confirm that the issue was mitigated at 22:45 UTC on September 23, 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/0D5a700001VNuHQCA1 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.

Reported by Akamai on their status page.

1. ResolvedSep 24 · 09:44 UTC

   We can confirm that the issue was mitigated at 22:45 UTC on September 23, 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/0D5a700001VNuHQCA1 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.

Reported by Akamai on their status page.

1. monitoringSep 28 · 10:01 UTC

   Our upstream carrier continues to work on the maintenance of the impacted subsea cables. Although immediate impact has subsided, customers may still experience intermittent impact until the repair works are completed - the current estimate points to early October, 2026, subject to change. Customers and partners can find more details on the Akamai Community: https://community.akamai.com/customers/s/feed/0D5a700001V5RQqCAN. We will continue to monitor to ensure that the impact has been fully mitigated.

Reported by Akamai on their status page.

1. UpdateSep 28 · 10:01 UTC

   Our upstream carrier continues to work on the maintenance of the impacted subsea cables. Although immediate impact has subsided, customers may still experience intermittent impact until the repair works are completed - the current estimate points to early October, 2026, subject to change. Customers and partners can find more details on the Akamai Community: https://community.akamai.com/customers/s/feed/0D5a700001V5RQqCAN. We will continue to monitor to ensure that the impact has been fully mitigated.

Reported by Akamai on their status page.

1. resolvedSep 30 · 11:11 UTC

   We can confirm that the issue was mitigated on September 30, 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/0D5a700001V0be8CAB 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.

Reported by Akamai on their status page.

1. ResolvedSep 30 · 11:11 UTC

   We can confirm that the issue was mitigated on September 30, 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/0D5a700001V0be8CAB 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.

Reported by Akamai on their status page.

1. resolvedSep 16 · 13:58 UTC

   We can confirm that the issue was mitigated at 12:20 UTC on Sep 16, 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/0D5a700001U5jVxCAJ 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.

Reported by Akamai on their status page.

1. ResolvedSep 16 · 13:58 UTC

   We can confirm that the issue was mitigated at 12:20 UTC on Sep 16, 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/0D5a700001U5jVxCAJ 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.

Reported by Akamai on their status page.

1. resolvedSep 16 · 01:36 UTC

   We can confirm that the issue was mitigated at 00:57 UTC on 15 September 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/0D5a700001TpkinCAB 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.

Reported by Akamai on their status page.

1. UpdateSep 15 · 12:59 UTC

   We are continuing to monitor the issue to ensure that the impact is fully mitigated. We will provide the next update as we make progress. We apologize for the impact.

Reported by Akamai on their status page.

1. resolvedSep 11 · 10:24 UTC

   We can confirm that the issue was mitigated at 00:10 UTC on 11 September 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/0D5a700001T8d9uCAB 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.

Reported by Akamai on their status page.

1. ResolvedSep 11 · 10:24 UTC

   We can confirm that the issue was mitigated at 00:10 UTC on 11 September 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/0D5a700001T8d9uCAB 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.

Reported by Akamai on their status page.