Histórico de interrupções do Akamai

1. 12 Eost 2026 da 13:02 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. 11 Eost 2026 da 10:11 UTCinvestigating

   Estamos investigando um problema emergente com o Sistema de Provisão de Certificados (SCP) relacionado a atrasos na validação de domínio e/ou incompatibilidades de IU onde as inscrições ativas não exibirão status. Estamos investigando ativamente o problema e forneceremos outra atualização dentro dos próximos 60 minutos. Em breve iremos postar mais detalhes para clientes e parceiros com um login válido do Centro de Controle em https://community.akamai.com/clientes/s/group/0F9000000DFgx/service-incident-notifications. Se você tiver dúvidas ou estiver tendo um impacto devido a este problema, utilize o Centro de Suporte na Comunidade Akamai (https://community.akamai.com/clientes/s/suporte), ou Centro de Controle Akamai, para entrar em contato com o Suporte Técnico Akamai. As informações de contacto estão disponíveis em https://www.akamai.com/us/en/support/.

2. 11 Eost 2026 da 10:51 UTCinvestigating

   Continuamos a investigar esta questão. Os clientes e parceiros podem encontrar mais detalhes sobre a Comunidade Akamai: https://community.akamai.com/clientes/s/feed/0D5a700001NAvXBCA1. Forneceremos uma atualização nos próximos 60 minutos.

3. 11 Eost 2026 da 12:05 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. 12 Eost 2026 da 13:16 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.

Traduzido automaticamente da atualização oficial do incidente.

1. 4 Eost 2026 da 15:23 UTCresolved

   Nós nos tornamos conscientes de um problema com Web Security Analytics relacionado ao HTTP Vazio Aceitar Linguagem e os valores do cabeçalho do Conteúdo que estão sendo registrados. A edição durou entre 11:30 UTC em 3 de agosto de 2026, e 14:00 UTC em 4 de agosto de 2026. Podemos confirmar que a questão está agora resolvida e que o serviço voltou a funcionar normalmente. Clientes e parceiros podem ver detalhes adicionais sobre o incidente fazendo login em: https://community.akamai.com/clientes/s/feed/0D5a700001M5NvWCAV ou contactando o Suporte da Akamai. Pedimos desculpas pelo impacto e agradecemos a sua paciência e apoio contínuo. Estamos empenhados em fazer melhorias contínuas para melhorar os nossos sistemas e evitar a recorrência desta questão.

Traduzido automaticamente da atualização oficial do incidente.

1. 4 Eost 2026 da 07:54 UTCmonitoring

   Nós ficamos cientes de um problema com "Traffic by Hostname" relacionado à disponibilidade de dados de relatórios. A edição durou entre 15:00 UTC em 3 de agosto de 2026 e 00:20 UTC em 4 de agosto de 2026. Implementamos uma correção para esta edição a partir de 00:20 UTC em 4 de agosto de 2026; com base em observações atuais, o serviço está retomando operações normais. Clientes e parceiros podem encontrar mais detalhes sobre a Comunidade Akamai: https://community.akamai.com/clientes/s/feed/0D5a700001M2nELCAZ. Continuaremos a acompanhar para garantir que o impacto tenha sido plenamente atenuado. Pedimos desculpas pelo impacto e agradecemos a sua paciência e apoio contínuo. Estamos empenhados em fazer melhorias contínuas para melhorar os nossos sistemas e evitar a recorrência desta questão.

2. 4 Eost 2026 da 09:14 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. 5 Eost 2026 da 00:05 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. 5 Eost 2026 da 08:59 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. 5 Eost 2026 da 14:33 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.

Traduzido automaticamente da atualização oficial do incidente.

1. 1 Eost 2026 da 10:54 UTCinvestigating

   Estamos investigando um problema emergente com HTTP e HTTPS relacionado à interrupção parcial do serviço com 400 erros. Estamos investigando ativamente o problema e forneceremos outra atualização nos próximos 30 minutos. Em breve iremos postar mais detalhes para clientes e parceiros com um login válido do Centro de Controle em https://community.akamai.com/clientes/s/group/0F9000000DFgx/service-incident-notifications. Se você tiver dúvidas ou estiver tendo um impacto devido a este problema, utilize o Centro de Suporte na Comunidade Akamai (https://community.akamai.com/clientes/s/suporte), ou Centro de Controle Akamai, para entrar em contato com o Suporte Técnico Akamai. As informações de contacto estão disponíveis em https://www.akamai.com/us/en/support/.

2. 1 Eost 2026 da 11:12 UTCinvestigating

   Continuamos a investigar esta questão. Clientes e parceiros podem encontrar mais detalhes sobre a Comunidade Akamai: https://community.akamai.com/clientes/s/feed/0D5a700001LizHpCAJNós forneceremos uma atualização à medida que avançamos.

3. 1 Eost 2026 da 12:14 UTCresolved

   Podemos confirmar que a questão foi atenuada às 09:05 UTC em 1o de agosto de 2026 e que o serviço retomou a operação normal. Clientes e parceiros podem visualizar detalhes adicionais sobre o incidente fazendo login em: https://community.akamai.com/clientes/s/feed/0D5a700001LizHpCAJ ou contactando o Suporte da Akamai. Pedimos desculpas pelo impacto e agradecemos a sua paciência e apoio contínuo. Estamos empenhados em fazer melhorias contínuas para melhorar os nossos sistemas e evitar a recorrência desta questão.

Traduzido automaticamente da atualização oficial do incidente.

1. 29 Gouere 2026 da 14:48 UTCinvestigating

   Estamos investigando um problema emergente com o NetStorage relacionado aos erros 5XX observados devido a uma região de armazenamento offline. Estamos investigando ativamente o problema e forneceremos outra atualização dentro dos próximos 60 minutos. Em breve iremos postar mais detalhes para clientes e parceiros com um login válido do Centro de Controle em https://community.akamai.com/clientes/s/group/0F9000000DFgx/service-incident-notifications. Se você tiver dúvidas ou estiver tendo um impacto devido a este problema, utilize o Centro de Suporte na Comunidade Akamai (https://community.akamai.com/clientes/s/suporte), ou Centro de Controle Akamai, para entrar em contato com o Suporte Técnico Akamai. As informações de contacto estão disponíveis em https://www.akamai.com/us/en/support/.

2. 29 Gouere 2026 da 15:36 UTCinvestigating

   Continuamos a investigar esta questão. Os clientes e parceiros podem encontrar mais detalhes sobre a Comunidade Akamai: https://community.akamai.com/clientes/s/feed/0D5a700001LBrwDCAT. Forneceremos uma atualização nos próximos 60 minutos.

3. 29 Gouere 2026 da 16:28 UTCidentified

   Identificámos a causa da questão e está a ser implementada uma solução. Os clientes e parceiros podem encontrar mais detalhes sobre a Comunidade Akamai: https://community.akamai.com/clientes/s/feed/0D5a700001LBrwDCAT. Forneceremos uma atualização nos próximos 60 minutos.

4. 29 Gouere 2026 da 17:06 UTCresolved

   Podemos confirmar que a questão foi atenuada às 14:21 UTC em 29 de julho de 2026 e o serviço retomou a operação normal. Clientes e parceiros podem ver detalhes adicionais sobre o incidente fazendo login em: https://community.akamai.com/clientes/s/feed/0D5a700001LBrwDCAT, ou contactando o Suporte da Akamai. Pedimos desculpas pelo impacto e agradecemos a sua paciência e apoio contínuo. Estamos empenhados em fazer melhorias contínuas para melhorar os nossos sistemas e evitar a recorrência desta questão.

Traduzido automaticamente da atualização oficial do incidente.

1. 27 Gouere 2026 da 01:46 UTCinvestigating

   Estamos investigando um problema com o Bot Manager relacionado a problemas falsos positivos com disponibilidade. Estamos investigando ativamente o problema e forneceremos outra atualização dentro dos próximos 60 minutos. Em breve iremos postar mais detalhes para clientes e parceiros com um login válido do Centro de Controle em https://community.akamai.com/clientes/s/group/0F9000000DFgx/service-incident-notifications. Se você tiver dúvidas ou estiver tendo um impacto devido a este problema, utilize o Centro de Suporte na Comunidade Akamai (https://community.akamai.com/clientes/s/suporte), ou Centro de Controle Akamai, para entrar em contato com o Suporte Técnico Akamai. As informações de contacto estão disponíveis em https://www.akamai.com/us/en/support/.

2. 27 Gouere 2026 da 02:11 UTCmonitoring

   Implementamos uma correção para esta edição a partir de 01:30 UTC em 27 de julho de 2026; com base nas observações atuais, o serviço está retomando operações normais. Clientes e parceiros podem encontrar mais detalhes sobre a Comunidade Akamai: https://community.akamai.com/clientes/s/feed/0D5a700001Kh1F0CAJ. Continuaremos a acompanhar para garantir que o impacto tenha sido plenamente atenuado.

3. 27 Gouere 2026 da 06:07 UTCresolved

   Podemos confirmar que a questão foi atenuada às 01:30 UTC em 27 de julho de 2026 e o serviço retomou a operação normal. Clientes e parceiros podem ver detalhes adicionais sobre o incidente fazendo login em: https://community.akamai.com/clientes/s/feed/0D5a700001Kh1F0CAJ ou a contactar o Apoio Akamai. Pedimos desculpas pelo impacto e agradecemos a sua paciência e apoio contínuo. Estamos empenhados em fazer melhorias contínuas para melhorar os nossos sistemas e evitar a recorrência desta questão.

Traduzido automaticamente da atualização oficial do incidente.

1. 24 Gouere 2026 da 12:21 UTCinvestigating

   Estamos investigando um problema emergente com rede HTTP e HTTPS relacionado a problemas de latência com erro de 5xx. Estamos investigando ativamente o problema e forneceremos outra atualização nos próximos 30 minutos. Em breve iremos postar mais detalhes para clientes e parceiros com um login válido do Centro de Controle em https://community.akamai.com/clientes/s/group/0F9000000DFgx/service-incident-notifications. Se você tiver dúvidas ou estiver tendo um impacto devido a este problema, utilize o Centro de Suporte na Comunidade Akamai (https://community.akamai.com/clientes/s/suporte), ou Centro de Controle Akamai, para entrar em contato com o Suporte Técnico Akamai. As informações de contacto estão disponíveis em https://www.akamai.com/us/en/support/.

2. 24 Gouere 2026 da 12:40 UTCinvestigating

   Continuamos a trabalhar com o nosso fornecedor de serviços de terceiros para investigar esta questão. Clientes e parceiros podem encontrar mais detalhes sobre a Comunidade Akamai: https://community.akamai.com/clientes/s/feed/0D5a700001KQ2QCA1Nós forneceremos uma atualização à medida que avançamos.

3. 24 Gouere 2026 da 12:56 UTCmonitoring

   O provedor de terceiros implementou uma correção para esta edição a partir de 12:00 UTC em 24 de julho de 2026: com base em observações atuais, o serviço está retomando operações normais. Clientes e parceiros podem encontrar mais detalhes sobre a Comunidade Akamai: https://community.akamai.com/clientes/s/feed/0D5a700001KQ2QCA1Nós continuaremos a monitorar para garantir que o impacto tenha sido totalmente atenuado.

4. 24 Gouere 2026 da 18:45 UTCresolved

   Podemos confirmar que a questão foi atenuada às 12:00 UTC em 24 de julho de 2026 e o serviço retomou a operação normal. Clientes e parceiros podem ver detalhes adicionais sobre o incidente fazendo login em: https://community.akamai.com/clientes/s/feed/0D5a700001KQ2QCA1 ou contactando o Suporte da Akamai. Pedimos desculpas pelo impacto e agradecemos a sua paciência e apoio contínuo. Estamos empenhados em fazer melhorias contínuas para melhorar os nossos sistemas e evitar a recorrência desta questão.

Traduzido automaticamente da atualização oficial do incidente.

1. 19 Gouere 2026 da 07:40 UTCinvestigating

   Estamos investigando um problema com a Edge Delivery, onde os usuários podem ter experimentado erros de entrega e tempo de conexão. A questão não está ocorrendo neste momento. Estamos a investigar activamente a causa e vamos fornecer os detalhes da investigação à medida que avançamos. Em breve iremos postar mais detalhes para clientes e parceiros com um login válido do Centro de Controle em https://community.akamai.com/clientes/s/group/0F9000000DFgx/service-incident-notifications. Se você tiver dúvidas ou estiver tendo um impacto devido a este problema, utilize o Centro de Suporte na Comunidade Akamai (https://community.akamai.com/clientes/s/suporte), ou Centro de Controle Akamai, para entrar em contato com o Suporte Técnico Akamai. As informações de contacto estão disponíveis em https://www.akamai.com/us/en/support/.

2. 19 Gouere 2026 da 11:06 UTCinvestigating

   Continuamos a investigar a causa. Clientes e parceiros podem encontrar mais detalhes sobre a Comunidade Akamai: https://community.akamai.com/clientes/s/feed/0D5a700001JVmHpCAL Apresentaremos uma actualização à medida que avançarmos.

3. 19 Gouere 2026 da 13:58 UTCmonitoring

   O fornecedor de serviços terceirizado identificou a causa do problema e implementou uma correção a partir de 04:10 UTC em 19 de julho de 2026; com base em observações atuais, o serviço está retomando operações normais. Clientes e parceiros podem encontrar mais detalhes sobre a Comunidade Akamai: https://community.akamai.com/clientes/s/feed/0D5a700001JVmHpCAL. Continuaremos a acompanhar para garantir que o impacto tenha sido plenamente atenuado.

4. 20 Gouere 2026 da 14:46 UTCresolved

   Podemos confirmar que a questão foi atenuada às 04:10 UTC em 19 de julho de 2026, e o serviço retomou a operação normal. Clientes e parceiros podem ver detalhes adicionais sobre o incidente fazendo login em: https://community.akamai.com/clientes/s/feed/0D5a700001JVmHpCAL ou contactando o Suporte da Akamai. Pedimos desculpas pelo impacto e agradecemos a sua paciência e apoio contínuo. Estamos empenhados em fazer melhorias contínuas para melhorar os nossos sistemas e evitar a recorrência desta questão.

Traduzido automaticamente da atualização oficial do incidente.

1. 16 Gouere 2026 da 04:21 UTCinvestigating

   Estamos investigando um problema com o relatório de Balanço de Carga de Aplicação (ALB) relacionado à disponibilidade com erros. Estamos investigando ativamente o problema e forneceremos outra atualização dentro dos próximos 60 minutos. Em breve, publicaremos mais detalhes para clientes e parceiros com um login válido do Centro de Controle em https://community.akamai.com/clientes/s/feed/0D5a700001J1h4UCAR. Se você tiver dúvidas ou estiver tendo um impacto devido a este problema, utilize o Centro de Suporte na Comunidade Akamai (https://community.akamai.com/clientes/s/suporte), ou Centro de Controle Akamai, para entrar em contato com o Suporte Técnico Akamai. As informações de contacto estão disponíveis em https://www.akamai.com/us/en/support/.

2. 16 Gouere 2026 da 05:01 UTCinvestigating

   Continuamos a investigar esta questão. Clientes e parceiros podem encontrar mais detalhes sobre a Comunidade Akamai: https://community.akamai.com/clientes/s/feed/0D5a700001J1h4UCAR. Apresentaremos a próxima actualização à medida que avançarmos.

3. 16 Gouere 2026 da 07:27 UTCmonitoring

   Implementamos uma correção para esta edição a partir de 04:36 UTC em 16 de julho de 2026; com base em observações atuais, o serviço está retomando operações normais. Clientes e parceiros podem encontrar mais detalhes sobre a Comunidade Akamai: https://community.akamai.com/clientes/s/feed/0D5a700001J1h4UCAR. Continuaremos a acompanhar para garantir que o impacto tenha sido plenamente atenuado.

4. 17 Gouere 2026 da 04:45 UTCmonitoring

   Não observamos uma recorrência, e o sistema parece estável. Continuamos a monitorizar para garantir que o impacto foi totalmente atenuado. Apresentaremos a próxima actualização à medida que avançarmos.

5. 23 Gouere 2026 da 02:06 UTCresolved

   Podemos confirmar que a questão foi atenuada às 04:36 UTC em 16 de julho de 2026 e o serviço retomou a operação normal. Clientes e parceiros podem visualizar detalhes adicionais sobre o incidente fazendo login em: https://community.akamai.com/clientes/s/feed/0D5a700001J1h4UCAR ou contactando o Suporte da Akamai. Pedimos desculpas pelo impacto e agradecemos a sua paciência e apoio contínuo. Estamos empenhados em fazer melhorias contínuas para melhorar os nossos sistemas e evitar a recorrência desta questão.

Traduzido automaticamente da atualização oficial do incidente.

1. 2 Gouere 2026 da 14:40 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. 2 Gouere 2026 da 15:05 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. 2 Gouere 2026 da 15:34 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. 2 Gouere 2026 da 17:51 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. 2 Gouere 2026 da 21:42 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. 6 Gouere 2026 da 04:11 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. 30 Mezheven 2026 da 21:15 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. 30 Mezheven 2026 da 21:23 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. 30 Mezheven 2026 da 22:02 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. 28 Mezheven 2026 da 14:45 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. 28 Mezheven 2026 da 15:10 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. 28 Mezheven 2026 da 15:57 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. 28 Mezheven 2026 da 17:22 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. 29 Mezheven 2026 da 00:42 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. 29 Mezheven 2026 da 15:42 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. 25 Mezheven 2026 da 18:14 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. 25 Mezheven 2026 da 18:58 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. 25 Mezheven 2026 da 19:54 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. 25 Mezheven 2026 da 21:59 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. 26 Mezheven 2026 da 00:45 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. 26 Mezheven 2026 da 23:35 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. 16 Mezheven 2026 da 15:45 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. 12 Mezheven 2026 da 14:58 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. 10 Mezheven 2026 da 18:38 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. 10 Mezheven 2026 da 18:51 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. 11 Mezheven 2026 da 16:41 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. 6 Mezheven 2026 da 04:29 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. 6 Mezheven 2026 da 07:21 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. 5 Mezheven 2026 da 16:16 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. 8 Mezheven 2026 da 19:56 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. 11 Mezheven 2026 da 18:54 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. 19 Mezheven 2026 da 11:07 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. 27 Mae 2026 da 13:28 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.