Optimizely: Content Marketing Platform (CMP) Library: Asset Visibility in CMP DAM
Timeline of updates
- resolved
This incident has been fully resolved, and the service has been operating normally since the fix was implemented. The root cause was traced to an anomalous use-case for a particular CMP instance, where our assets database faced an unusual amount of load (500k asset lineage entries for a particular asset) causing delays in data replication in our Elasticsearch instances which resulted in uploaded assets not being visible, as well as slowness/504 errors in our asset public API endpoints. We have taken corrective actions and are implementing additional preventive measures to reduce the likelihood of similar incidents occurring in the future.
From Optimizely’s published incident history: for incidents before Rewindex began polling this status page, only the final update text is available.
Archive proof
Rewindex commits each version of an incident it captures to a daily checkpoint, chains it to the day before, and has the checkpoint timestamped by FreeTSA and DigiCert.
How the archive is checked, and what it cannot prove.
This incident predates live tracking (October 17, 2026). It came from the vendor’s own published history, which is not covered by checkpoints.
Impact, status and times are the vendor’s own, as last archived. View on status.optimizely.com (opens in new tab).
Cite this
Status incident (vendor impact label: minor) posted by Optimizely, started 2026-01-02 11:43 UTC, resolved after 46 h, 1 update(s).
- Title
- Content Marketing Platform (CMP) Library: Asset Visibility in CMP DAM
- Vendor
- Optimizely
- Date
- URL
- https://rewindex.com/company/optimizely/incidents/v1pdhgcsbmx2
Optimizely profileRecent Optimizely incidentsAll outages on January 2, 2026Optimizely in January 2026MarkdownJSON