Akamai driftsforstyrrelser

1. 12. august 2026 kl. 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. august 2026 kl. 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 kl. 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 kl. 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 kl. 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 kl. 15.23 UTCresolved

   Vi blev opmærksomme på et problem med Web Security Analytics relateret til Tom HTTP Accept Sprog og indhold Længde header værdier bliver logget. Spørgsmålet varede mellem 11: 30 UTC den 3. august 2026 og 14: 00 UTC den 4. august 2026. Vi kan bekræfte, at spørgsmålet nu er løst, og tjenesten har genoptaget normal drift. Kunder og partnere kan se yderligere oplysninger om hændelsen ved at logge ind på: https: / / community.akamai.com / kunder / s / feed / 0D5a700001M5NvWCAV eller nå ud til Akamai Support. Vi undskylder for virkningen og takker dig for din tålmodighed og fortsatte støtte. Vi er forpligtet til løbende at forbedre vores systemer og forhindre en gentagelse af dette spørgsmål.

Automatisk oversat fra den officielle hændelsesopdatering.

1. 4. august 2026 kl. 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 kl. 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 kl. 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 kl. 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 kl. 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 kl. 10.54 UTCinvestigating

   Vi undersøger et nyt problem med HTTP og HTTPS relateret til delvis afbrydelse af tjenesten med 400 fejl. Vi er aktivt i gang med at undersøge spørgsmålet og vil levere endnu en opdatering inden for de næste 30 minutter. Vi vil snart være udstationering flere detaljer for kunder og partnere med en gyldig Control Center login på https: / / community.akamai.com / kunder / s / group / 0F90f0000DFgx / service-incident- notifikationer. Hvis du har spørgsmål eller oplever en indvirkning på grund af dette problem, bedes du bruge Support Center på Akamai Community (https: / / community.akamai.com / kunder / s / support), eller Akamai Control Center, til at kontakte Akamai Technical Support. Kontaktoplysninger findes på https: / / www.akamai.com / us / en / support /.

2. 1. august 2026 kl. 11.12 UTCinvestigating

   Vi fortsætter med at undersøge dette spørgsmål. Kunder og partnere kan finde flere oplysninger om Akamai-fællesskabet: https: / / community.akamai.com / customer / s / feed / 0D5a700001LizHpCAJVi vil levere en opdatering, efterhånden som vi gør fremskridt.

3. 1. august 2026 kl. 12.14 UTCresolved

   Vi kan bekræfte, at spørgsmålet blev afbødet kl 09: 05 UTC den 1. august 2026 og tjenesten har genoptaget normal drift. Kunder og partnere kan se yderligere oplysninger om hændelsen ved at logge ind på: https: / / community.akamai.com / kunder / s / feed / 0D5a700001LizHpCAJ eller nå ud til Akamai Support. Vi undskylder for virkningen og takker dig for din tålmodighed og fortsatte støtte. Vi er forpligtet til løbende at forbedre vores systemer og forhindre en gentagelse af dette spørgsmål.

Automatisk oversat fra den officielle hændelsesopdatering.

1. 29. juli 2026 kl. 14.48 UTCinvestigating

   Vi undersøger et nyt problem med NetStorage relateret til observerede 5XX fejl på grund af en offline lagerregion. Vi er aktivt i gang med at undersøge spørgsmålet og vil levere endnu en opdatering inden for de næste 60 minutter. Vi vil snart være udstationering flere detaljer for kunder og partnere med en gyldig Control Center login på https: / / community.akamai.com / kunder / s / group / 0F90f0000DFgx / service-incident- notifikationer. Hvis du har spørgsmål eller oplever en indvirkning på grund af dette problem, bedes du bruge Support Center på Akamai Community (https: / / community.akamai.com / kunder / s / support), eller Akamai Control Center, til at kontakte Akamai Technical Support. Kontaktoplysninger findes på https: / / www.akamai.com / us / en / support /.

2. 29. juli 2026 kl. 15.36 UTCinvestigating

   Vi fortsætter med at undersøge dette spørgsmål. http: / / community.akamai.com / cunders / s / feed / 0D5a700001LBrwDCAT. Vi vil levere en opdatering inden for de næste 60 minutter.

3. 29. juli 2026 kl. 16.28 UTCidentified

   Vi har identificeret årsagen til problemet, og der gennemføres et fix. http: / / community.akamai.com / cunders / s / feed / 0D5a700001LBrwDCAT. Vi vil levere en opdatering inden for de næste 60 minutter.

4. 29. juli 2026 kl. 17.06 UTCresolved

   Vi kan bekræfte, at spørgsmålet blev afbødet kl. 14.21 UTC den 29. juli 2026, og at tjenesten har genoptaget normal drift. Kunder og partnere kan se yderligere oplysninger om hændelsen ved at logge ind på: https: / / community.akamai.com / kunder / s / feed / 0D5a700001LBrwDCAT, eller nå ud til Akamai Support. Vi undskylder for virkningen og takker dig for din tålmodighed og fortsatte støtte. Vi er forpligtet til løbende at forbedre vores systemer og forhindre en gentagelse af dette spørgsmål.

Automatisk oversat fra den officielle hændelsesopdatering.

1. 27. juli 2026 kl. 01.46 UTCinvestigating

   Vi undersøger et problem med Bot Manager relateret til falske positive problemer med tilgængelighed. Vi er aktivt i gang med at undersøge spørgsmålet og vil levere endnu en opdatering inden for de næste 60 minutter. Vi vil snart være udstationering flere detaljer for kunder og partnere med en gyldig Control Center login på https: / / community.akamai.com / kunder / s / group / 0F90f0000DFgx / service-incident- notifikationer. Hvis du har spørgsmål eller oplever en indvirkning på grund af dette problem, bedes du bruge Support Center på Akamai Community (https: / / community.akamai.com / kunder / s / support), eller Akamai Control Center, til at kontakte Akamai Technical Support. Kontaktoplysninger findes på https: / / www.akamai.com / us / en / support /.

2. 27. juli 2026 kl. 02.11 UTCmonitoring

   Vi har implementeret en rettelse for dette problem fra 01: 30 UTC den 27 juli 2026; baseret på aktuelle observationer, tjenesten er ved at genoptage normale operationer. http: / / community.akamai.com / customer / s / feed / 0D5a700001KH1F0CAJ. Vi vil fortsat overvåge, at virkningen er blevet fuldt afbødet.

3. 27. juli 2026 kl. 06.07 UTCresolved

   Vi kan bekræfte, at spørgsmålet blev afbødet kl. 01: 30 UTC den 27. juli 2026, og at tjenesten er genoptaget normal drift. Kunder og partnere kan se yderligere oplysninger om hændelsen ved at logge ind på: https: / / community.akamai.com / kunder / s / feed / 0D5a700001KH1F0CAJ eller når Akamai Support. Vi undskylder for virkningen og takker dig for din tålmodighed og fortsatte støtte. Vi er forpligtet til løbende at forbedre vores systemer og forhindre en gentagelse af dette spørgsmål.

Automatisk oversat fra den officielle hændelsesopdatering.

1. 24. juli 2026 kl. 12.21 UTCinvestigating

   Vi undersøger et nyt problem med HTTP og HTTPS netværk relateret til latency problemer med 5xx fejl. Vi er aktivt i gang med at undersøge spørgsmålet og vil levere endnu en opdatering inden for de næste 30 minutter. Vi vil snart være udstationering flere detaljer for kunder og partnere med en gyldig Control Center login på https: / / community.akamai.com / kunder / s / group / 0F90f0000DFgx / service-incident- notifikationer. Hvis du har spørgsmål eller oplever en indvirkning på grund af dette problem, bedes du bruge Support Center på Akamai Community (https: / / community.akamai.com / kunder / s / support), eller Akamai Control Center, til at kontakte Akamai Technical Support. Kontaktoplysninger findes på https: / / www.akamai.com / us / en / support /.

2. 24. juli 2026 kl. 12.40 UTCinvestigating

   Vi fortsætter med at arbejde med vores tredjeparts tjenesteudbyder for at undersøge dette spørgsmål. Kunder og partnere kan finde flere oplysninger om Akamai-fællesskabet: https: / / community.akamai.com / kunder / s / feed / 0D5a700001KQ2QQCA1Vi vil levere en opdatering, efterhånden som vi gør fremskridt.

3. 24. juli 2026 kl. 12.56 UTCmonitoring

   Den tredje part udbyder har gennemført en rettelse for dette spørgsmål fra 12: 00 UTC den 24 juli 2026: baseret på aktuelle observationer, tjenesten er at genoptage normale operationer. Kunder og partnere kan finde flere oplysninger om Akamai-fællesskabet: https: / / community.akamai.com / customer / s / feed / 0D5a700001KQ2QQCA1Vi vil fortsat overvåge for at sikre, at virkningen er fuldt afbødet.

4. 24. juli 2026 kl. 18.45 UTCresolved

   Vi kan bekræfte, at spørgsmålet blev afbødet kl 12: 00 UTC den 24 juli 2026 og tjenesten har genoptaget normal drift. Kunder og partnere kan se yderligere oplysninger om hændelsen ved at logge ind på: https: / / community.akamai.com / kunder / s / feed / 0D5a700001KQ2QQCA1 eller nå ud til Akamai Support. Vi undskylder for virkningen og takker dig for din tålmodighed og fortsatte støtte. Vi er forpligtet til løbende at forbedre vores systemer og forhindre en gentagelse af dette spørgsmål.

Automatisk oversat fra den officielle hændelsesopdatering.

1. 19. juli 2026 kl. 07.40 UTCinvestigating

   Vi undersøger et problem med Edge Levering, hvor brugerne kan have oplevet leveringsfejl og tilslutningstid outs. Spørgsmålet opstår ikke på nuværende tidspunkt. Vi undersøger sagen aktivt og vil give detaljerne i undersøgelsen, når vi gør fremskridt. Vi vil snart være udstationering flere detaljer for kunder og partnere med en gyldig Control Center login på https: / / community.akamai.com / kunder / s / group / 0F90f0000DFgx / service-incident- notifikationer. Hvis du har spørgsmål eller oplever en indvirkning på grund af dette problem, bedes du bruge Support Center på Akamai Community (https: / / community.akamai.com / kunder / s / support), eller Akamai Control Center, til at kontakte Akamai Technical Support. Kontaktoplysninger findes på https: / / www.akamai.com / us / en / support /.

2. 19. juli 2026 kl. 11.06 UTCinvestigating

   Vi fortsætter med at undersøge sagen. Kunder og partnere kan finde flere oplysninger om Akamai-fællesskabet: https: / / community.akamai.com / kunder / s / feed / 0D5a700001JVmHpCAL Vi vil levere en opdatering, når vi gør fremskridt.

3. 19. juli 2026 kl. 13.58 UTCmonitoring

   Den tredje part tjenesteudbyder har identificeret årsagen til problemet og gennemført et fix som 04: 10 UTC den juli 19, 2026; baseret på aktuelle observationer, tjenesten er ved at genoptage normale operationer. Kunder og partnere kan finde flere oplysninger om Akamai-fællesskabet: https: / / community.akamai.com / customer / s / feed / 0D5a700001JVmHpCAL. Vi vil fortsat overvåge, at virkningen er blevet fuldt afbødet.

4. 20. juli 2026 kl. 14.46 UTCresolved

   Vi kan bekræfte, at spørgsmålet blev afbødet kl. 04: 10 UTC den 19. juli 2026, og tjenesten har genoptaget normal drift. Kunder og partnere kan se yderligere oplysninger om hændelsen ved at logge ind på: https: / / community.akamai.com / kunder / s / feed / 0D5a700001JVmHpCAL eller nå ud til Akamai Support. Vi undskylder for virkningen og takker dig for din tålmodighed og fortsatte støtte. Vi er forpligtet til løbende at forbedre vores systemer og forhindre en gentagelse af dette spørgsmål.

Automatisk oversat fra den officielle hændelsesopdatering.

1. 16. juli 2026 kl. 04.21 UTCinvestigating

   Vi undersøger et problem med Application Load Balancer (ALB) rapportering relateret til tilgængelighed med fejl. Vi er aktivt i gang med at undersøge spørgsmålet og vil levere endnu en opdatering inden for de næste 60 minutter. Vi vil snart være udstationering flere detaljer for kunder og partnere med en gyldig Control Center login på https: / / community.akamai.com / kunder / s / feed / 0D5a700001J1h4UCAR. Hvis du har spørgsmål eller oplever en indvirkning på grund af dette problem, bedes du bruge Support Center på Akamai Community (https: / / community.akamai.com / kunder / s / support), eller Akamai Control Center, til at kontakte Akamai Technical Support. Kontaktoplysninger findes på https: / / www.akamai.com / us / en / support /.

2. 16. juli 2026 kl. 05.01 UTCinvestigating

   Vi fortsætter med at undersøge dette spørgsmål. http: / / community.akamai.com / customer / s / feed / 0D5a700001J1h4UCAR. Vi vil levere den næste opdatering, når vi gør fremskridt.

3. 16. juli 2026 kl. 07.27 UTCmonitoring

   Vi har implementeret en rettelse til dette spørgsmål fra 04: 36 UTC den 16 juli 2026; baseret på aktuelle observationer, tjenesten er ved at genoptage normale operationer. http: / / community.akamai.com / customer / s / feed / 0D5a700001J1h4UCAR. Vi vil fortsat overvåge, at virkningen er blevet fuldt afbødet.

4. 17. juli 2026 kl. 04.45 UTCmonitoring

   Vi så ikke en gentagelse, og systemet ser stabilt ud. Vi fortsætter med at overvåge for at sikre, at virkningen er blevet fuldt afbødet. Vi vil levere den næste opdatering, når vi gør fremskridt.

5. 23. juli 2026 kl. 02.06 UTCresolved

   Vi kan bekræfte, at spørgsmålet blev afbødet kl 04: 36 UTC den 16 juli 2026 og tjenesten er genoptaget normal drift. Kunder og partnere kan se yderligere oplysninger om hændelsen ved at logge ind på: https: / / community.akamai.com / kunder / s / feed / 0D5a700001J1h4UCAR eller nå ud til Akamai Support. Vi undskylder for virkningen og takker dig for din tålmodighed og fortsatte støtte. Vi er forpligtet til løbende at forbedre vores systemer og forhindre en gentagelse af dette spørgsmål.

Automatisk oversat fra den officielle hændelsesopdatering.

1. 2. juli 2026 kl. 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. juli 2026 kl. 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. juli 2026 kl. 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. juli 2026 kl. 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. juli 2026 kl. 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. juli 2026 kl. 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. juni 2026 kl. 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. juni 2026 kl. 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. juni 2026 kl. 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. juni 2026 kl. 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. juni 2026 kl. 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. juni 2026 kl. 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. juni 2026 kl. 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. juni 2026 kl. 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. juni 2026 kl. 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. juni 2026 kl. 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. juni 2026 kl. 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. juni 2026 kl. 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. juni 2026 kl. 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. juni 2026 kl. 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. juni 2026 kl. 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. juni 2026 kl. 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. juni 2026 kl. 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. juni 2026 kl. 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. juni 2026 kl. 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. juni 2026 kl. 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. juni 2026 kl. 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. juni 2026 kl. 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. juni 2026 kl. 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. juni 2026 kl. 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. juni 2026 kl. 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. juni 2026 kl. 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. maj 2026 kl. 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.