Akamai Outage History

We became aware of an issue with a third-party service provider causing performance degradation to Edge Delivery in Asia. The issue lasted between 11:00 UTC on November 21, 2025, and 12:10 UTC on November 21, 2025. The third-party service provider has implemented a fix and, 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/0D5a700000j7RBRCA2 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.

We became aware of an issue in Web Security Analytics regarding errors when loading the application. The issue lasted between 13:25 UTC and 14:10 UTC on November 19, 2025. 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/0D5a700000iqYWyCAM 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.

We became aware of an issue with Compute and Edge Delivery services hosted in India related to connection timeouts and packet loss due to an issue with a third party transit provider. The issue lasted between 13:52 UTC on 08 November, 2025 and 14:53 UTC on 08 November, 2025. 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: 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.

We can confirm that the issue was mitigated at 13:18 on 04 November 2025, 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/0D5a700000gqFY2CAM 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.

We can confirm that the issue was mitigated at approximately 11:45 UTC on November 4, 2025, 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/0D5a700000gpUKaCAM 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.

We became aware of an issue with Content Protector related to availability with Rule ID # 3903402. The issue lasted from around 22:30 UTC on 22 October 2025 to 07:00 UTC on 23 October 2025, and 19:15-20:45 UTC on 27 October 2025. 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/0D5a700000g44I2CAI 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.

We became aware of an issue with the Akamai Control Center related to multiple security reports returning errors. The issue lasted between 7:55 UTC on October 23, 2025, and 8:55 UTC on October 23, 2025. 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/0D5a700000f56BiCAI 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.

Our MFA's SMS message delivery service provider has marked this incident as resolved at 23:08 UTC on October 20, 2025; based on current observations, the service has resumed normal operations.