- Level
- confirmed
- Worst impact
- Degraded
- Regions
- us
- Down Index
- 12of 100
What to do
Check whether you use Optimizely in 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 0m it lasted.
Anything that failed between 2026-06-09 08:34 UTC and 2026-06-04 08:00 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 1
- resolved
A partial outage affected OCP Job Scheduler, where scheduled jobs across multiple apps failed to execute due to an expired certificate in the env‑injector mutating webhook, in the US region only. This prevented required environment variables from being injected into workloads, causing job failures. Non-job features (e.g., configuration, webhooks) remained functional. No data loss occurred, and all affected jobs caught up after the issue was resolved, though customers may have experienced delays (e.g., stale audience syncs)
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-ee1d267a86
Is Optimizely still down?
No, this incident was resolved 2026-06-04 08:00 UTC. For Optimizely's live state, see https://down.guide/optimizely.
How long did it last?
0m, from 2026-06-09 08:34 UTC to 2026-06-04 08:00 UTC, by the times Optimizely posted.
What was affected?
Optimizely named in 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.