Optimizely incident

SSL trust issue causing login failures across multiple DXP environments

Major Resolved View vendor source →

Optimizely experienced a major incident on September 2, 2026 affecting Australia East and East US, lasting 7h 18m. The incident has been resolved; the full update timeline is below.

Started
Sep 02, 2026, 08:05 AM UTC
Resolved
Sep 02, 2026, 03:23 PM UTC
Duration
7h 18m
Detected by Pingoru
Sep 02, 2026, 08:05 AM UTC

Affected components

Australia EastEast US

Update timeline

  1. investigating Sep 02, 2026, 08:05 AM UTC

    We are currently investigating an SSL trust issue causing login failures across multiple DXP environments and working on mitigating actions. We will provide new updates.

  2. identified Sep 02, 2026, 08:51 AM UTC

    We continue investigating login failures affecting some DXP environments. Affected applications may receive a certificate trust error when connecting to our login service. The issue appears to affect applications running on older OS images and .NET versions earlier than .NET 8. Applications on .NET 8 or later seems not impacted based on the reports. Restarting the web application does not resolve the issue. Our engineering teams are working on a service-side resolution. Impacted regions are still being confirmed. We will continue to provide further updates.

  3. identified Sep 02, 2026, 10:26 AM UTC

    We continue to actively work on measures to restore normal operations as quickly as possible. Our investigation has identified a probable root cause, and our team is currently working to resolve it. We are closely monitoring the situation and will continue to provide updates as we make progress. Thank you for your patience and understanding.

  4. identified Sep 02, 2026, 11:35 AM UTC

    We are continuing to work on fix for this issue. We will let you know as soon we have new updates. Thank you for your patience!

  5. monitoring Sep 02, 2026, 12:15 PM UTC

    A fix has been implemented and we are monitoring the results. Thank for your patience!

  6. resolved Sep 02, 2026, 03:23 PM UTC

    The issue has been resolved and the service is now operating normally. Thank you for your patience!