- Level
- confirmed
- Worst impact
- Degraded
- Components
- Application UI, App UI, Optimizely REST API
- Down Index
- 8of 100
What to do
Check whether you use Optimizely Application UI, App UI, Optimizely REST API. 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-22 13:03 UTC and 2026-06-22 13:03 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
We have resolved an issue that was resulting in some users receiving errors in the application and configuration-related REST APIs (500 or 502 status codes). There was no impact to experiment execution or ingestion related to the issue.
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-3d23722415
Is Optimizely still down?
No, this incident was resolved 2026-06-22 13:03 UTC. For Optimizely's live state, see https://down.guide/optimizely.
How long did it last?
0m, from 2026-06-22 13:03 UTC to 2026-06-22 13:03 UTC, by the times Optimizely posted.
What was affected?
Optimizely named Application UI, App UI, Optimizely REST API.
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.