Live status / AI & models

Akamai is operating normally.

Akamai is operating normally.

Signal updated 1d ago · Sep 16, 2026, 2:00 PM UTC

OperationalOfficial signal: none

Affected surface

Components

06 components
Content DeliveryOfficial componentOperational
App & Network SecurityOfficial componentOperational
Enterprise SecurityOfficial componentOperational
Data ServicesOfficial componentOperational
ConfigurationOfficial componentOperational
Customer Service, Documentation and CommunityOfficial componentOperational

0 of 6 affected

Last 30 days · Status timeline

What changed

47 updates
  1. Monitoring

    We became aware of an issue with the Certificate Provisioning System (CPS) involving timeouts in the User Interface of Akamai Control Center, as well as errors when using the API. The issue lasted between 03:12 UTC on 19 August 2026 and 03:34 UTC on 19 August 2026; based on current observations, the service has resumed normal operations. Customers and partners can find more details on the Akamai Community: https://community.akamai.com/customers/s/feed/0D5a700001PHy9qCAD. We will continue to monitor to ensure that the impact has been fully mitigated. We apologize for the impact and thank you for your patience and continued support. We are committed to making continuous improvements to make our systems better and prevent a recurrence of this issue.

  2. Monitoring

    We are continuing to monitor for any further issues.

  3. Resolved

    We can confirm that the issue was mitigated at 03:34 UTC on 19 August, 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/0D5a700001PHy9qCAD 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.

  4. Investigating

    We are investigating an emerging issue with "Traffic by Hostname" related to reporting data availability. 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/.

  5. Investigating

    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. We will provide an update within the next 60 minutes.

  6. Identified

    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/group/0F90f000000DFgxCAG/. We will provide an update within the next 60 minutes.

  7. Identified

    We are continuing working on mitigating the issue and will provide another update as progress is made. We thank you for your patience.Customers and partners can find more details on the Akamai Community: https://community.akamai.com/customers/s/feed/0D5a700001PVMc9CAH

  8. Investigating

    We are investigating an emerging issue with a third-party service provider causing Edge Delivery issues in India. We are working with the service provider and 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, or Akamai Control Center, to contact Akamai Technical Support. Contact information is available at https://www.akamai.com/us/en/support/.

  9. Investigating

    We are continuing to investigate the issue. After further investigation the issue appears to not be caused by a third-party service provider. Customers and partners can find more details on the Akamai Community: https://community.akamai.com/customers/s/feed/0D5a700001Psh2gCAB. We will provide an update within the next 60 minutes.

  10. Investigating

    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/0D5a700001Psh2gCAB. We will provide an update as we make progress.

  11. Investigating

    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/0D5a700001Psh2gCAB. We will provide an update as we make progress.

  12. Investigating

    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/0D5a700001Psh2gCAB. We will provide an update as we make progress.

  13. Investigating

    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/0D5a700001Psh2gCAB. We will provide an update as we make progress.

  14. Monitoring

    We have implemented a fix for this issue; 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/0D5a700001Psh2gCAB. We will continue to monitor to ensure that the impact has been fully mitigated.

  15. Investigating

    We are investigating a recurrence of this issue. Customers and partners can find more details on the Akamai Community: https://community.akamai.com/customers/s/feed/0D5a700001PVMc9CAH. We will provide an update within the next 60 minutes.

  16. Investigating

    We are continuing working on mitigating the issue and will provide another update as progress is made. We thank you for your patience.Customers and partners can find more details on the Akamai Community: https://community.akamai.com/customers/s/feed/0D5a700001PVMc9CAH.

  17. Resolved

    We can confirm that the issue was mitigated at 14:25 UTC on August 22, 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/0D5a700001Psh2gCAB 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.

  18. Monitoring

    We have implemented a fix for this issue as of 14:50 UTC on 25 August, 2026; based on current observations, the service has resumed normal operations. Customers and partners can find more details on the Akamai Community: https://community.akamai.com/customers/s/feed/0D5a700001PVMc9CAH. We will continue to monitor to ensure that the impact has been fully mitigated.

  19. Investigating

    We are investigating an emerging issue with Media Services Live 4 related to live streaming with 502 bad gateway 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/.

  20. Investigating

    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/0D5a700001QPRcTCAX?language=en_US. We will provide an update within the next 30 minutes.

  21. Investigating

    We are continuing to investigate this issue and work towards mitigation. Customers and partners can find more details on the Akamai Community: https://community.akamai.com/customers/s/feed/0D5a700001QPRcTCAX?language=en_US. We will provide an update within the next 30 minutes.

  22. Identified

    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/0D5a700001QPRcTCAX. We will provide an update within the next 30 minutes.

  23. Monitoring

    We have implemented a fix for this issue as of 18:15 UTC on August 25, 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/0D5a700001QPRcTCAX. We will continue to monitor to ensure that the impact has been fully mitigated.

  24. Monitoring

    Service operations remain in a stable state. We will continue to monitor to ensure that the impact has been fully mitigated.Customers and partners can find more details on the Akamai Community: https://community.akamai.com/customers/s/feed/0D5a700001PVMc9CAH. 

  25. Resolved

    We can confirm that the issue was mitigated at 18:15 UTC on August 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/0D5a700001QPRcTCAX 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.

  26. Investigating

    We are investigating an issue with Event Center related to the reporting dashboard being inaccessible with data unavailability. 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/feed/0D5a700001QvOI6CAN. 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/.

  27. Investigating

    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/0D5a700001QvOI6CAN. We will provide the next update as we make progress.

  28. Monitoring

    We have implemented a fix for this issue as of 03:30 UTC on 28 August 2026; based on current observations, the service is resuming normal operations. Customers and partners can find more details on the Akamai Community: https://community.akamai.com/customers/s/feed/0D5a700001QvOI6CAN. We will continue to monitor to ensure that the impact has been fully mitigated.

  29. Resolved

    We can confirm that the issue was mitigated at 03:30 UTC on 28 August 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/0D5a700001QvOI6CAN 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.

  30. Resolved

    We can confirm that the issue was mitigated at 23:50 UTC on August 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/0D5a700001PVMc9CAH 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.

  31. Investigating

    We are investigating an issue with Application Load Balancer (ALB) reporting related to availability with 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/feed/0D5a700001S7tYbCAJ . 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/.

  32. Investigating

    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/0D5a700001S7tYbCAJ. We will provide the next update as we make progress.

  33. Monitoring

    We have implemented a fix for this issue as of 14:20 UTC on 4 September, 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/0D5a700001S7tYbCAJ. We will continue to monitor to ensure that the impact has been fully mitigated.

  34. Resolved

    We became aware of an issue with a network component related to connectivity in the Atlanta, GA region which impacted the Certificate Provisioning System as well as potential impact to other Edge traffic through the region. The issue lasted between 12:21 UTC and 14:19 UTC on September 4, 2026. We can confirm that the issue is now resolved, and the service has resumed normal operation. Customers and partners can view additional details about the incident by logging in to: 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.

  35. Resolved

    We can confirm that the issue was mitigated at 14:20 UTC on 4 September, 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/0D5a700001S7tYbCAJ 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.

  36. Investigating

    We are investigating an emerging issue with Edge Delivery related to increased latency and elevated end user 403 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 Akamai Control Center, to contact Akamai Technical Support. Contact information is available at https://www.akamai.com/us/en/support/.

  37. Identified

    We have identified the cause of the issue and are implementing a fix. We initially mentioned elevated 403 errors in this status page post as an additional symptom of the incident. That was incorrect, and we have removed the reference. Customers and partners can find more details on the Akamai Community: https://community.akamai.com/customers/s/feed/0D5a700001T8d9uCAB. We will provide another update within the next 60 minutes.

  38. Monitoring

    We have implemented a fix for this issue as of 18:10 UTC on 10 September 2026; based on current observations, the service is resuming normal operations. We will continue to monitor to ensure that the impact has been fully mitigated.

  39. Resolved

    We can confirm that the issue was mitigated at 00:10 UTC on 11 September 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/0D5a700001T8d9uCAB 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.

  40. Monitoring

    We became aware of an issue with the HTTPS edge delivery network related to performance issues. The issue lasted between 00:45 UTC and 00:57 UTC on 15 September 2026. We have implemented a fix for this issue, which we believe may have caused the issue; 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/0D5a700001TpkinCAB. 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.

  41. Monitoring

    We are continuing to monitor the issue to ensure that the impact is fully mitigated. We will provide the next update as we make progress. We apologize for the impact.

  42. Monitoring

    We are continuing to monitor the issue to ensure that the impact is fully mitigated. We will provide the next update as we make progress. We apologize for the impact.

  43. Resolved

    We can confirm that the issue was mitigated at 00:57 UTC on 15 September 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/0D5a700001TpkinCAB 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.

  44. Investigating

    We are investigating an emerging issue with a third-party service provider where users might experience issues creating new tickets with Akamai Support. The issue appears to have started around 08:00 UTC on Sep 16, 2026. The customers can use https://control.akamai.com/apps/support-ui/#/contact-support or reach out to country-specific support numbers for urgent cases. We are working with the service provider and actively investigating the issue and will provide another update within the next 60 minutes.

  45. Investigating

    We are continuing to work 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/0D5a700001U5jVxCAJ.

  46. Monitoring

    The third-party provider has implemented a fix for this issue as of 12:20 UTC on 16 Sep,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/0D5a700001U5jVxCAJ. We will continue to monitor to ensure that the impact has been fully mitigated

  47. Resolved

    We can confirm that the issue was mitigated at 12:20 UTC on Sep 16, 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/0D5a700001U5jVxCAJ 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.