Skip to main content
Optimizely

SSL trust issue causing login failures across multiple DXP environments

Partial outage Lasted 7h 18m · started · Optimizely's page

Level
confirmed
Worst impact
Partial outage
Components
Australia East, East US
Regions
au, us
Down Index
40of 100

What to do

  • Check whether you use Optimizely Australia East, East US in au, us. Check your stack

    Paste a package.json, lockfile, Terraform or a list of domains at down.guide/stack to see every provider you depend on.
  • Confirm your retries, queues and scheduled jobs caught up after the 7h 18m it lasted.

    Anything that failed between 2026-09-02 08:05 UTC and 2026-09-02 15:23 UTC may need a replay.
  • Subscribe to Optimizely's feed to hear about the next one first. RSS feed

    https://down.guide/feed?provider=optimizely works in Slack (/feed subscribe), Discord feed bots and any RSS reader.

Updates from Optimizely 6

  1. investigating

    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.

    provider

  2. identified

    We continue investigating login failures affecting some DXP environments. Affected applications may receive a certificate trust error when connecting to our login service. Affected customers cannot log in to the CMS management interface and are currently unable to create or edit content. 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.

    provider

  3. identified

    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.

    provider

  4. identified

    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!

    provider

  5. monitoring

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

    provider

  6. resolved

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

    provider

Reports count in aggregate; nothing about you is shown.

Corrections

None so far.

Something wrong on this page? Report an error or send us a note. Every fix is listed here.

Questions about DWN-000b8d6270

Is Optimizely still down?

No, this incident was resolved 2026-09-02 15:23 UTC. For Optimizely's live state, see https://down.guide/optimizely.

How long did it last?

7h 18m, from 2026-09-02 08:05 UTC to 2026-09-02 15:23 UTC, by the times Optimizely posted.

What was affected?

Optimizely named Australia East, East US in au, us.

What caused it?

Optimizely hasn't published a root cause. If it does, it shows here.

Where does this come from?

Optimizely's official status page, https://status.optimizely.com, quoted verbatim. down.guide's own probes, reports and social counts are labeled as ours.