- Level
- confirmed
- Worst impact
- Degraded
- Components
- E-mail dispatch
- Down Index
- 21of 100
What to do
Check whether you use Optimizely E-mail dispatch. 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 4h 21m it lasted.
Anything that failed between 2026-08-04 13:11 UTC and 2026-08-04 17:32 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 4
- investigating
We are currently investigating an issue with degraded performance for email dispatch.
provider
- investigating
The problem has been identified and a partial workaround has been applied. We are still working on a full solution.
provider
- monitoring
The problem has been resolved. Unfortunately the Online Versions were impacted between 17:30 and 18:00 CEST as well. We are now monitoring the system.
provider
- resolved
No further problems have been observed.
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-a60c05f073
Is Optimizely still down?
No, this incident was resolved 2026-08-04 17:32 UTC. For Optimizely's live state, see https://down.guide/optimizely.
How long did it last?
4h 21m, from 2026-08-04 13:11 UTC to 2026-08-04 17:32 UTC, by the times Optimizely posted.
What was affected?
Optimizely named E-mail dispatch.
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.