Skip to content

Incident detail

Edge Delivery Issues With OpenJDK

Edge Delivery Issues With OpenJDK

Resolved incidentMinor1 affected service

Timeline window

to

Timeline

Incident updates

Updates are normalized from the official source chronology so timeline changes remain easy to scan.

  1. Investigating

    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/.

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

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

  4. Investigating

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

  5. Investigating

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

  6. Investigating

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

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

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

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

  11. Resolved

    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.