Historial de interrupciones de Akamai

1. August 12, 2026 at 1:02 PM UTCmonitoring

   We became aware of an issue with Edge Delivery in India related to connectivity issues in the form of latency or connection timeouts that impacted traffic flowing from India to multiple geos. The issue lasted between 11:15 UTC on August 12, 2026, and 11:50 UTC on August 12, 2026. The third-party service provider has implemented a fix and based on current observations, the service is resuming normal operations. Customers and partners can find more details on the Akamai Community. We will continue to monitor to ensure that the impact has been fully mitigated. 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.

1. August 11, 2026 at 10:11 AM UTCinvestigating

   We are investigating an emerging issue with the Certificate Provisioning System (CPS) related to delays in domain validation and/or UI mismatches where active enrollments will display no status. We are actively investigating the issue and will provide another update within the next 60 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/.

2. August 11, 2026 at 10:51 AM UTCinvestigating

   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/0D5a700001NAvXBCA1. We will provide an update within the next 60 minutes.

3. August 11, 2026 at 12:05 PM UTCinvestigating

   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/0D5a700001NAvXBCA1. We will provide an update as we make progress.

4. August 12, 2026 at 1:16 PM UTCinvestigating

   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/0D5a700001NAvXBCA1. We will provide an update as we make progress.

1. August 4, 2026 at 3:23 PM UTCresolved

   Nos dimos cuenta de un problema con Web Security Analytics relacionado con Empty HTTP Accept Language and Content Longitud header values being logged. El tema duró entre las 11:30 UTC el 3 de agosto de 2026 y las 14:00 UTC el 4 de agosto de 2026. Podemos confirmar que la cuestión se resuelve ahora, y el servicio ha reanudado el funcionamiento normal. Los clientes y socios pueden ver detalles adicionales sobre el incidente iniciando sesión en: https://community.akamai.com/customers/s/feed/0D5a700001M5NvWCAV o llegando a Akamai Support. Nos disculpamos por el impacto y gracias por su paciencia y apoyo continuo. Nos comprometemos a hacer mejoras continuas para mejorar nuestros sistemas e impedir que se repita esta cuestión.

Traducido automáticamente desde la actualización oficial del incidente.

1. August 4, 2026 at 7:54 AM UTCmonitoring

   Nos dimos cuenta de un problema con "Traffic by Hostname" relacionado con la disponibilidad de datos. La cuestión duró entre las 15.00 horas UTC el 3 de agosto de 2026 y las 00:20 UTC el 4 de agosto de 2026. Hemos implementado una solución para esta cuestión a partir de las 00:20 UTC el 4 de agosto de 2026; basado en las observaciones actuales, el servicio está resumiendo operaciones normales. Los clientes y socios pueden encontrar más detalles sobre la Comunidad Akamai: https://community.akamai.com/customers/s/feed/0D5a700001M2nELCAZ. Seguiremos vigilando para asegurar que el impacto se haya mitigado completamente. Nos disculpamos por el impacto y gracias por su paciencia y apoyo continuo. Nos comprometemos a hacer mejoras continuas para mejorar nuestros sistemas e impedir que se repita esta cuestión.

2. August 4, 2026 at 9:14 AM UTCmonitoring

   We are continuing to monitor to ensure that the impact has been fully mitigated. Customers and partners can find more details on the Akamai Community: https://community.akamai.com/customers/s/feed/0D5a700001M2nELCAZ. We will provide the next update as we make progress.

3. August 5, 2026 at 12:05 AM UTCmonitoring

   Service remains operational. We are continuing to monitor the environment to ensure performance and stability are maintained.Customers and partners can find more details on the Akamai Community: https://community.akamai.com/customers/s/feed/0D5a700001M2nELCAZ. We will provide the next update as we make progress.

4. August 5, 2026 at 8:59 AM UTCmonitoring

   We are continuing to monitor the issue to ensure performance and stability are maintained. Customers and partners can find more details on the Akamai Community: https://community.akamai.com/customers/s/feed/0D5a700001M2nELCAZ. We will provide the next update as we make progress.

5. August 5, 2026 at 2:33 PM UTCresolved

   We can confirm that the issue was mitigated at 00:20 UTC on August 4, 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/0D5a700001M2nELCAZ 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.

Traducido automáticamente desde la actualización oficial del incidente.

1. August 1, 2026 at 10:54 AM UTCinvestigating

   Estamos investigando un problema emergente con HTTP y HTTPS relacionado con la interrupción parcial del servicio con 400 errores. Estamos investigando activamente el problema y proporcionaremos otra actualización en los próximos 30 minutos. Pronto publicaremos más detalles para clientes y socios con un acceso válido al Centro de Control en https://community.akamai.com/customers/s/group/0F90f000DFgx/service-incident-notifications. Si tiene preguntas o está experimentando un impacto debido a esta cuestión, utilice el Centro de Apoyo en la Comunidad de Akamai (https://community.akamai.com/customers/s/support), o el Centro de Control de Akamai, para ponerse en contacto con Akamai Technical Support. La información de contacto puede consultarse en https://www.akamai.com/us/en/support/.

2. August 1, 2026 at 11:12 AM UTCinvestigating

   Seguimos investigando esta cuestión. Los clientes y socios pueden encontrar más detalles sobre la Comunidad Akamai: https://community.akamai.com/customers/s/feed/0D5a700001LizHpCAJProporcionaremos una actualización a medida que avanzamos.

3. August 1, 2026 at 12:14 PM UTCresolved

   Podemos confirmar que la cuestión fue mitigada a las 09:05 UTC el 1 de agosto de 2026 y el servicio ha reanudado el funcionamiento normal. Los clientes y socios pueden ver detalles adicionales sobre el incidente iniciando sesión en: https://community.akamai.com/customers/s/feed/0D5a700001LizHpCAJ o llegando a Akamai Support. Nos disculpamos por el impacto y gracias por su paciencia y apoyo continuo. Nos comprometemos a hacer mejoras continuas para mejorar nuestros sistemas e impedir que se repita esta cuestión.

Traducido automáticamente desde la actualización oficial del incidente.

1. July 29, 2026 at 2:48 PM UTCinvestigating

   Estamos investigando un problema emergente con NetStorage relacionado con errores observados 5XX debido a una región de almacenamiento offline. Estamos investigando activamente el problema y proporcionaremos otra actualización en los próximos 60 minutos. Pronto publicaremos más detalles para clientes y socios con un acceso válido al Centro de Control en https://community.akamai.com/customers/s/group/0F90f000DFgx/service-incident-notifications. Si tiene preguntas o está experimentando un impacto debido a esta cuestión, utilice el Centro de Apoyo en la Comunidad de Akamai (https://community.akamai.com/customers/s/support), o el Centro de Control de Akamai, para ponerse en contacto con Akamai Technical Support. La información de contacto puede consultarse en https://www.akamai.com/us/en/support/.

2. July 29, 2026 at 3:36 PM UTCinvestigating

   Seguimos investigando esta cuestión. Los clientes y socios pueden encontrar más detalles sobre la Comunidad Akamai: https://community.akamai.com/customers/s/feed/0D5a700001LBrwDCAT. Proporcionaremos una actualización en los próximos 60 minutos.

3. July 29, 2026 at 4:28 PM UTCidentified

   Hemos identificado la causa de la cuestión y se está aplicando una solución. Los clientes y socios pueden encontrar más detalles sobre la Comunidad Akamai: https://community.akamai.com/customers/s/feed/0D5a700001LBrwDCAT. Proporcionaremos una actualización en los próximos 60 minutos.

4. July 29, 2026 at 5:06 PM UTCresolved

   Podemos confirmar que la cuestión fue mitigada a las 14:21 UTC el 29 de julio de 2026 y el servicio ha reanudado el funcionamiento normal. Los clientes y socios pueden ver detalles adicionales sobre el incidente iniciando sesión en: https://community.akamai.com/customers/s/feed/0D5a700001LBrwDCAT, o llegando a Akamai Support. Nos disculpamos por el impacto y gracias por su paciencia y apoyo continuo. Nos comprometemos a hacer mejoras continuas para mejorar nuestros sistemas e impedir que se repita esta cuestión.

Traducido automáticamente desde la actualización oficial del incidente.

1. July 27, 2026 at 1:46 AM UTCinvestigating

   Estamos investigando un problema con Bot Manager relacionado con falsos problemas positivos con disponibilidad. Estamos investigando activamente el problema y proporcionaremos otra actualización en los próximos 60 minutos. Pronto publicaremos más detalles para clientes y socios con un acceso válido al Centro de Control en https://community.akamai.com/customers/s/group/0F90f000DFgx/service-incident-notifications. Si tiene preguntas o está experimentando un impacto debido a esta cuestión, utilice el Centro de Apoyo en la Comunidad de Akamai (https://community.akamai.com/customers/s/support), o el Centro de Control de Akamai, para ponerse en contacto con Akamai Technical Support. La información de contacto puede consultarse en https://www.akamai.com/us/en/support/.

2. July 27, 2026 at 2:11 AM UTCmonitoring

   Hemos implementado una solución para esta cuestión a partir de las 01:30 UTC el 27 de julio de 2026; sobre la base de las observaciones actuales, el servicio está resumiendo operaciones normales. Los clientes y socios pueden encontrar más detalles sobre la Comunidad Akamai: https://community.akamai.com/customers/s/feed/0D5a700001Kh1F0CAJ. Seguiremos vigilando para asegurar que el impacto se haya mitigado completamente.

3. July 27, 2026 at 6:07 AM UTCresolved

   Podemos confirmar que la cuestión fue mitigada a las 01:30 UTC el 27 de julio de 2026 y el servicio ha reanudado el funcionamiento normal. Los clientes y socios pueden ver más detalles sobre el incidente iniciando sesión en: https://community.akamai.com/customers/s/feed/0D5a700001Kh1F0CAJ o llegar a Akamai Support. Nos disculpamos por el impacto y gracias por su paciencia y apoyo continuo. Nos comprometemos a hacer mejoras continuas para mejorar nuestros sistemas e impedir que se repita esta cuestión.

Traducido automáticamente desde la actualización oficial del incidente.

1. July 24, 2026 at 12:21 PM UTCinvestigating

   Estamos investigando un problema emergente con la red HTTP y HTTPS relacionados con problemas de latencia con error 5xx. Estamos investigando activamente el problema y proporcionaremos otra actualización en los próximos 30 minutos. Pronto publicaremos más detalles para clientes y socios con un acceso válido al Centro de Control en https://community.akamai.com/customers/s/group/0F90f000DFgx/service-incident-notifications. Si tiene preguntas o está experimentando un impacto debido a esta cuestión, utilice el Centro de Apoyo en la Comunidad de Akamai (https://community.akamai.com/customers/s/support), o el Centro de Control de Akamai, para ponerse en contacto con Akamai Technical Support. La información de contacto puede consultarse en https://www.akamai.com/us/en/support/.

2. July 24, 2026 at 12:40 PM UTCinvestigating

   Continuamos trabajando con nuestro proveedor de servicios de terceros para investigar esta cuestión. Los clientes y socios pueden encontrar más detalles sobre la Comunidad Akamai: https://community.akamai.com/customers/s/feed/0D5a700001KQ2QQCA1Proporcionaremos una actualización a medida que avanzamos.

3. July 24, 2026 at 12:56 PM UTCmonitoring

   El proveedor de terceros ha aplicado una solución para esta cuestión a las 12:00 UTC el 24 de julio de 2026: sobre la base de las observaciones actuales, el servicio está resumiendo operaciones normales. Los clientes y los socios pueden encontrar más detalles sobre la Comunidad de Akamai: https://community.akamai.com/customers/s/feed/0D5a700001KQ2QQCA1Seguiremos monitoreando para asegurar que el impacto haya sido completamente mitigado.

4. July 24, 2026 at 6:45 PM UTCresolved

   Podemos confirmar que el problema fue mitigado a las 12:00 UTC el 24 de julio de 2026 y el servicio ha reanudado el funcionamiento normal. Los clientes y los socios pueden ver más detalles sobre el incidente iniciando sesión en: https://community.akamai.com/customers/s/feed/0D5a700001KQ2QQCA1 o llegando a Akamai Support. Nos disculpamos por el impacto y gracias por su paciencia y apoyo continuo. Nos comprometemos a hacer mejoras continuas para mejorar nuestros sistemas e impedir que se repita esta cuestión.

Traducido automáticamente desde la actualización oficial del incidente.

1. July 19, 2026 at 7:40 AM UTCinvestigating

   Estamos investigando un problema con Edge Delivery donde los usuarios pueden haber experimentado errores de entrega y tiempo de conexión. La cuestión no está ocurriendo en este momento. Estamos investigando activamente la causa y proporcionaremos los detalles de la investigación mientras avanzamos. Pronto publicaremos más detalles para clientes y socios con un acceso válido al Centro de Control en https://community.akamai.com/customers/s/group/0F90f000DFgx/service-incident-notifications. Si tiene preguntas o está experimentando un impacto debido a esta cuestión, utilice el Centro de Apoyo en la Comunidad de Akamai (https://community.akamai.com/customers/s/support), o el Centro de Control de Akamai, para ponerse en contacto con Akamai Technical Support. La información de contacto puede consultarse en https://www.akamai.com/us/en/support/.

2. July 19, 2026 at 11:06 AM UTCinvestigating

   Continuamos investigando la causa. Los clientes y socios pueden encontrar más detalles sobre la Comunidad Akamai: https://community.akamai.com/customers/s/feed/0D5a700001JVmHpCAL Proporcionaremos una actualización a medida que avancemos.

3. July 19, 2026 at 1:58 PM UTCmonitoring

   El proveedor de servicios de terceros ha identificado la causa del problema e implementado una solución a partir de 04:10 UTC el 19 de julio de 2026; basado en las observaciones actuales, el servicio está resumiendo operaciones normales. Los clientes y socios pueden encontrar más detalles sobre la Comunidad Akamai: https://community.akamai.com/customers/s/feed/0D5a700001JVmHpCAL. Seguiremos vigilando para asegurar que el impacto se haya mitigado completamente.

4. July 20, 2026 at 2:46 PM UTCresolved

   Podemos confirmar que la cuestión fue mitigada a las 04:10 UTC el 19 de julio de 2026, y el servicio ha reanudado el funcionamiento normal. Los clientes y socios pueden ver detalles adicionales sobre el incidente iniciando sesión en: https://community.akamai.com/customers/s/feed/0D5a700001JVmHpCAL o llegando a Akamai Support. Nos disculpamos por el impacto y gracias por su paciencia y apoyo continuo. Nos comprometemos a hacer mejoras continuas para mejorar nuestros sistemas e impedir que se repita esta cuestión.

Traducido automáticamente desde la actualización oficial del incidente.

1. July 16, 2026 at 4:21 AM UTCinvestigating

   Estamos investigando un problema con el balanceador de carga de aplicación (ALB) que informa sobre disponibilidad con errores. Estamos investigando activamente el problema y proporcionaremos otra actualización en los próximos 60 minutos. Pronto publicaremos más detalles para clientes y socios con un acceso válido al Centro de Control en https://community.akamai.com/customers/s/feed/0D5a700001J1h4UCAR. Si tiene preguntas o está experimentando un impacto debido a esta cuestión, utilice el Centro de Apoyo en la Comunidad de Akamai (https://community.akamai.com/customers/s/support), o el Centro de Control de Akamai, para ponerse en contacto con Akamai Technical Support. La información de contacto puede consultarse en https://www.akamai.com/us/en/support/.

2. July 16, 2026 at 5:01 AM UTCinvestigating

   Seguimos investigando esta cuestión. Los clientes y socios pueden encontrar más detalles sobre la Comunidad Akamai: https://community.akamai.com/customers/s/feed/0D5a700001J1h4UCAR. Proporcionaremos la próxima actualización a medida que avancemos.

3. July 16, 2026 at 7:27 AM UTCmonitoring

   Hemos implementado una solución para esta cuestión a partir de las 04:36 UTC el 16 de julio de 2026; sobre la base de las observaciones actuales, el servicio está resumiendo operaciones normales. Los clientes y socios pueden encontrar más detalles sobre la Comunidad Akamai: https://community.akamai.com/customers/s/feed/0D5a700001J1h4UCAR. Seguiremos vigilando para asegurar que el impacto se haya mitigado completamente.

4. July 17, 2026 at 4:45 AM UTCmonitoring

   No observamos una recurrencia, y el sistema se ve estable. Seguimos vigilando para asegurar que el impacto se haya mitigado plenamente. Proporcionaremos la próxima actualización a medida que avancemos.

5. July 23, 2026 at 2:06 AM UTCresolved

   Podemos confirmar que la cuestión fue mitigada a las 04:36 UTC el 16 de julio de 2026 y el servicio ha reanudado el funcionamiento normal. Los clientes y socios pueden ver detalles adicionales sobre el incidente iniciando sesión en: https://community.akamai.com/customers/s/feed/0D5a700001J1h4UCAR o llegando a Akamai Support. Nos disculpamos por el impacto y gracias por su paciencia y apoyo continuo. Nos comprometemos a hacer mejoras continuas para mejorar nuestros sistemas e impedir que se repita esta cuestión.

Traducido automáticamente desde la actualización oficial del incidente.

1. July 2, 2026 at 2:40 PM UTCinvestigating

   We are investigating an emerging issue with Edge Delivery involving timeouts and performance degradation in the Pakistan region. 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/.

2. July 2, 2026 at 3:05 PM UTCinvestigating

   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/0D5a700001GuST3CAN. We will provide an update within the next 30 minutes.

3. July 2, 2026 at 3:34 PM UTCinvestigating

   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/0D5a700001GuST3CAN. We will provide an update as we progress.

4. July 2, 2026 at 5:51 PM UTCidentified

   The issue has been identified as related to a submarine cable issue affecting traffic to/from Pakistan. Customers and partners can find more details on the Akamai Community: https://community.akamai.com/customers/s/feed/0D5a700001GuST3CAN. We will provide an update as we progress.

5. July 2, 2026 at 9:42 PM UTCmonitoring

   We have implemented network changes to route traffic away from the affected areas while the ISP continues to work on the submarine cable issue; based on current observations, the service has resumed normal operations. Customers and partners can find more details on the Akamai Community: https://community.akamai.com/customers/s/feed/0D5a700001GuST3CAN. We will continue to monitor to ensure that the impact has been fully mitigated.

6. July 6, 2026 at 4:11 AM UTCresolved

   We can confirm that the issue was mitigated at 4:20 UTC on July 2, 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.

1. June 30, 2026 at 9:15 PM UTCinvestigating

   We are investigating an emerging issue with Akamai Control Center related to Property Manager issues, where users may experience errors when trying to activate new properties or perform changes to their properties related to EdgeWorkers. 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/feed/0D5a700001GabcKCAR. 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/.

2. June 30, 2026 at 9:23 PM UTCidentified

   We have identified the cause of the issue, and a fix is being implemented. Customers and partners can find more details on the Akamai https://community.akamai.com/customers/s/feed/0D5a700001GabcKCAR. We will provide an update within the next 60 minutes.

3. June 30, 2026 at 10:02 PM UTCresolved

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

1. June 28, 2026 at 2:45 PM UTCinvestigating

   We are investigating an emerging issue with Cloudlets related to issues while activating Application Load Balancing configurations. 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/feed/0D5a700001GB7HRCA1. 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/.

2. June 28, 2026 at 3:10 PM UTCinvestigating

   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/0D5a700001GB7HRCA1. We will provide an update within the next 60 minutes.

3. June 28, 2026 at 3:57 PM UTCinvestigating

   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/0D5a700001GB7HRCA1. We will provide an update within the next 120 minutes.

4. June 28, 2026 at 5:22 PM UTCmonitoring

   We have implemented a fix for this issue as of 16:50 UTC on June 28, 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/0D5a700001GB7HRCA1. We will continue to monitor to ensure that the impact has been fully mitigated

5. June 29, 2026 at 12:42 AM UTCmonitoring

   We are continuing to monitor for any further issues; 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/0D5a700001GB7HRCA1. We will continue to monitor to ensure that the impact has been fully mitigated.

6. June 29, 2026 at 3:42 PM UTCresolved

   We can confirm that the issue was mitigated at 16:50 UTC on June 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/0D5a700001GB7HRCA1 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.

1. June 25, 2026 at 6:14 PM UTCinvestigating

   We are investigating an emerging issue with DataStream related to configuring and editing DataStream configurations with users possibly running into the following errors: "There are no eligible properties available to clone the stream.", "One or more properties are invalid. Provide properties that are authorized to be a part of this stream, and belong to the contract and group ID.". We are actively investigating the issue and will provide another update within the next 60 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/.

2. June 25, 2026 at 6:58 PM UTCinvestigating

   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/0D5a700001FiyHGCAZ. We will provide an update within the next 60 minutes.

3. June 25, 2026 at 7:54 PM UTCinvestigating

   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/0D5a700001FiyHGCAZ. Subsequent updates around mitigation status will be posted as progress is made.

4. June 25, 2026 at 9:59 PM UTCmonitoring

   We have rolled back a release which we believe may have caused this issue as of 20:55 UTC on 25 June 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/0D5a700001FiyHGCAZ. We will continue to monitor to ensure that the impact has been fully mitigated.

5. June 26, 2026 at 12:45 AM UTCmonitoring

   We are actively monitoring the fix for this issue and will share updates on mitigation status as progress continues. Thank you for your patience.

6. June 26, 2026 at 11:35 PM UTCresolved

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

1. June 16, 2026 at 3:45 PM UTCresolved

   We became aware of an issue with HTTP and HTTPS related to latency and performance degradation while accessing the applications. The issue lasted between 13:37 UTC and 14:20 UTC on June 16, 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/0D5a700001E6lLpCAJ 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.

1. June 12, 2026 at 2:58 PM UTCresolved

   We identified an issue with the Datastream service where between 10:00 UTC and 21:00 UTC on June 11, 2026, customers may have experienced degraded fidelity on CDN observability streams. We can confirm that the issue is now mitigated as of 21:00 UTC on June 11, 2026, and no longer occurring. Customers and partners can find more details on the Akamai Community: https://community.akamai.com/customers/s/feed/0D5a700001DVkdgCAD. We apologize for any impact and thank you for your patience and continued support. We are committed to making continuous improvements to make our systems better and prevent recurrence.

1. June 10, 2026 at 6:38 PM UTCinvestigating

   We are investigating an emerging issue with Bot Manager Premier related to some legitimate users utilizing a specific rule to be denied. 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/

2. June 10, 2026 at 6:51 PM UTCmonitoring

   We have implemented a fix for this issue as of 18:41 UTC on June 10, 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/0D5a700001D7uShCAJ. We will continue to monitor to ensure that the impact has been fully mitigated.

3. June 11, 2026 at 4:41 PM UTCresolved

   We can confirm that the issue was mitigated at 18:41 UTC on June 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/0D5a700001D7uShCAJ 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.

1. June 6, 2026 at 4:29 AM UTCinvestigating

   We became aware of an issue with Edge Delivery in Americas Region related to elevated request denials and service degradation between 1:00 UTC and 1:30 UTC on June 6, 2026. We are actively investigating the cause of the service degradation within the affected environment and assessing customer impact. At this time, the issue appears to have stabilized, and we will continue to monitor the platform closely. We will provide additional updates as we make further progress in our investigation. Customers and partners can find more details on the Akamai Community: https://community.akamai.com/customers/s/feed/0D5a700001CQ6lqCAD.

2. June 6, 2026 at 7:21 AM UTCresolved

   We can confirm that the issue was mitigated at 1:30 UTC on June 6, 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/0D5a700001CQ6lqCAD 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.

1. June 5, 2026 at 4:16 PM UTCinvestigating

   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/.

2. June 8, 2026 at 7:56 PM UTCinvestigating

   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.

3. June 11, 2026 at 6:54 PM UTCinvestigating

   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.

4. June 19, 2026 at 11:07 AM UTCresolved

   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.

1. May 27, 2026 at 1:28 PM UTCresolved

   We became aware of an issue with HTTP and HTTPS related to latency while accessing the applications. The issue lasted between 11:18 UTC and 12:22 UTC on May 27, 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/0D5a700001ANLNkCAP 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.