Akamai

Mar 9, 22:36 UTC
Resolved - We can confirm that the issue was mitigated at 21:16 UTC on March 9, 2026 and the service has resumed normal operation. Customers and partners can view additional details about the incident by logging in to: 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.

Mar 9, 21:32 UTC
Monitoring - We have implemented a fix for this issue as of 21:16 UTC on March 9, 2026; …

Mar 7, 22:06 UTC
Resolved - We can confirm that the issue was mitigated at 22:00 UTC on March 7, 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/0D5a700000xlBv4CAE, 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.

Mar 7, 21:43 UTC
Update - We are continuing to implement a fix for this issue. Thank you for your patience. …

Mar 5, 22:25 UTC
Resolved - We can confirm that the issue was mitigated at 20:55 UTC on March 5, 2026 and the service has resumed normal operation. Customers and partners can view additional details about the incident by logging in to: 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.

Mar 5, 21:40 UTC
Monitoring - We have rolled back a release which we believe may have caused this issue as of …

Mar 4, 21:22 UTC
Update - We identified that this issue was caused by a software defect that impacted our automated database maintenance procedures. As an immediate mitigation, our team performed manual database maintenance to stabilize the system and restore normal operations, we can confirm the service continues to operate within normal parameters.
Also as a long term mitigation, we are also releasing additional software changes to correct the underlying issue and prevent this condition from recurring. We will continue monitoring closely as the updates roll out and will provide further updates as appropriate.
Next scheduled update should arrive after March 18th.

Feb 27, …

Mar 3, 17:32 UTC
Resolved - We can confirm that the issue was mitigated at 13:40 UTC on February 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/0D5a700000wQl7YCAS, 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.

Feb 28, 17:43 UTC
Monitoring - We have taken mitigation steps and escalated to our third-party service provider who confirmed the impact …

Feb 27, 19:48 UTC
Resolved - We can confirm that the issue was mitigated at 13:10 UTC on February 27, 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/0D5a700000wQI7YCAS 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.

Feb 27, 15:52 UTC
Update - We are continuing to monitor for any further issues following the implementation of the temporary …

Feb 19, 21:50 UTC
Resolved - We can confirm that the issue was mitigated at ~19:00 UTC on February 19, 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/0D5a700000uxhxXCAQ?language=en_US 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.

Feb 19, 20:22 UTC
Investigating - We are investigating an emerging issue with Content Purge related to 503 error responses to …

Feb 11, 00:13 UTC
Resolved - We can confirm that the issue was mitigated at 23:58 UTC on February 10, 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/0D5a700000tQzoNCAS 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.

Feb 10, 23:48 UTC
Identified - We have identified the cause of the issue, and a fix is being implemented. Customers …

Feb 10, 17:41 UTC
Resolved - We can confirm that the issue was mitigated at 03:22 UTC on 10 February 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/0D5a700000tGYakCAG 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.

Feb 10, 04:27 UTC
Monitoring - We have implemented a fix for this issue as of 03:22 UTC on 10 February …