- Level
- confirmed
- Worst impact
- Maintenance
- Components
- Australia East, North Europe, Canada East, Australia Southeast, West Europe, Canada Central, Japan East, Norway East, East US, Southeast Asia, Sweden Central, East US 2, UK South, North Central US, UAE North, West US, West US 2
- Regions
- apac, au, ca, eu, jp, me, us
Summary
Optimizely says it is disabling TLS 1.0 and 1.1 on its apex domain redirect service in batches, during daily 8:00 to 12:00 UTC windows from October 29 to November 6, 2026, leaving only TLS 1.2 and newer. Its latest update, at 08:00 UTC on October 29, says maintenance is in progress, and the incident is marked resolved.
Written by anthropic/claude-haiku-5.5 from Optimizely's own updates.
What to do
Check whether you use Optimizely Australia East, North Europe, Canada East, Australia Southeast and 13 more in apac, au, ca, eu. 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.Check that everything you run on Optimizely came back after the window closed 2026-11-06 09:00 UTC.
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 3
- scheduled
Schedule: * Date range: October 29, 2026 - November 6, 2026 * Daily window: 8:00 UTC - 12:00 UTC Between October 29, 2026 and November 6, 2026, we will be performing scheduled maintenance to enhance our TLS security configuration. During this period, maintenance will be conducted daily between 8:00 UTC and 12:00 UTC. As part of this update, we will be disabling TLS 1.0 and TLS 1.1 on our apex domain redirect service in batches. Following this change, only TLS 1.2 and newer protocol versions will be supported. Who is affected? This change only affects customers whose clients connect to apex domain redirects using the deprecated TLS 1.0 or 1.1 protocols. Modern browsers and standard HTTP clients already use TLS 1.2 or later and will continue to function without interruption. Action required: Customers with integrations or monitoring tools connecting to apex domains over HTTPS should verify if these clients support TLS 1.2 or newer. Most modern tools already meet this requirement. We apologize for any inconvenience this may cause, and appreciate your collaboration during this transition as we continue to improve our services. Please don't hesitate to contact the Optimizely Support Team (support@optimizely.com) for additional assistance or questions.
provider
- scheduled
Maintenance will begin as scheduled in 60 minutes.
provider
- in_progress
Scheduled maintenance is currently in progress. We will provide updates as necessary.
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-53ec84ba9b
Is this Optimizely maintenance still going on?
No, it ended 2026-11-06 09:00 UTC.
How long did it last?
8d 1h, from 2026-10-29 08:00 UTC to 2026-11-06 09:00 UTC, by the times Optimizely posted.
What was affected?
Optimizely named Australia East, North Europe, Canada East, Australia Southeast and 13 more in apac, au, ca, eu.
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.