- Detected by Pingoru
- Apr 30, 2026, 06:41 PM UTC
- Resolved
- Apr 30, 2026, 08:00 PM UTC
- Duration
- 1h 18m
Affected: Bot Management
Timeline · 3 updates
-
investigating Apr 30, 2026, 06:41 PM UTC
We are investigating an emerging issue with Bot Manager related to elevated false positives leading to denied legitimate traffic for end users. 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/.
-
monitoring Apr 30, 2026, 07:02 PM UTC
We have implemented a fix for Bot Manager which addresses the issue we believe may have caused the elevated false positives as of 19:00 UTC on April 30, 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/0D5a70000168PJsCAM. We will continue to monitor to ensure that the impact has been fully mitigated.
-
resolved Apr 30, 2026, 08:00 PM UTC
We can confirm that the issue was mitigated at 19:00 UTC on April 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/0D5a70000168PJsCAM, 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.
Read the full incident report →
- Detected by Pingoru
- Apr 28, 2026, 03:40 PM UTC
- Resolved
- Apr 28, 2026, 11:37 PM UTC
- Duration
- 7h 57m
Affected: Edge Delivery
Timeline · 3 updates
-
investigating Apr 28, 2026, 03:40 PM UTC
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/.
-
investigating Apr 28, 2026, 04:02 PM UTC
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.
-
resolved Apr 28, 2026, 11:37 PM UTC
We can confirm that the issue was mitigated at 16:20 UTC on April 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/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.
Read the full incident report →
- Detected by Pingoru
- Apr 28, 2026, 02:50 AM UTC
- Resolved
- Apr 28, 2026, 05:02 PM UTC
- Duration
- 14h 12m
Affected: Reporting
Timeline · 6 updates
-
investigating Apr 28, 2026, 02:50 AM UTC
We have identified an issue with Traffic Reports where users may stop seeing data for "Traffic by Hostname" post 23:00 UTC on April 27, 2026. We are actively working with the appropriate Subject Matter Experts to mitigate the issue. We apologize for the impact. We will provide an update in 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/.
-
investigating Apr 28, 2026, 03:41 AM UTC
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/0D5a7000015dBomCAE. We will provide an update within the next 60 minutes.
-
investigating Apr 28, 2026, 04:38 AM UTC
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/0D5a7000015dBomCAE. We will provide an update within the next 60 minutes.
-
investigating Apr 28, 2026, 05:33 AM UTC
We are continuing to investigate this issue and our SMEs have determined the potential cause. Customers and partners can find more details on the Akamai Community: https://community.akamai.com/customers/s/feed/0D5a7000015dBomCAEWe will provide another update as we make progress.
-
monitoring Apr 28, 2026, 07:18 AM UTC
The delay in reports is determined to be due to a runtime memory issue. This has been addressed at around 4:30 UTC on April 28, 2026. Customers and partners can find more details on the Akamai Community:https://community.akamai.com/customers/s/feed/0D5a7000015dBomCAE . We will continue to monitor to ensure that the impact has been fully mitigated.
-
resolved Apr 28, 2026, 05:02 PM UTC
We can confirm that the issue was mitigated at 13:30 UTC on April 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/0D5a7000015dBomCAE 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.
Read the full incident report →
- Detected by Pingoru
- Apr 27, 2026, 03:20 AM UTC
- Resolved
- Apr 27, 2026, 01:27 PM UTC
- Duration
- 10h 6m
Affected: ETP/SIA: Web Proxy
Timeline · 4 updates
-
investigating Apr 27, 2026, 03:20 AM UTC
We are investigating an issue with Secure Internet Access related to access issues with certificate errors. 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 the Akamai Control Center to contact Akamai Technical Support. Contact information is available at https://www.akamai.com/us/en/support/.
-
investigating Apr 27, 2026, 03:58 AM UTC
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/0D5a7000015Qwi8CAC. We will provide the next update as we make progress.
-
monitoring Apr 27, 2026, 05:44 AM UTC
We have implemented a fix for this issue as of 05:26 UTC on 27 April 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/0D5a7000015Qwi8CAC. We will continue to monitor to ensure that the impact has been fully mitigated.
-
resolved Apr 27, 2026, 01:27 PM UTC
We can confirm that the issue was mitigated at 05:26 UTC on 27 April, 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/0D5a7000015Qwi8CAC 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.
Read the full incident report →
- Detected by Pingoru
- Apr 24, 2026, 08:07 PM UTC
- Resolved
- Apr 24, 2026, 11:52 PM UTC
- Duration
- 3h 44m
Affected: TrafficPeak
Timeline · 6 updates
-
investigating Apr 24, 2026, 08:07 PM UTC
We are investigating an emerging issue with TrafficPeak related to timeout errors experienced across panels. 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/.
-
identified Apr 24, 2026, 08:34 PM UTC
We have identified a potential cause of the issue, and a fix is being implemented. Customers and partners can find more details on the Akamai Community: https://community.akamai.com/customers/s/feed/0D5a7000015H7xxCAC?language=en_US. We will provide an update within the next 60 minutes.
-
identified Apr 24, 2026, 09:30 PM UTC
We are continuing work to apply the identified fix. Customers and partners can find more details on the Akamai Community: https://community.akamai.com/customers/s/feed/0D5a7000015H7xxCAC?language=en_US. We will provide an update within the next 60 minutes.
-
identified Apr 24, 2026, 10:06 PM UTC
We are continuing work to apply the identified fix. Customers and partners can find more details on the Akamai Community: https://community.akamai.com/customers/s/feed/0D5a7000015H7xxCAC?language=en_US. We will provide an update within the next 60 minutes.
-
identified Apr 24, 2026, 11:07 PM UTC
We are continuing work to apply the identified fix. We will provide an update within the next 60 minutes.
-
resolved Apr 24, 2026, 11:52 PM UTC
We can confirm that the issue was mitigated at 23:36 UTC on April 24, 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/0D5a7000015H7xxCAC?language=en_US 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.
Read the full incident report →
- Detected by Pingoru
- Apr 23, 2026, 02:11 PM UTC
- Resolved
- Apr 28, 2026, 05:39 PM UTC
- Duration
- 5d 3h
Affected: Web Security Analytics
Timeline · 6 updates
-
investigating Apr 23, 2026, 02:11 PM UTC
We are investigating an emerging issue with WSA where incomplete or missing data is reported when filtering by TLS v3 Fingerprint. 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/.
-
investigating Apr 23, 2026, 03:06 PM UTC
We are continuing to work with our subject matter experts to investigate this issue. Customers and partners can find more details on the Akamai Community: https://community.akamai.com/customers/s/feed/0D5a70000151eEnCAIWe will provide an update within the next 60 minutes.
-
investigating Apr 23, 2026, 03:56 PM UTC
We are continuing to work with our subject matter experts to investigate this issue. Customers and partners can find more details on the Akamai Community: https://community.akamai.com/customers/s/group/0F90f000000DFgxCAG/service-incident-notificationsWe will provide an update within the next 120 minutes.
-
investigating Apr 23, 2026, 06:19 PM UTC
We are continuing to investigate this issue. Customers and partners can find more details on the Akamai Community: https://community.akamai.com/customers/s/group/0F90f000000DFgxCAG/service-incident-notificationsWe will provide an update within the next 3 hours.
-
investigating Apr 23, 2026, 09:50 PM UTC
We are continuing to investigate this issue. Customers and partners can find more details on the Akamai Community: https://community.akamai.com/customers/s/group/0F90f000000DFgxCAG/service-incident-notifications. Subsequent updates around mitigation status will be posted as progress is made.
-
resolved Apr 28, 2026, 05:39 PM UTC
We can confirm that the issue was mitigated at 10:45 UTC on April 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/0D5a70000151eEnCAI 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.
Read the full incident report →
- Detected by Pingoru
- Apr 23, 2026, 09:44 AM UTC
- Resolved
- Apr 23, 2026, 09:44 AM UTC
- Duration
- —
Affected: Akamai Control Center
Timeline · 1 update
-
resolved Apr 23, 2026, 09:44 AM UTC
We became aware of an issue in the Akamai Control Center related to errors when using the "Translate Error String" tool within "Edge Diagnostics". The issue lasted between 20:34 UTC on April 22, 2026, and 8:31 UTC on April 23, 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/0D5a7000014zYTlCAM 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.
Read the full incident report →
- Detected by Pingoru
- Apr 20, 2026, 12:25 PM UTC
- Resolved
- Apr 21, 2026, 01:07 AM UTC
- Duration
- 12h 42m
Affected: Edge DeliveryEnterprise Application Access
Timeline · 5 updates
-
investigating Apr 20, 2026, 12:25 PM UTC
We are investigating an emerging issue with edge delivery in our Frankfurt (DE-FRA-2) Data Center where customers may experience performance degradation. 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/.
-
investigating Apr 20, 2026, 12:58 PM UTC
We are continuing to investigate this issue.
-
monitoring Apr 20, 2026, 01:54 PM UTC
We have implemented a fix for this issue as of 13:12 UTC on April 20, 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/0D5a7000014QIlOCAW. We will continue to monitor to ensure that the impact has been fully mitigated.
-
resolved Apr 21, 2026, 01:07 AM UTC
We can confirm that the issue was mitigated at 13:12 UTC on April 20, 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.
-
postmortem Apr 21, 2026, 02:18 PM UTC
Customers and partners can find an incident summary report, here: https://community.akamai.com/customers/s/feed/0D5a7000014QIlOCAW
Read the full incident report →
- Detected by Pingoru
- Apr 16, 2026, 03:17 AM UTC
- Resolved
- Apr 16, 2026, 06:44 AM UTC
- Duration
- 3h 26m
Affected: NetStorage
Timeline · 4 updates
-
investigating Apr 16, 2026, 03:17 AM UTC
We are investigating an issue with NetStorage related to issues with new storage group creations or making changes to the existing storage groups. 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/.
-
identified Apr 16, 2026, 03:45 AM UTC
We have identified the cause of the issue, and a fix is being implemented. Customers and partners can find more details on the Akamai Community: https://community.akamai.com/customers/s/feed/0D5a7000013s3OVCAY. We will provide the next update as we make progress.
-
monitoring Apr 16, 2026, 06:09 AM UTC
We have implemented a fix for this issue as of 04:57 UTC on April 16, 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/0D5a7000013s3OVCAY. We will continue to monitor to ensure that the impact has been fully mitigated.
-
resolved Apr 16, 2026, 06:44 AM UTC
We can confirm that the issue was mitigated at 04:57 UTC on 16 April 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/0D5a7000013s3OVCAY 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.
Read the full incident report →
- Detected by Pingoru
- Apr 07, 2026, 06:43 PM UTC
- Resolved
- Apr 08, 2026, 01:02 PM UTC
- Duration
- 18h 18m
Affected: Configuration Deployment
Timeline · 6 updates
-
investigating Apr 07, 2026, 06:43 PM UTC
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/group/0F90f000000Fgx/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/.
-
investigating Apr 07, 2026, 07:15 PM UTC
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/0D5a7000012Uk7TCAS. We will provide an update within the next 60 minutes.
-
identified Apr 07, 2026, 08:40 PM UTC
We have identified the cause of the issue, and a platform fix is being tested. Customers can find instructions to mitigate impacts to their systems or services on the Akamai Community: https://community.akamai.com/customers/s/feed/0D5a7000012Uk7TCAS. We will provide an update as we have progress on the platform fix.
-
identified Apr 08, 2026, 10:30 AM UTC
We have determined a fix and it is going to be deployed at 11:00 UTC on April 8, 2026. Customers and partners can find more details on the Akamai Community: https://community.akamai.com/customers/s/feed/0D5a7000012Uk7TCAS We will provide another update post deploying the fix.
-
monitoring Apr 08, 2026, 12:00 PM UTC
We have implemented a fix for this issue as of 11:30 UTC on April 08, 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/0D5a7000012Uk7TCAS. We will continue to monitor to ensure that the impact has been fully mitigated.
-
resolved Apr 08, 2026, 01:02 PM UTC
We can confirm that the issue was mitigated at 11:30 UTC on April 8, 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/0D5a7000012Uk7TCAS 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.
Read the full incident report →
- Detected by Pingoru
- Apr 07, 2026, 12:11 PM UTC
- Resolved
- Apr 14, 2026, 07:47 PM UTC
- Duration
- 7d 7h
Affected: Reporting
Timeline · 7 updates
-
investigating Apr 07, 2026, 12:11 PM UTC
We are investigating an emerging issue with Data Services related to Reporting specifically with "Traffic by Geography" and "URL Traffic" where data is missing after March 28, 2026. 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/.
-
investigating Apr 07, 2026, 12:31 PM UTC
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/0D5a7000012RCWbCAO We will provide an update as we progress.
-
identified Apr 07, 2026, 07:00 PM UTC
We have identified the cause of the issue, and a fix is being implemented. Customers and partners can find more details on the Akamai Community: https://community.akamai.com/customers/s/feed/0D5a7000012RCWbCAO We will provide an update as we progress.
-
identified Apr 08, 2026, 09:45 AM UTC
We are continuing to work toward mitigating this issue. Customers and partners can find more details on the Akamai Community: https://community.akamai.com/customers/s/feed/0D5a7000012RCWbCAO We will provide an update as we progress.
-
identified Apr 09, 2026, 06:31 PM UTC
We are continuing to work toward mitigating this issue. Customers and partners can find more details on the Akamai Community: https://community.akamai.com/customers/s/feed/0D5a7000012RCWbCAO We will provide an update as we progress.
-
monitoring Apr 13, 2026, 02:14 PM UTC
We have implemented a fix for this issue as of 11:00 UTC on April 13, 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/0D5a7000012RCWbCAOWe will continue to monitor to ensure that the impact has been fully mitigated.
-
resolved Apr 14, 2026, 07:47 PM UTC
We can confirm that the issue was mitigated at 11:00 UTC on April 13, 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/0D5a7000012RCWbCAO 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.
Read the full incident report →
- Detected by Pingoru
- Apr 07, 2026, 10:02 AM UTC
- Resolved
- Apr 07, 2026, 01:31 PM UTC
- Duration
- 3h 29m
Affected: Akamai Control CenterConfiguration Deployment
Timeline · 3 updates
-
investigating Apr 07, 2026, 10:02 AM UTC
We are investigating an emerging issue with the Certificate Provisioning System related to users being presented with errors while trying to access the application via Akamai Control Center. 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/.
-
monitoring Apr 07, 2026, 10:36 AM UTC
We have implemented a fix for this issue as of 9:49 UTC on April 7, 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/0D5a7000012QbOsCAK. We will continue to monitor to ensure that the impact has been fully mitigated.
-
resolved Apr 07, 2026, 01:31 PM UTC
We can confirm that the issue was mitigated at 9:49 UTC on April 7, 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/0D5a7000012QbOsCAK 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.
Read the full incident report →
- Detected by Pingoru
- Apr 06, 2026, 06:22 PM UTC
- Resolved
- Apr 15, 2026, 04:02 PM UTC
- Duration
- 8d 21h
Affected: Edge Delivery
Timeline · 6 updates
-
investigating Apr 06, 2026, 06:22 PM UTC
We are investigating an emerging issue with Edge Delivery related to packet loss and general performance degradation. 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/.
-
investigating Apr 06, 2026, 06:57 PM UTC
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/0D5a7000012K6RECA0. We will provide an update within the next 60 minutes.
-
monitoring Apr 06, 2026, 07:46 PM UTC
We have implemented a fix for this issue as of approximately 18:30 UTC on April 6, 2026; based on current observations, the service is resuming normal operations. Customers and partners can find more details on Akamai Community: https://community.akamai.com/customers/s/feed/0D5a7000012K6RECA0. We will continue to monitor to ensure that the impact has been fully mitigated.
-
monitoring Apr 06, 2026, 10:54 PM UTC
We are continuing to monitor the situation following temporary mitigations put in place to restore service stability. While performance has stabilized, we will continue to provide periodic updates until a permanent mitigation has been fully implemented. Customers and partners can find additional technical details on the Akamai Community: https://community.akamai.com/customers/s/feed/0D5a7000012K6RECA0.
-
monitoring Apr 08, 2026, 11:53 PM UTC
We are continuing to monitor the situation in the Chicago, Illinois region following the implementation of permanent mitigations. Service performance remains stable, and our monitoring indicates there is minimal impact to customers at this time. We will provide further updates as needed to ensure the issue remains fully resolved. Customers and partners can find additional technical details on Akamai Community: https://community.akamai.com/customers/s/feed/0D5a7000012K6RECA0.
-
resolved Apr 15, 2026, 04:02 PM UTC
We can confirm that the issue was mitigated at 23:12 UTC on April 10, 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.
Read the full incident report →
- Detected by Pingoru
- Apr 03, 2026, 04:54 AM UTC
- Resolved
- Apr 06, 2026, 09:55 AM UTC
- Duration
- 3d 5h
Affected: CloudletsNetStorage
Timeline · 7 updates
-
investigating Apr 03, 2026, 04:54 AM UTC
We are investigating an issue with Cloudlets related to activation failures. 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/.
-
investigating Apr 03, 2026, 05:13 AM UTC
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/0D5a7000011usZNCAY. We will provide the next update as we make progress.
-
investigating Apr 03, 2026, 08:24 AM UTC
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/0D5a7000011usZNCAY. We will provide an update as we make progress.
-
investigating Apr 03, 2026, 10:27 AM UTC
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/0D5a7000011usZNCAY. We will provide an update as we make progress.
-
monitoring Apr 03, 2026, 12:00 PM UTC
We have rolled back a change which we believe may have caused this issue as of approximately 11:30 UTC on April 3, 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/0D5a7000011usZNCAY. We will continue to monitor to ensure that the impact has been fully mitigated.
-
resolved Apr 06, 2026, 09:55 AM UTC
We can confirm that the issue was mitigated at 11:29 UTC on 3 April 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/0D5a7000011usZNCAY 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.
-
postmortem Apr 07, 2026, 01:19 AM UTC
Customers and partners can find an incident summary report here: https://community.akamai.com/customers/s/feed/0D5a7000011usZNCAY.
Read the full incident report →
- Detected by Pingoru
- Mar 31, 2026, 07:03 AM UTC
- Resolved
- Apr 02, 2026, 02:13 PM UTC
- Duration
- 2d 7h
Affected: Edge DeliveryContent Purge
Timeline · 6 updates
-
investigating Mar 31, 2026, 07:03 AM UTC
We are investigating an issue with purge and edge delivery related to intermittent failures, latency and/or errors. 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/.
-
investigating Mar 31, 2026, 07:17 AM UTC
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/0D5a7000011IxVDCA0. We will provide the next update as we make progress.
-
investigating Mar 31, 2026, 11:10 AM UTC
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/0D5a7000011IxVDCA0.
-
investigating Mar 31, 2026, 04:18 PM UTC
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/0D5a7000011IxVDCA0.
-
investigating Mar 31, 2026, 09:56 PM UTC
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/0D5a7000011IxVDCA0.
-
resolved Apr 02, 2026, 02:13 PM UTC
We can confirm that the issue was mitigated at 14:00 UTC on April 2, 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/0D5a7000011IxVDCA0 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.
Read the full incident report →
- Detected by Pingoru
- Mar 24, 2026, 10:37 PM UTC
- Resolved
- Mar 25, 2026, 05:29 PM UTC
- Duration
- 18h 51m
Affected: CloudletsEdge Delivery
Timeline · 7 updates
-
investigating Mar 24, 2026, 10:37 PM UTC
We are investigating an emerging issue with Cloudlets where some redirect links may be not work properly. 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/.
-
investigating Mar 24, 2026, 11:14 PM UTC
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/0D5a7000010MD88CAG. We will provide an update within the next 60 minute.
-
investigating Mar 25, 2026, 12:12 AM UTC
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/0D5a7000010MD88CAG. We will provide an update within the next 60 minute.
-
investigating Mar 25, 2026, 01:50 AM UTC
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/0D5a7000010MD88CAG. We will provide another update as we make progress.
-
identified Mar 25, 2026, 04:34 AM UTC
We have changed the scope of this incident from Cloudlets specific issues To Edge Delivery issues as we determined that this is impacting DNS responses over 512 bytes including cloudlets. We are rolling back a change that seems to have caused the issue. Customers and partners can find more details on the Akamai Community: https://community.akamai.com/customers/s/feed/0D5a7000010MD88CAG.We will provide an update as we make progress.
-
identified Mar 25, 2026, 02:02 PM UTC
The rollback continues without issues and is expected to complete in the next 3 hours. Customers and partners can find more details on the Akamai Community: https://community.akamai.com/customers/s/feed/0D5a7000010MD88CAG. We will provide an update as we make progress.
-
resolved Mar 25, 2026, 05:29 PM UTC
We can confirm that the issue was mitigated at 17:24 UTC on March 25, 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/0D5a7000010MD88CAG?language=en_US 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.
Read the full incident report →
- Detected by Pingoru
- Mar 24, 2026, 10:34 PM UTC
- Resolved
- Mar 25, 2026, 12:30 AM UTC
- Duration
- 1h 55m
Affected: TLS Provisioning (Certificates, CPS)
Timeline · 3 updates
-
investigating Mar 24, 2026, 10:34 PM UTC
We are investigating an emerging issue with Certificate Provisioning System (CPS) occurring when internal users edit deployment settings. Specifically, the 'Select Cipher Profiles' section fails to update after clicking 'Edit' and 'Save'."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/0D5a7000010MQrWCAW. 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/.
-
investigating Mar 24, 2026, 10:57 PM UTC
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/0D5a7000010MQrWCAW. We will provide an update within the next 120 minutes.
-
resolved Mar 25, 2026, 12:30 AM UTC
After further investigation it was determined that this issue is not causing any customer impact or service disruption, we apologize for the confusion.
Read the full incident report →
- Detected by Pingoru
- Mar 19, 2026, 04:38 PM UTC
- Resolved
- Mar 23, 2026, 05:59 PM UTC
- Duration
- 4d 1h
Affected: Edge Delivery
Timeline · 11 updates
-
investigating Mar 19, 2026, 04:38 PM UTC
We are investigating an emerging issue with our Enhanced TLS Delivery Network related to intermittent TLS errors against Akamaized hostnames for customers who are using OpenJDK. 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/.
-
investigating Mar 19, 2026, 05:02 PM UTC
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/0D5a700000zYYneCAG. We will provide an update within the next 60 minutes.
-
investigating Mar 19, 2026, 06:05 PM UTC
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/0D5a700000zYYneCAG. We will provide an update within the next 60 minutes.
-
investigating Mar 19, 2026, 07:05 PM UTC
We are continuing to investigate this issue. We will provide an update within the next 60 minutes.
-
investigating Mar 19, 2026, 08:05 PM UTC
We are continuing to investigate this issue. We will provide an update within the next 60 minutes.
-
investigating Mar 19, 2026, 09:03 PM UTC
We are continuing to investigate this issue. We will provide an update within the next 60 minutes.
-
investigating Mar 19, 2026, 09:58 PM UTC
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/0D5a700000zYYneCAG. We will provide an update within the next 60 minutes.
-
investigating Mar 19, 2026, 11:00 PM UTC
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/0D5a700000zYYneCAG. We will provide an update within the next 60 minutes
-
investigating Mar 19, 2026, 11:55 PM UTC
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/0D5a700000zYYneCAG. We will provide an update within the next 60 minutes
-
investigating Mar 20, 2026, 12:55 AM UTC
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/0D5a700000zYYneCAG. We will provide an update within the next 60 minutes
-
resolved Mar 23, 2026, 05:59 PM UTC
We can confirm that the issue was mitigated at 18:35 UTC on March 20, 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/0D5a700000zYYneCAG 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.
Read the full incident report →
- Detected by Pingoru
- Mar 17, 2026, 09:57 AM UTC
- Resolved
- Mar 17, 2026, 12:19 PM UTC
- Duration
- 2h 22m
Affected: Enterprise Application AccessEnterprise Application Access: Configuration
Timeline · 3 updates
-
investigating Mar 17, 2026, 09:57 AM UTC
We are investigating an emerging issue with Enterprise Application Access (EAA) related to device postures. We are actively investigating the issue and will provide another update within the next 120 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/.
-
investigating Mar 17, 2026, 11:39 AM UTC
We've engaged the necessary subject matter experts and are continuing to investigate this issue. We will continue to post updates as more information is available.
-
resolved Mar 17, 2026, 12:19 PM UTC
We can confirm that the issue was mitigated at 12:00 UTC on March 17, 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/0D5a700000z74q9CAA 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.
Read the full incident report →
- Detected by Pingoru
- Mar 13, 2026, 06:39 PM UTC
- Resolved
- Mar 13, 2026, 07:57 PM UTC
- Duration
- 1h 18m
Affected: Account ProtectorEnterprise Application AccessBot ManagementEnterprise Application Access: API ServiceEnterprise Application Access: ConfigurationEnterprise Application Access: ReportingWeb Security AnalyticsETP/SIA: ClientETP/SIA: ConfigurationETP/SIA: ConnectorsETP/SIA: Name ServersETP/SIA: ReportingETP/SIA: Web Proxy
Timeline · 4 updates
-
investigating Mar 13, 2026, 06:39 PM UTC
We are investigating an emerging issue with Account Protector, Bot Manager Premier, Enterprise Application Access (EAA), and ETP/SIA (Secure Internet Access) related to connectivity issues at the Compute Washington Data Center beginning at approximately 18:00 UTC. 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/0D5a700000yhjlyCAA. 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/.
-
identified Mar 13, 2026, 07:01 PM UTC
We have identified the cause of the issue, and a fix is being implemented. Customers and partners can find more details on the Akamai Community: https://community.akamai.com/customers/s/feed/0D5a700000yhjlyCAA. We will provide an update within the next 60 minutes.
-
resolved Mar 13, 2026, 07:57 PM UTC
We can confirm that the issue was mitigated at 18:50 UTC on March 13, 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/0D5a700000yhjlyCAA 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.
-
postmortem Mar 17, 2026, 08:47 PM UTC
Customers and partners can find an incident summary report here: https://community.akamai.com/customers/s/feed/0D5a700000yhjlyCAA
Read the full incident report →
- Detected by Pingoru
- Mar 10, 2026, 05:49 PM UTC
- Resolved
- Mar 10, 2026, 05:49 PM UTC
- Duration
- —
Affected: Edge Delivery
Timeline · 1 update
-
resolved Mar 10, 2026, 05:49 PM UTC
We became aware of an issue with Edge Delivery related to performance degradation in Dallas, US. The issue lasted between 14:37 UTC and 15:43 UTC on March 10, 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/0D5a700000y8scWCAQ 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.
Read the full incident report →
- Detected by Pingoru
- Mar 10, 2026, 05:38 PM UTC
- Resolved
- Mar 10, 2026, 10:00 PM UTC
- Duration
- 4h 21m
Affected: Global Traffic Management
Timeline · 6 updates
-
investigating Mar 10, 2026, 05:38 PM UTC
We are investigating an emerging issue with multiple Akamai products related to DNS malicious filtering where users may encounter fully qualified domain names (FQDNs) erroneously being flagged as malicious. 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/.
-
investigating Mar 10, 2026, 06:04 PM UTC
We are continuing to investigate this issue. We identified that the components listed on this status page were incorrectly marked when the update was created. We have now corrected this to reflect the accurately impacted components. We apologize for any confusion this may have caused. Customers and partners can find more details on Akamai Community: https://community.akamai.com/customers/s/feed/0D5a700000y9enBCAQ. We will provide an update within the next 60 minutes.
-
identified Mar 10, 2026, 06:50 PM UTC
We have identified the cause of the issue, and a fix is being implemented. Customers and partners can find more details on the Akamai Community: https://community.akamai.com/customers/s/feed/0D5a700000y9enBCAQ. We will provide an update within the next 60 minutes.
-
identified Mar 10, 2026, 08:08 PM UTC
We continue to work on implementing a fix for this issue. Customers and partners can find more details on the Akamai Community: https://community.akamai.com/customers/s/feed/0D5a700000y9enBCAQ. We will provide an update within the next 60 minutes.
-
monitoring Mar 10, 2026, 09:03 PM UTC
We continue to work on implementing a fix for this issue. Customers and partners can find more details on the Akamai Community: https://community.akamai.com/customers/s/feed/0D5a700000y9enBCAQ. We will provide an update within the next 60 minutes.
-
resolved Mar 10, 2026, 10:00 PM UTC
We can confirm that the issue was mitigated at 20:39 UTC on March 10, 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.
Read the full incident report →
- Detected by Pingoru
- Mar 09, 2026, 07:28 PM UTC
- Resolved
- Mar 09, 2026, 10:36 PM UTC
- Duration
- 3h 7m
Affected: Account ProtectorEnterprise Application AccessBot ManagementEnterprise Application Access: API ServiceEnterprise Application Access: ConfigurationEnterprise Application Access: ReportingETP/SIA: ClientETP/SIA: ConfigurationETP/SIA: ConnectorsETP/SIA: Name ServersETP/SIA: ReportingETP/SIA: Web Proxy
Timeline · 5 updates
-
investigating Mar 09, 2026, 07:28 PM UTC
We are investigating an emerging issue with Account Protector, Bot Manager Premier, Enterprise Application Access (EAA), and ETP/SIA related to Compute connectivity issues beginning at approximately 18:10 UTC. 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/.
-
investigating Mar 09, 2026, 07:53 PM UTC
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/0D5a700000y0QksCAE. We will provide an update within the next 60 minutes.
-
investigating Mar 09, 2026, 08:55 PM UTC
We are continuing to investigate this issue. We will provide an update within the next 60 minutes.
-
monitoring Mar 09, 2026, 09:32 PM UTC
We have implemented a fix for this issue as of 21:16 UTC on March 9, 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/0D5a700000y0QksCAE. We will continue to monitor to ensure that the impact has been fully mitigated.
-
resolved Mar 09, 2026, 10:36 PM UTC
We can confirm that the issue was mitigated at 21:16 UTC on March 9, 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.
Read the full incident report →
- Detected by Pingoru
- Mar 07, 2026, 07:00 PM UTC
- Resolved
- Mar 07, 2026, 10:06 PM UTC
- Duration
- 3h 6m
Affected: Bot Management
Timeline · 5 updates
-
investigating Mar 07, 2026, 07:00 PM UTC
We are investigating an emerging issue with Bot Manager Premier related to legitimate traffic being blocked with elevated false positives. 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/.
-
investigating Mar 07, 2026, 07:55 PM UTC
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/0D5a700000xlBv4CAE. We will provide an update within the next 60 minutes.
-
identified Mar 07, 2026, 08:49 PM UTC
We have identified the cause of the issue, and a fix is being implemented. Customers and partners can find more details on Akamai Community: https://community.akamai.com/customers/s/feed/0D5a700000xlBv4CAE. We will provide an update within the next 60 minutes.
-
identified Mar 07, 2026, 09:43 PM UTC
We are continuing to implement a fix for this issue. Thank you for your patience. We will provide an update within the next 60 minutes.
-
resolved Mar 07, 2026, 10:06 PM UTC
We can confirm that the issue was mitigated at 22:00 UTC on March 7, 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/0D5a700000xlBv4CAE, 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.
Read the full incident report →
- Detected by Pingoru
- Feb 27, 2026, 09:32 PM UTC
- Resolved
- Mar 03, 2026, 05:32 PM UTC
- Duration
- 3d 20h
Affected: Edge Delivery
Timeline · 5 updates
-
monitoring Feb 27, 2026, 09:32 PM UTC
We became aware of a reoccurrence of the issue with a third-party service provider causing degraded networking performance and packet loss with multiple Akamai services in the Mumbai, IN region related to https://www.akamaistatus.com/incidents/m5z1b82n5h0z. The issue lasted between 19:45 UTC and 21:00 UTC on February 27, 2026. We have taken mitigation steps and escalated to our third-party service provider to investigate the additional period of impact; 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/0D5a700000wQl7YCAS. 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.
-
investigating Feb 28, 2026, 11:16 AM UTC
We are aware of an ongoing reoccurrence of this issue starting from 09:17 UTC on February 28, 2026, which may cause degraded networking performance and packet loss with multiple Akamai services in the Mumbai, IN region. We are continuing to work with our third-party service provider to nvestigate this issue. Customers and partners can find more details on the Akamai Community: https://community.akamai.com/customers/s/feed/0D5a700000wQl7YCAS. We will provide an update within the next 120 minutes.
-
investigating Feb 28, 2026, 12:26 PM UTC
We have been able to apply mitigation actions that improve the experience for customers connecting to the Mumbai, IN region, and continue working with our third-party service provider to investigate this issue. Customers and partners can find more details on the Akamai Community: https://community.akamai.com/customers/s/feed/0D5a700000wQl7YCAS. We will provide an update as we make progress.
-
monitoring Feb 28, 2026, 05:43 PM UTC
We have taken mitigation steps and escalated to our third-party service provider who confirmed the impact was caused due to ongoing restoration activities on their cable system during that period, which has been completed.; based on current observations as of 13:40 UTC on February 28, 2026, the service is resuming normal operations. Customers and partners can find more details on the Akamai Community: https://community.akamai.com/customers/s/feed/0D5a700000wQl7YCAS. We will continue to monitor to ensure that the impact has been fully mitigated.
-
resolved Mar 03, 2026, 05:32 PM UTC
We can confirm that the issue was mitigated at 13:40 UTC on February 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/0D5a700000wQl7YCAS, 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.
Read the full incident report →