Istoricul incidentelor Akamai

1. 12 august 2026 la 13:02 UTCmonitoring

   Am devenit conștienți de o problemă cu Edge Livrare în India legată de probleme de conectivitate sub formă de latență sau temporizări de conexiune care au afectat traficul care curge din India la mai multe geouri. Problema a durat între orele 12:15 UTC la 12 august 2026 și 11:50 UTC la 12 august 2026. Furnizorul de servicii terţ a implementat un fix şi bazat pe observaţiile actuale, serviciul reia operaţiunile normale. Clienţii şi partenerii pot găsi mai multe detalii despre Comunitatea Akamai. Vom continua să monitorizăm pentru a ne asigura că impactul a fost atenuat pe deplin. Ne cerem scuze pentru impact și vă mulțumim pentru răbdare și sprijin continuu. Ne-am angajat să facem îmbunătățiri continue pentru a îmbunătăți sistemele noastre și pentru a preveni repetarea acestei probleme.

Traducere automată din actualizarea oficială a incidentului.

1. 11 august 2026 la 10:11 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. 11 august 2026 la 10:51 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. 11 august 2026 la 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 august 2026 la 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.

1. 4 august 2026 la 15:23 UTCresolved

   We became aware of an issue with Web Security Analytics related to Empty HTTP Accept Language and Content Length header values being logged. The issue lasted between 11:30 UTC on August 3, 2026, and 14:00 UTC on August 4, 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/0D5a700001M5NvWCAV 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. 4 august 2026 la 07:54 UTCmonitoring

   We became aware of an issue with "Traffic by Hostname" related to reporting data availability. The issue lasted between 15:00 UTC on 3 August 2026 and 00:20 UTC on 4 August 2026. We have implemented a fix for this issue as of 00:20 UTC on 4 August 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/0D5a700001M2nELCAZ. 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.

2. 4 august 2026 la 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 august 2026 la 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 august 2026 la 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 august 2026 la 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.

1. 1 august 2026 la 10:54 UTCinvestigating

   Investigăm o problemă apărută cu HTTP și HTTPS legată de perturbarea parțială a serviciului cu 400 de erori. Investigăm în mod activ problema și vom furniza o altă actualizare în următoarele 30 de minute. În curând vom posta mai multe detalii pentru clienți și parteneri cu un acces valid la Centrul de Control https://community.akamai.com/clienți/s/group/0F90f000000DFgx/service-incident-notificări. Dacă aveţi întrebări sau aveţi un impact din cauza acestei probleme, vă rugăm să utilizaţi Centrul de sprijin al Comunităţii Akamai (https://comunity.akamai.com/clienti/s/support), sau Akamai Control Center, pentru a contacta Akamai Technical Support. Informații de contact sunt disponibile la https://www.akamai.com/us/en/support/.

2. 1 august 2026 la 11:12 UTCinvestigating

   Continuăm să investigăm această problemă. Clienţii şi partenerii pot găsi mai multe detalii despre Comunitatea Akamai: https://comunity.akamai.com/clienţi/s/feed/0D5a70000LizHpCAJVom furniza o actualizare pe măsură ce progresăm.

3. 1 august 2026 la 12:14 UTCresolved

   Putem confirma că problema a fost atenuată la 09:05 UTC la 1 august 2026, iar serviciul a reluat funcționarea normală. Clienții și partenerii pot vizualiza detalii suplimentare despre incident prin logare la: https://comunity.akamai.com/clienți/s/feed/0D5a70000LizHpCAJ sau ajunge la Akamai Support. Ne cerem scuze pentru impact și vă mulțumim pentru răbdare și sprijin continuu. Ne-am angajat să facem îmbunătățiri continue pentru a îmbunătăți sistemele noastre și pentru a preveni repetarea acestei probleme.

Traducere automată din actualizarea oficială a incidentului.

1. 29 iulie 2026 la 14:48 UTCinvestigating

   Investigăm o problemă apărută cu NetStorage legată de erorile observate la 5XX din cauza unei regiuni de stocare offline. Investigăm în mod activ problema și vom oferi o altă actualizare în următoarele 60 de minute. În curând vom posta mai multe detalii pentru clienți și parteneri cu un acces valid la Centrul de Control https://community.akamai.com/clienți/s/group/0F90f000000DFgx/service-incident-notificări. Dacă aveţi întrebări sau aveţi un impact din cauza acestei probleme, vă rugăm să utilizaţi Centrul de sprijin al Comunităţii Akamai (https://comunity.akamai.com/clienti/s/support), sau Akamai Control Center, pentru a contacta Akamai Technical Support. Informații de contact sunt disponibile la https://www.akamai.com/us/en/support/.

2. 29 iulie 2026 la 15:36 UTCinvestigating

   Continuăm să investigăm această problemă. Clienții și partenerii pot găsi mai multe detalii despre comunitatea Akamai: https://comunity.akamai.com/clienți/s/feed/0D5a70000LBrwDCAT. Vom oferi o actualizare în următoarele 60 de minute.

3. 29 iulie 2026 la 16:28 UTCidentified

   Am identificat cauza problemei și se pune în aplicare o soluție. Clienții și partenerii pot găsi mai multe detalii despre comunitatea Akamai: https://comunity.akamai.com/clienți/s/feed/0D5a70000LBrwDCAT. Vom oferi o actualizare în următoarele 60 de minute.

4. 29 iulie 2026 la 17:06 UTCresolved

   Putem confirma că problema a fost atenuată la 14:21 UTC la 29 iulie 2026, iar serviciul a reluat funcționarea normală. Clienții și partenerii pot vizualiza detalii suplimentare despre incident prin autentificarea la: https://community.akamai.com/clienți/s/feed/0D5a70000LBrwDCAT, sau ajungerea la Akamai Support. Ne cerem scuze pentru impact și vă mulțumim pentru răbdare și sprijin continuu. Ne-am angajat să facem îmbunătățiri continue pentru a îmbunătăți sistemele noastre și pentru a preveni repetarea acestei probleme.

Traducere automată din actualizarea oficială a incidentului.

1. 27 iulie 2026 la 01:46 UTCinvestigating

   Investigăm o problemă cu Bot Manager legată de probleme fals pozitive cu disponibilitate. Investigăm în mod activ problema și vom oferi o altă actualizare în următoarele 60 de minute. În curând vom posta mai multe detalii pentru clienți și parteneri cu un acces valid la Centrul de Control https://community.akamai.com/clienți/s/group/0F90f000000DFgx/service-incident-notificări. Dacă aveţi întrebări sau aveţi un impact din cauza acestei probleme, vă rugăm să utilizaţi Centrul de sprijin al Comunităţii Akamai (https://comunity.akamai.com/clienti/s/support), sau Akamai Control Center, pentru a contacta Akamai Technical Support. Informații de contact sunt disponibile la https://www.akamai.com/us/en/support/.

2. 27 iulie 2026 la 02:11 UTCmonitoring

   Am implementat un fix pentru această problemă la data de 01:30 UTC la 27 iulie 2026; pe baza observațiilor actuale, serviciul reia operațiunile normale. Clienţii şi partenerii pot găsi mai multe detalii despre Comunitatea Akamai: https://comunity.akamai.com/clienti/s/feed/0D5a700001Kh1F0CAJ. Vom continua să monitorizăm pentru a ne asigura că impactul a fost atenuat pe deplin.

3. 27 iulie 2026 la 06:07 UTCresolved

   Putem confirma că problema a fost atenuată la 01:30 UTC la 27 iulie 2026, iar serviciul a reluat funcționarea normală. Clienții și partenerii pot vizualiza detalii suplimentare despre incident prin autentificarea la: https://comunity.akamai.com/clienți/s/feed/0D5a700001Kh1F0CAJ sau ajunge la Akamai Support. Ne cerem scuze pentru impact și vă mulțumim pentru răbdare și sprijin continuu. Ne-am angajat să facem îmbunătățiri continue pentru a îmbunătăți sistemele noastre și pentru a preveni repetarea acestei probleme.

Traducere automată din actualizarea oficială a incidentului.

1. 24 iulie 2026 la 12:21 UTCinvestigating

   Investigăm o problemă apărută cu reţeaua HTTP şi HTTPS legată de probleme de latenţă cu eroare 5xx. Investigăm în mod activ problema și vom furniza o altă actualizare în următoarele 30 de minute. În curând vom posta mai multe detalii pentru clienți și parteneri cu un acces valid la Centrul de Control https://community.akamai.com/clienți/s/group/0F90f000000DFgx/service-incident-notificări. Dacă aveţi întrebări sau aveţi un impact din cauza acestei probleme, vă rugăm să utilizaţi Centrul de sprijin al Comunităţii Akamai (https://comunity.akamai.com/clienti/s/support), sau Akamai Control Center, pentru a contacta Akamai Technical Support. Informații de contact sunt disponibile la https://www.akamai.com/us/en/support/.

2. 24 iulie 2026 la 12:40 UTCinvestigating

   Continuăm să lucrăm cu furnizorul nostru terţ de servicii pentru a investiga această problemă. Clienţii şi partenerii pot găsi mai multe detalii despre Comunitatea Akamai: https://comunity.akamai.com/clienti/s/feed/0D5a700001KQ2QCA1Vom furniza o actualizare pe măsură ce progresăm.

3. 24 iulie 2026 la 12:56 UTCmonitoring

   Furnizorul terţ a implementat un fix pentru această problemă la ora 12:00 UTC la 24 iulie 2026: pe baza observaţiilor actuale, serviciul reia operaţiunile normale. Clienții și partenerii pot găsi mai multe detalii cu privire la Comunitatea Akamai: https://comunity.akamai.com/clienți/s/feed/0D5a700001KQ2QQCA1Vom continua să monitorizăm pentru a ne asigura că impactul a fost atenuat pe deplin.

4. 24 iulie 2026 la 18:45 UTCresolved

   Putem confirma că problema a fost atenuată la ora 12:00 UTC pe 24 iulie 2026, iar serviciul a reluat funcționarea normală. Clienții și partenerii pot vizualiza detalii suplimentare cu privire la incident prin logare la: https://community.akamai.com/clienți/s/feed/0D5a700001KQ2QCA1 sau ajungând la Akamai Support. Ne cerem scuze pentru impact și vă mulțumim pentru răbdare și sprijin continuu. Ne-am angajat să facem îmbunătățiri continue pentru a îmbunătăți sistemele noastre și pentru a preveni repetarea acestei probleme.

Traducere automată din actualizarea oficială a incidentului.

1. 19 iulie 2026 la 07:40 UTCinvestigating

   Investigăm o problemă cu Edge Livrare în cazul în care utilizatorii au experimentat erori de livrare și timp de conectare. Problema nu are loc în acest moment. Investigăm în mod activ cauza și vom furniza detaliile anchetei pe măsură ce progresăm. În curând vom posta mai multe detalii pentru clienți și parteneri cu un acces valid la Centrul de Control https://community.akamai.com/clienți/s/group/0F90f000000DFgx/service-incident-notificări. Dacă aveţi întrebări sau aveţi un impact din cauza acestei probleme, vă rugăm să utilizaţi Centrul de sprijin al Comunităţii Akamai (https://comunity.akamai.com/clienti/s/support), sau Akamai Control Center, pentru a contacta Akamai Technical Support. Informații de contact sunt disponibile la https://www.akamai.com/us/en/support/.

2. 19 iulie 2026 la 11:06 UTCinvestigating

   Continuăm să investigăm cauza. Clienții și partenerii pot găsi mai multe detalii despre comunitatea Akamai: https://comunity.akamai.com/clienți/s/feed/0D5a700001JVmHpCAL Vom oferi o actualizare în timp ce facem progrese.

3. 19 iulie 2026 la 13:58 UTCmonitoring

   Furnizorul de servicii terţ a identificat cauza problemei şi a pus în aplicare un fix la data de 04:10 UTC la 19 iulie 2026; pe baza observaţiilor actuale, serviciul reia operaţiunile normale. Clienții și partenerii pot găsi mai multe detalii despre comunitatea Akamai: https://comunity.akamai.com/clienți/s/feed/0D5a700001JVmHpCAL. Vom continua să monitorizăm pentru a ne asigura că impactul a fost atenuat pe deplin.

4. 20 iulie 2026 la 14:46 UTCresolved

   Putem confirma că problema a fost atenuată la 04:10 UTC la 19 iulie 2026, iar serviciul a reluat funcționarea normală. Clienții și partenerii pot vizualiza detalii suplimentare despre incident prin logare la: https://community.akamai.com/clienți/s/feed/0D5a700001JVmHpCAL sau ajunge la Akamai Support. Ne cerem scuze pentru impact și vă mulțumim pentru răbdare și sprijin continuu. Ne-am angajat să facem îmbunătățiri continue pentru a îmbunătăți sistemele noastre și pentru a preveni repetarea acestei probleme.

Traducere automată din actualizarea oficială a incidentului.

1. 16 iulie 2026 la 04:21 UTCinvestigating

   Investigăm o problemă cu raportarea "Aplication Load Balancer" (ALB) referitoare la disponibilitatea cu erori. Investigăm în mod activ problema și vom oferi o altă actualizare în următoarele 60 de minute. În curând vom posta mai multe detalii pentru clienți și parteneri cu un acces valid la Centrul de Control https://community.akamai.com/clienți/s/feed/0D5a700001J1h4UCAR. Dacă aveţi întrebări sau aveţi un impact din cauza acestei probleme, vă rugăm să utilizaţi Centrul de sprijin al Comunităţii Akamai (https://comunity.akamai.com/clienti/s/support), sau Akamai Control Center, pentru a contacta Akamai Technical Support. Informații de contact sunt disponibile la https://www.akamai.com/us/en/support/.

2. 16 iulie 2026 la 05:01 UTCinvestigating

   Continuăm să investigăm această problemă. Clienţii şi partenerii pot găsi mai multe detalii despre Comunitatea Akamai: https://community.akamai.com/clienti/s/feed/0D5a70000J1h4UCAR. Vom furniza următoarea actualizare pe măsură ce facem progrese.

3. 16 iulie 2026 la 07:27 UTCmonitoring

   Am implementat un fix pentru această problemă la data de 04:36 UTC la 16 iulie 2026; pe baza observațiilor actuale, serviciul reia operațiunile normale. Clienţii şi partenerii pot găsi mai multe detalii despre Comunitatea Akamai: https://community.akamai.com/clienti/s/feed/0D5a70000J1h4UCAR. Vom continua să monitorizăm pentru a ne asigura că impactul a fost atenuat pe deplin.

4. 17 iulie 2026 la 04:45 UTCmonitoring

   Nu am observat o recidivă, iar sistemul pare stabil. Continuăm să monitorizăm pentru a ne asigura că impactul a fost atenuat pe deplin. Vom furniza următoarea actualizare pe măsură ce facem progrese.

5. 23 iulie 2026 la 02:06 UTCresolved

   Putem confirma că problema a fost atenuată la 04:36 UTC la 16 iulie 2026, iar serviciul a reluat funcționarea normală. Clienții și partenerii pot vizualiza detalii suplimentare despre incident prin logare la: https://community.akamai.com/clienți/s/feed/0D5a700001J1h4UCAR sau ajungând la Akamai Support. Ne cerem scuze pentru impact și vă mulțumim pentru răbdare și sprijin continuu. Ne-am angajat să facem îmbunătățiri continue pentru a îmbunătăți sistemele noastre și pentru a preveni repetarea acestei probleme.

Traducere automată din actualizarea oficială a incidentului.

1. 2 iulie 2026 la 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 iulie 2026 la 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 iulie 2026 la 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 iulie 2026 la 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 iulie 2026 la 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 iulie 2026 la 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 iunie 2026 la 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 iunie 2026 la 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 iunie 2026 la 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 iunie 2026 la 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 iunie 2026 la 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 iunie 2026 la 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 iunie 2026 la 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 iunie 2026 la 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 iunie 2026 la 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 iunie 2026 la 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 iunie 2026 la 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 iunie 2026 la 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 iunie 2026 la 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 iunie 2026 la 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 iunie 2026 la 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 iunie 2026 la 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 iunie 2026 la 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 iunie 2026 la 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 iunie 2026 la 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 iunie 2026 la 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 iunie 2026 la 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 iunie 2026 la 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 iunie 2026 la 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 iunie 2026 la 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 iunie 2026 la 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 iunie 2026 la 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 mai 2026 la 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.