- Level
- confirmed
- Worst impact
- Degraded
- Components
- US West
- Regions
- us
What to do
Check whether you use Optimizely US West 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 1h 58m it lasted.
Anything that failed between 2026-07-09 18:39 UTC and 2026-07-09 20:38 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 3
- investigating
We are currently investigating an event that is impacting the availability on the Search & Navigation (FIND) service in the US West region. A subset of clients will be experiencing high latency or 5xx-errors and failed requests. We will continue to provide updates as they become available. Thank you for your patience.
provider
- identified
The issue has been identified and a fix is being implemented.
provider
- resolved
The incident has been resolved as the service has fully recovered and is stable.
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-c53c76be70
Is Optimizely still down?
No, this incident was resolved 2026-07-09 20:38 UTC. For Optimizely's live state, see https://down.guide/optimizely.
How long did it last?
1h 58m, from 2026-07-09 18:39 UTC to 2026-07-09 20:38 UTC, by the times Optimizely posted.
What was affected?
Optimizely named US West 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.