Update on Configured Commerce incident (November 19th 2026)
Nov 21, 00:35 UTCOngoing
Duration
Ongoing
Impact
Informational
Root cause
Not disclosed
Optimizely, 90 days
28 incidents
Affected
Configured Commerce – APAC RegionConfigured Commerce – EMEA RegionConfigured Commerce – NA Region
Final update
Between 10 and 12 November 2026, an unauthorized third party gained access to a legacy Configured Commerce build and deployment server that we were in process of retiring. Optimizely detected the activity on 12 November 2026, removed an injected script (on two sites only), and permanently shut down the compromised server. We have secured our environment and are processing forensics. This incident is unrelated to the Experimentation incident. Independent third-party experts are helping with our ongoing investigation, and we're confident in the extra safeguards we've put in place to protect Configured Commerce.
Timeline
- Monitoring · Nov 21, 00:35 UTC
Between 10 and 12 November 2026, an unauthorized third party gained access to a legacy Configured Commerce build and deployment server that we were in process of retiring. Optimizely detected the activity on 12 November 2026, removed an injected script (on two sites only), and permanently shut down the compromised server. We have secured our environment and are processing forensics. This incident is unrelated to the Experimentation incident. Independent third-party experts are helping with our ongoing investigation, and we're confident in the extra safeguards we've put in place to protect Configured Commerce.
More from Optimizely
Full historyWeb Experimentation Security Incidentstill openPartial Outage Affecting Recommendations Tracking and Reportinglasted 27h 11mConfigured Commerce - Mission Control service degredationlasted 2d 21hSlow loading and performance issues in Content Marketing Platform (CMP)lasted 2h 28mOptimizely E-Mail Support Outagelasted 39h 5mOptimizely Graph in EMEA - Intermittent performance issueslasted 4h 17m