- Detected by Pingoru
- Jun 16, 2026, 03:45 PM UTC
- Resolved
- Jun 16, 2026, 03:45 PM UTC
- Duration
- —
Affected: Edge Delivery
Timeline · 1 update
-
resolved Jun 16, 2026, 03:45 PM UTC
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.
Read the full incident report →
- Detected by Pingoru
- Jun 12, 2026, 02:58 PM UTC
- Resolved
- Jun 12, 2026, 02:58 PM UTC
- Duration
- —
Affected: Log Delivery
Timeline · 1 update
-
resolved Jun 12, 2026, 02:58 PM UTC
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.
Read the full incident report →
- Detected by Pingoru
- Jun 10, 2026, 06:38 PM UTC
- Resolved
- Jun 11, 2026, 04:41 PM UTC
- Duration
- 22h 3m
Affected: Bot Management
Timeline · 3 updates
-
investigating Jun 10, 2026, 06:38 PM UTC
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/
-
monitoring Jun 10, 2026, 06:51 PM UTC
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.
-
resolved Jun 11, 2026, 04:41 PM UTC
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.
Read the full incident report →
- Detected by Pingoru
- Jun 06, 2026, 04:29 AM UTC
- Resolved
- Jun 06, 2026, 07:21 AM UTC
- Duration
- 2h 51m
Affected: Edge Delivery
Timeline · 2 updates
-
investigating Jun 06, 2026, 04:29 AM UTC
We became aware of an issue with Edge Delivery in Americas Region related to elevated packet loss and service degradation between 1:00 UTC and 1:30 UTC on June 6, 2026. We are actively investigating the cause of the elevated packet loss 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.
-
resolved Jun 06, 2026, 07:21 AM UTC
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.
Read the full incident report →
- Detected by Pingoru
- May 27, 2026, 01:28 PM UTC
- Resolved
- May 27, 2026, 01:28 PM UTC
- Duration
- —
Affected: Edge Delivery
Timeline · 1 update
-
resolved May 27, 2026, 01:28 PM UTC
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.
Read the full incident report →
- Detected by Pingoru
- May 21, 2026, 01:58 PM UTC
- Resolved
- May 21, 2026, 04:52 PM UTC
- Duration
- 2h 54m
Affected: Telephony
Timeline · 4 updates
-
investigating May 21, 2026, 01:58 PM UTC
We are investigating an emerging issue with Email Exchange server related to delay with the emails. 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 May 21, 2026, 02: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/0D5a7000019St8yCAC .We will provide an update within the next 60 minutes.
-
monitoring May 21, 2026, 02:04 PM UTC
We have implemented a fix for this issue as of 13:00 UTC on May 21, 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/0D5a7000019St8yCACWe will continue to monitor to ensure that the impact has been fully mitigated.
-
resolved May 21, 2026, 04:52 PM UTC
We can confirm that the issue was mitigated at 14:50 UTC on May 21, 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/0D5a7000019St8yCAC 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
- May 20, 2026, 02:29 PM UTC
- Resolved
- May 21, 2026, 12:36 PM UTC
- Duration
- 22h 7m
Affected: Configuration Deployment
Timeline · 19 updates
Read the full incident report →
- Detected by Pingoru
- May 19, 2026, 10:13 AM UTC
- Resolved
- Jun 01, 2026, 07:46 AM UTC
- Duration
- 12d 21h
Affected: Reporting
Timeline · 5 updates
-
identified May 19, 2026, 10:13 AM UTC
We are aware of an issue with the 'URL Traffic' and ‘URL Responses’ report related to reporting data unavailability. We have identified the cause of the issue, and a fix is being implemented. 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/.
-
identified May 20, 2026, 08:07 AM UTC
The data is slowly getting updated. Customers and partners can find more details on the Akamai Community: https://community.akamai.com/customers/s/feed/0D5a7000018q2TuCAI. We will provide an update once the data catches up.
-
identified May 22, 2026, 05:20 AM UTC
The data is getting updated. Customers and partners can find more details on the Akamai Community: https://community.akamai.com/customers/s/feed/0D5a7000018q2TuCAI. We will provide an update once the data catches up.
-
monitoring May 28, 2026, 09:50 AM UTC
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/0D5a7000018q2TuCAI. We will continue to monitor to ensure that the impact has been fully mitigated.
-
resolved Jun 01, 2026, 07:46 AM UTC
We can confirm that the issue was mitigated 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/0D5a7000018q2TuCAI 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
- May 14, 2026, 06:08 PM UTC
- Resolved
- May 14, 2026, 06:45 PM UTC
- Duration
- 37m
Affected: Cloudlets
Timeline · 4 updates
-
investigating May 14, 2026, 06:08 PM UTC
We are investigating an emerging issue with Cloudlets related to issues with activating Cloudlets policies. 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 May 14, 2026, 06:28 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/0D5a70000189Hk3CAE. We will provide an update within the next 30 minutes.
-
monitoring May 14, 2026, 06:37 PM UTC
We have rolled back a release which we believe may have caused this issue as of 18:21 UTC on May 14th, 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/0D5a70000189Hk3CAE. We will continue to monitor to ensure that the impact has been fully mitigated.
-
resolved May 14, 2026, 06:45 PM UTC
We can confirm that the issue was mitigated at 18:21 UTC on May 14th, 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/0D5a70000189Hk3CAE, 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
- May 13, 2026, 09:33 AM UTC
- Resolved
- May 13, 2026, 10:25 AM UTC
- Duration
- 51m
Affected: Edge Delivery
Timeline · 2 updates
-
investigating May 13, 2026, 09:33 AM UTC
We are investigating an emerging issue with Edge Delivery related to general performance degratation in Amsterdam, Netherlands. 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/.
-
resolved May 13, 2026, 10:25 AM UTC
We can confirm that the issue was mitigated at approximately 09:40 UTC on May 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/0D5a7000017tokVCAQ 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
- May 12, 2026, 06:39 PM UTC
- Resolved
- May 13, 2026, 01:08 AM UTC
- Duration
- 6h 29m
Affected: Edge Delivery
Timeline · 7 updates
Read the full incident report →
- Detected by Pingoru
- May 06, 2026, 11:21 AM UTC
- Resolved
- May 06, 2026, 12:01 PM UTC
- Duration
- 39m
Affected: TLS Provisioning (Certificates, CPS)
Timeline · 2 updates
-
investigating May 06, 2026, 11:21 AM UTC
We are investigating an emerging issue with the Certificate Provisioning System (CPS) in the Akamai Control Center related to users being unable to perform changes. 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/.
-
resolved May 06, 2026, 12:01 PM UTC
We can confirm that the issue was mitigated at approximately 11:30 UTC on May 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/0D5a7000016uVhvCAE 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 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, 04:42 PM UTC
- Resolved
- May 04, 2026, 03:05 AM UTC
- Duration
- 5d 10h
Affected: Edge DeliveryBot Management
Timeline · 5 updates
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
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
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 →