Optimizely: Update on Configured Commerce incident (November 19th 2026)
Affected components: Configured Commerce – APAC RegionConfigured Commerce – EMEA RegionConfigured Commerce – NA Region
Timeline of updates
- monitoring
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.
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.
Rewindex captured this 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).
Cite this
Status incident (vendor impact label: none) posted by Optimizely, started 2026-11-21 00:35 UTC, not resolved, 1 update(s).
- Title
- Update on Configured Commerce incident (November 19th 2026)
- Vendor
- Optimizely
- Date
- URL
- https://rewindex.com/company/optimizely/incidents/qyy4qsvxpp66
Optimizely profileRecent Optimizely incidentsAll outages on November 21, 2026Optimizely in November 2026MarkdownJSON