Is Akamai down?

Last checked 4m ago
Current status
Akamai has degraded performance

4 active incidents: Performance Degradation for Customers in Mumbai and Chennai, Edge Delivery issues between Indonesia and Singapore · +2 more

  • Official status page: akamaistatus.com
  • Checked every 5 minutes
  • 42 components tracked

Akamai is reporting degraded performance right now (last checked 4m ago). Services are up but slower or partially failing.

Real-time Akamai status, recent outages, and incident history: pulled directly from Akamai's official status page at akamaistatus.com every 5 minutes. Pingoru tracks 42 Akamai services and has captured 33 incidents in the last 90 days (99.10% uptime). Get email, Slack, Discord, or webhook alerts the moment Akamai reports a new incident, free for 3 monitors, no credit card.

Users who monitor Akamai also follow these Status Pages services: StatusPage Diligent ServiceTitan QuaverEd Boomi Unbounce Chowly Signicat FACEIT Sync View all 8,000+ providers
Akamai uptime 99.10% uptime · past 90 days
Mon Wed Fri
JulAugSepOct
Less More

Active incidents 4

  1. Ongoing ● 1d 15h
    Started Oct 27, 2026, 01:09 PM UTC
    Edge Delivery
    Timeline · 1 update
    • investigating · Oct 27, 2026, 01:09 PM UTC

      On October 27, 2026, between 08:05 UTC and 10:45 UTC customers using services in Mumbai and Chennai may have experienced performance degradation. This occurred due to packet loss within an upstream provider’s network. As of 10:45 UTC the loss has subsided, and we are no longer seeing degraded performance in the affected regions. We have been monitoring for recurrence, and will continue to do so for the next few hours.If you have questions or are still 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/.

    Latest: On October 27, 2026, between 08:05 UTC and 10:45 UTC customers using services in Mumbai and Chennai may have experienced performance degradation. This occurred due to packet loss w…

  2. Ongoing ● 3d 14h
    Started Oct 25, 2026, 01:44 PM UTC
    Edge Delivery
    Timeline · 3 updates
    • investigating · Oct 25, 2026, 01:44 PM UTC

      We are investigating an emerging issue with Edge delivery related to performance degradation and timeouts between Indonesia and Singapore. 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 · Oct 25, 2026, 02:43 PM UTC

      We are continuing to work 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/0D5a700001b6aheCAA. Subsequent updates around mitigation status will be posted as progress is made.

    • monitoring · Oct 25, 2026, 04:06 PM UTC

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

    Latest: We have implemented a fix for this issue as of 13:11 UTC on 25 October, 2026; based on current observations, the service is resuming normal operations. Customers and partners can f…

  3. Ongoing ● 5d 16h
    Started Oct 23, 2026, 12:00 PM UTC
    Akamai Customer Community
    Timeline · 7 updates
    • investigating · Oct 23, 2026, 12:00 PM UTC

      Akamai is aware of the recently published remote code execution vulnerability: CVE-2026-111497.Our subject matter experts are actively investigating and taking the appropriate mitigation actions, while we continue to monitor our platform in parallel. We will provide updates as additional information becomes available.In the interest of time, we are providing you with the most current information available, which is subject to changes, corrections, and updates.

    • investigating · Oct 23, 2026, 04:42 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/0D5a700001apcFhCAIWe will provide an update as we progress.

    • investigating · Oct 23, 2026, 08:07 PM UTC

      We are continuing to investigate this issue to evaluate any possible impact to customers and our platform, so far we don't have evidence of customer impact caused by this vulnerability. The appropriate subject matter experts are engaged. We will continue to provide updates until we have a clearer picture about the evaluation and the mitigation plan. Subsequent updates around mitigation status will be posted as progress is made.

    • identified · Oct 24, 2026, 12:34 AM UTC

      We will continue to investigate and evaluate any possible impact to customers and our platform over the weekend. So far the investigation has not shown evidence of customer impact caused by this vulnerability. The appropriate subject matter experts are engaged. We will continue to provide updates until we have a clearer picture about the evaluation and the mitigation plan. Subsequent updates around mitigation status will be posted as progress is made.

    • investigating · Oct 24, 2026, 12:59 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/0D5a700001apcFhCAI We will provide subsequent updates as we make progress.

    • investigating · Oct 26, 2026, 04:13 PM UTC

      We are continuing to investigate this issue. The scope of this CVE has been expanded to include any foreign data which is being processed with the Brotli decoder, not just node.js. Customers and partners can find more details on the Akamai Community: https://community.akamai.com/customers/s/feed/0D5a700001apcFhCAIWe will provide an update as we progress.

    • investigating · Oct 28, 2026, 05:43 PM UTC

      Our investigation has revealed that a significant majority of our Platform is not affected by this CVE. We are continuing to investigate this issue to evaluate possible impact to customers and remaining Akamai products. Customers and partners can find more details on the Akamai Community: https://community.akamai.com/customers/s/feed/0D5a700001apcFhCAI. We will provide an update as we progress.

    Latest: Our investigation has revealed that a significant majority of our Platform is not affected by this CVE. We are continuing to investigate this issue to evaluate possible impact to c…

  4. Ongoing ● 6d 7h
    Started Oct 22, 2026, 08:17 PM UTC
    Akamai MFAEnterprise Application AccessEnterprise Application Access: API ServiceEnterprise Application Access: ConfigurationEnterprise Application Access: ReportingETP/SIA: ClientETP/SIA: ConfigurationETP/SIA: ConnectorsETP/SIA: Name ServersETP/SIA: Reporting
    Timeline · 4 updates
    • investigating · Oct 22, 2026, 08:17 PM UTC

      Akamai is aware of the recently published F5/NGINX vulnerabilities (CVE-2026-15176, CVE-2026-97205, and CVE-2026-93479), and our teams are investigating their potential impact across our platform and infrastructure.F5 has released out-of-band security patches addressing three critical severity vulnerabilities in NGINX Open Source and NGINX Plus. These vulnerabilities may allow unauthenticated attackers to trigger heap buffer overflows, which could cause a denial of service or potential remote code execution if ASLR is bypassed.If you are running a vulnerable version of NGINX Open Source or NGINX Plus, we recommend following guidance from F5/NGINX and applying available patches.We will post more details for customers and partners with a valid Control Center login at https://community.akamai.com/customers/s/group/0F90f000000DFgx/service-incident-notifications as additional information becomes available. 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/.

    • identified · Oct 23, 2026, 05:18 PM UTC

      Akamai continues to investigate the potential impact of the recently published F5/NGINX vulnerabilities (CVE-2026-15176, CVE-2026-97205, and CVE-2026-93479) across our platform and infrastructure. Our teams are taking action where necessary and will provide additional updates as more information becomes available.Customers and partners with a valid Control Center login can find more details at https://community.akamai.com/customers/s/group/0F90f000000DFgx/service-incident-notifications.If you have questions or are experiencing impact related 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/.

    • monitoring · Oct 23, 2026, 08:03 PM UTC

      Akamai continues to investigate the potential impact of the recently published F5/NGINX vulnerabilities (CVE-2026-15176, CVE-2026-97205, and CVE-2026-93479) across our platform and infrastructure.As part of our initial assessment, we included EAA, MFA, and SIA in the affected component selection. Based on our investigation to date, we have determined that these offerings are not vulnerable to these CVEs and have updated the affected component selection accordingly. We apologize for any concern this may have caused.Our teams continue to monitor the situation closely and respond where necessary. We will update the affected components as our investigation progresses.Customers and partners with a valid Control Center login can find more details at https://community.akamai.com/customers/s/group/0F90f000000DFgx/service-incident-notifications.If you have questions or are experiencing impact related 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/.

    • monitoring · Oct 23, 2026, 09:55 PM UTC

      Akamai continues to investigate the potential impact of the recently published F5/NGINX vulnerabilities (CVE-2026-15176, CVE-2026-97205, and CVE-2026-93479) across our platform and infrastructure. Customers and partners with a valid Control Center login can find more details at https://community.akamai.com/customers/s/group/0F90f000000DFgx/service-incident-notifications. If you have questions or are experiencing impact related 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/.

    Latest: Akamai continues to investigate the potential impact of the recently published F5/NGINX vulnerabilities (CVE-2026-15176, CVE-2026-97205, and CVE-2026-93479) across our platform and…

Recent outages & incidents

Past 90 days
  1. Resolved 5h 53m
    Started Oct 27, 2026, 09:58 AM UTC · Resolved Oct 27, 2026, 03:52 PM UTC
    Enterprise Application Access
    Timeline · 4 updates
    • investigating · Oct 27, 2026, 09:58 AM UTC

      We are investigating an issue with Enterprise Application Access that is affecting a subset of Unified EAA Connectors. This issue began on October 27, 2026, at approximately 01:25 UTC. We are working on implementing the fix for 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/feed/0D5a700001bU4YFCA0. 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 · Oct 27, 2026, 11:44 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/0D5a700001bU4YFCA0 . We will provide an update within the next 120 minutes.

    • identified · Oct 27, 2026, 02:03 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/0D5a700001bU4YFCA0 . We will provide an update within the next 120 minutes.

    • resolved · Oct 27, 2026, 03:52 PM UTC

      We can confirm that the issue was mitigated at 08:30 UTC on 27 October 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/0D5a700001bU4YFCA0 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.

    Latest: We can confirm that the issue was mitigated at 08:30 UTC on 27 October 2026, and the service has resumed normal operation. Customers and partners can view additional details about …

  2. Resolved 1d 23h
    Started Oct 21, 2026, 06:59 PM UTC · Resolved Oct 23, 2026, 06:57 PM UTC
    Edge Delivery
    Timeline · 9 updates
    • investigating · Oct 21, 2026, 06:59 PM UTC

      We are investigating an emerging issue with our Secure CDN platform with risk of impacting capacity. 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 · Oct 21, 2026, 07:33 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/0D5a700001aSoWGCA0. We will provide an update within the next 60 minutes.

    • investigating · Oct 21, 2026, 08:33 PM UTC

      We are continuing to investigate this issue. We will provide an update within the next 60 minutes.

    • identified · Oct 21, 2026, 09:29 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/0D5a700001aSoWGCA0. We will continue to provide updates as progress is made.

    • identified · Oct 21, 2026, 11:15 PM UTC

      We have identified the cause of the issue, and a fix is being implemented. We will continue to provide updates as progress is made.

    • identified · Oct 22, 2026, 12:41 AM UTC

      We continue to work on implementing a permanent fix to prevent recurrence. We can confirm that there are currently no delivery issues and that the network has remained stable since the brief impact observed at approximately 18:23 UTC. Additionally, as of 20:09 UTC, our propagation system channels are processing requests normally.We will provide our next update during the US business day on October 22.

    • identified · Oct 22, 2026, 08:51 PM UTC

      We continue to work on implementing a permanent fix to prevent recurrence. The deployment with the fix is continuing with no issues and it is expected to finalize tomorrow October 23rd during US business hours. During this time customers may experience minor instability; however, we do not anticipate any service disruptions. We are closely monitoring our systems and the deployment to ensure that there is no impact during this period.We will provide our next update during the US business day on October 23rd.

    • resolved · Oct 23, 2026, 06:57 PM UTC

      We can confirm that the issue was mitigated at 17:44 UTC on October 23, 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/0D5a700001aSoWGCA0 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.17:

    • postmortem · Oct 26, 2026, 10:45 PM UTC

      Customers and partners can find an incident summary report, here: https://community.akamai.com/customers/s/feed/0D5a700001aSoWGCA0

    Latest: Customers and partners can find an incident summary report, here: https://community.akamai.com/customers/s/feed/0D5a700001aSoWGCA0

  3. Resolved 1d 8h
    Started Oct 21, 2026, 03:30 PM UTC · Resolved Oct 22, 2026, 11:54 PM UTC
    Configuration DeploymentReportingWeb Security Analytics
    Timeline · 9 updates
    • investigating · Oct 21, 2026, 03:30 PM UTC

      We are investigating an emerging issue with Web Security Application, Reporting, and Configuration Deployment related to latency and 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/.

    • identified · Oct 21, 2026, 03:46 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/0D5a700001aPoFkCAK. We will provide an update within the next 30 minutes.

    • identified · Oct 21, 2026, 04:08 PM UTC

      We are continuing to work on a fix for this issue. Customers and partners can find more details on the Akamai Community: https://community.akamai.com/customers/s/feed/0D5a700001aPoFkCAK. We will provide an update within the next 60 minutes.

    • identified · Oct 21, 2026, 05:00 PM UTC

      We are continuing to work on a fix for this issue. Customers and partners can find more details on the Akamai Community: https://community.akamai.com/customers/s/feed/0D5a700001aPoFkCAK. We will provide an update within the next 60 minutes.

    • identified · Oct 21, 2026, 06:02 PM UTC

      Based on our observations, WSA and Reporting are working as expected. Configuration Deployments are experiencing higher latency and may take longer in the "pending" state than usual. However, these configurations will eventually be deployed to production after a longer-than-usual delay. We are continuing to work on a fix for this issue. Customers and partners can find more details on the Akamai Community: https://community.akamai.com/customers/s/feed/0D5a700001aPoFkCAK. We will provide an update within the next 60 minutes.

    • identified · Oct 21, 2026, 07:00 PM UTC

      We are continuing to work on a fix for this issue. Customers and partners can find more details on the Akamai Community: https://community.akamai.com/customers/s/feed/0D5a700001aPoFkCAK. We will provide an update within the next 60 minutes.

    • monitoring · Oct 21, 2026, 08:23 PM UTC

      We have rolled back a release that we believe may have caused this issue as of 16:42 UTC on October 21, 2026; based on current observations, the service is resuming normal operations. Additional issues related to Configuration Deployment are related to https://www.akamaistatus.com/incidents/p7jmyq5fhbfh. Customers and partners can find more details on the Akamai Community: https://community.akamai.com/customers/s/feed/0D5a700001aPoFkCAK. We will continue to monitor to ensure that the impact has been fully mitigated.

    • resolved · Oct 22, 2026, 11:54 PM UTC

      We can confirm that the issue was mitigated at 20:45 UTC on October 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/0D5a700001aPoFkCAK 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 · Oct 26, 2026, 05:32 AM UTC

      Customers and partners can find an incident summary report, here: https://community.akamai.com/customers/s/feed/0D5a700001aPoFkCAK

    Latest: Customers and partners can find an incident summary report, here: https://community.akamai.com/customers/s/feed/0D5a700001aPoFkCAK

  4. Resolved 2d 5h
    Started Oct 21, 2026, 03:03 PM UTC · Resolved Oct 23, 2026, 08:18 PM UTC
    Akamai Customer Community
    Timeline · 5 updates
    • investigating · Oct 21, 2026, 03:03 PM UTC

      Akamai is aware of the recently published remote code execution vulnerabilities CVE-2026-109618 and CVE-2026-10961). Our subject matter experts are actively investigating and taking the appropriate measures. We have released security updates to address these CVEs and monitor for exploitation attempts. We are actively monitoring our platform while we perform the mitigation actions. 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 · Oct 22, 2026, 01:44 AM UTC

      We are continuing to assess the reported vulnerabilities (CVE-2026-109618 and CVE-2026-10961) across our systems and applications. Our initial assessment has identified systems and applications that may be affected, and remediation efforts, including patching, are actively underway.At this time, we have found no evidence indicating that these vulnerabilities have impacted our products, API calls, or Control Center. We will continue to review our systems and applications to assess potential exposure and identify any additional remediation requirements.Mitigation efforts are being prioritized based on the assessment of potential risk and impact. We remain focused on addressing identified vulnerabilities and will provide further updates as additional information becomes available. We will provide further updates as we make progress.

    • identified · Oct 22, 2026, 06:15 PM UTC

      Update - We are continuing to assess the reported vulnerabilities (CVE-2026-109618 and CVE-2026-109619) across our systems and applications. Our initial assessment has identified systems and applications that may be affected, and remediation efforts, including patching, are actively underway.At this time, we have found no evidence indicating that these vulnerabilities have impacted our products, API calls, or Control Center. We will continue to review our systems and applications to assess potential exposure and identify any additional remediation requirements. Mitigation efforts are being prioritized based on the assessment of potential risk and impact. We remain focused on addressing identified vulnerabilities and will provide further updates as additional information becomes available. We will provide further updates as we make progress.

    • resolved · Oct 23, 2026, 08:18 PM UTC

      We can confirm that remediation efforts for the reported vulnerabilities, CVE-2026-109618 and CVE-2026-109619, were completed as of 20:06 UTC on October 23, 2026.We have found no evidence that these vulnerabilities impacted Akamai products, API calls, or Control Center. Customers and partners can view additional details by logging in to Control Center or contacting Akamai Support.We apologize for any concern this advisory may have caused and thank you for your patience and continued support. We remain committed to improving our systems and reducing the risk of similar issues in the future.

    • postmortem · Oct 29, 2026, 01:52 AM UTC

      Customers and partners can find an incident summary report, here: [https://community.akamai.com/customers/s/feed/0D5a700001aNd78CAC](https://community.akamai.com/customers/s/feed/0D5a700001aNd78CAC)

    Latest: Customers and partners can find an incident summary report, here: [https://community.akamai.com/customers/s/feed/0D5a700001aNd78CAC](https://community.akamai.com/customers/s/feed/0…

  5. Resolved 9h 19m
    Started Oct 21, 2026, 02:52 PM UTC · Resolved Oct 22, 2026, 12:12 AM UTC
    NetStorage
    Timeline · 4 updates
    • investigating · Oct 21, 2026, 02:52 PM UTC

      We are investigating an emerging issue with NetStorage related to performance degradation and timeouts in the Los Angeles area. 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 · Oct 21, 2026, 04:01 PM UTC

      We continue investigating this issue. Customers and partners can find more details on the Akamai Community: https://community.akamai.com/customers/s/feed/0D5a700001aOfDBCA0. We will provide an update within the next 120 minutes.

    • investigating · Oct 21, 2026, 05:56 PM UTC

      We are continuing to work 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/0D5a700001aOfDBCA0. We will provide an update as we progress.

    • resolved · Oct 22, 2026, 12:12 AM UTC

      We can confirm that the issue was mitigated at approximately 22:00 UTC on 21 October 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/0D5a700001aOfDBCA0 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.

    Latest: We can confirm that the issue was mitigated at approximately 22:00 UTC on 21 October 2026, and the service has resumed normal operation. Customers and partners can view additional …

See the full Akamai outage history

28 more incidents in the last 90 days, plus the full multi-year archive of per-service events and update timelines.

Browse Akamai outage history →

Or sign up free to get alerts when Akamai breaks · 10 free monitors · No credit card

Incident record

Since April 2026 · Statuspage by Atlassian · 42 components checked every 5 minutes
115incidents recorded
110last 12 months
33last 90 days
2 daystypical duration, 12 months

The longest incident in the last year, Certificate Provisioning System (CPS) recurrence of issues in Akamai Control Center Portal on February 11, 2026, ran for 37 days.

Most affected components, last 12 months

  • Edge Delivery44
  • Reporting12
  • Configuration Deployment9
  • TLS Provisioning (Certificates, CPS)9
  • Akamai Control Center8

Latest incidents

Outage history

Past 90 days · 33 incidents View full outage history →