- Level
- confirmed
- Worst impact
- Degraded
- Components
- Library, Open API
- Down Index
- 21of 100
What to do
Check whether you use Optimizely Library, Open 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 5h 17m it lasted.
Anything that failed between 2026-06-08 09:27 UTC and 2026-06-08 14:44 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 issue affecting customers hosted on the GCP stack. Starting this morning, calls to the DAM REST API endpoint 'GET /v3/assets/{asset_id}/renditions' appear to be returning a 500 Internal Server Error. As a result, configured image renditions (used for cropping and scaling images across channels) are not being served. Affected customers will see only the original/main asset image in place of their configured renditions. The rendition configuration UI in CMP Settings > Assets also appears to be impacted, with rendition setups failing to load correctly. Affected: Optimizely Content Marketing Platform (CMP) – DAM / Asset Renditions Infrastructure: GCP-hosted customers only Impact: Image renditions unavailable; 'GET /v3/assets/{asset_id}/renditions' returning 500 We are actively investigating the root cause and will provide an update soon.
provider
- monitoring
A fix has been implemented for the issue affecting DAM asset renditions on the GCP stack. We are actively monitoring the situation to confirm full stability. If you are still experiencing issues, please contact Optimizely Technical Support Services for assistance. We will provide a final update once the incident is fully resolved.
provider
- resolved
This incident has been resolved.
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-bcaa439e7a
Is Optimizely still down?
No, this incident was resolved 2026-06-08 14:44 UTC. For Optimizely's live state, see https://down.guide/optimizely.
How long did it last?
5h 17m, from 2026-06-08 09:27 UTC to 2026-06-08 14:44 UTC, by the times Optimizely posted.
What was affected?
Optimizely named Library, Open 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.