Optimizely: Asset uploads failing in Optimizely CMP and DAM
Affected components: Content Marketing Platform - LibraryContent Marketing Platform - PlanContent Marketing Platform - RequestsLibraryPlanRequests
Timeline of updates
- investigating
We're aware of an issue where uploads are failing in Optimizely Content Marketing Platform (CMP) and Digital Asset Management (DAM). Users trying to upload assets may see an "Upload Error" message, and the upload won't finish.
Our Engineering team is investigating right now and is working to find the cause and restore normal upload behavior as quickly as possible.
We'll post more details on the investigation soon. We apologize for the disruption and thank you for your patience. - identified
We've identified the cause of the upload failures in Optimizely Content Marketing Platform (CMP) and Digital Asset Management (DAM).
The issue is with a third-party service provider that supports file uploads. Their service is currently rejecting upload requests from our platform, which is why users see an "Upload Error" message. Our Engineering team has already contacted the provider and is working with them to restore uploads as quickly as possible.
We don't have an estimated time for resolution yet. We'll share another update as soon as we have more information
We apologize for the disruption and thank you for your patience. - monitoring
A fix has been implemented and we're currently monitoring the results.
- resolved
This incident has been resolved.
Changes Rewindex caught on this incident
- Major incident: Asset uploads failing in Optimizely CMP and DAM
- Incident updated: Asset uploads failing in Optimizely CMP and DAM
- Incident updated: Asset uploads failing in Optimizely CMP and DAM
- Incident updated: Asset uploads failing in Optimizely CMP and DAM
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. That proves these records existed by then and have not been changed since, by anyone, Rewindex included.
How the archive is checked, and what it cannot prove.
First version captured
In the 2026-10-27 checkpoint, timestamped by DigiCert on . Record hash
f8295b6df3ff573b…Version 2 captured
In the 2026-10-27 checkpoint, timestamped by DigiCert on . Record hash
8fbad82ce5cc6e93…
Rewindex captured a newer version after the last checkpoint; the next run () commits it.
Impact, status and times are the vendor’s own, as last archived. View on status.optimizely.com (opens in new tab).