Some Systems Operational
← All services

Optimizely

Developer Tools

Official status page ↗

Source: status.optimizely.com · last checked

Active incidents 1

NoticeMonitoring · started

Web Experimentation Security Incident

  1. Monitoring

    On 16 November 2026, an unauthorized third party exploited a flaw in the Optimizely Web Experimentation account signup flow. They used it to impersonate users on targeted customer accounts and insert malicious JavaScript into those customers’ projects. On the day the activity began, we detected it, blocked delivery of the malicious code and closed the vulnerability within three hours of detection. We also removed the injected code from all affected projects. No malicious code remains in our systems. This was not a credentials breach. The incident was limited to Web Experimentation. Less than 5% of our customers were impacted. No other Optimizely product was affected. We have contacted every Web Experimentation customer directly to confirm whether they were affected. If you do not use Web Experimentation, you do not need to do anything. If you do, we have completed remediation and have provided additional guidance. The security of your data and the trust you place in us are our highest priority. Optimizely’s platform is protected by layered security controls, continuous monitoring and a dedicated security team, which is why we could detect and contain this incident on the day it began. Attackers are increasingly using AI to find and exploit weaknesses easier, faster and at greater scale, and we are responding to that. We are strengthening our security strategy, hardening systems and using the latest in AI capabilities to counter the sophistication of attackers.

  2. Monitoring

    Earlier today, Optimizely identified a security incident in which an unauthorized party exploited a vulnerability in Experimentation and used it to add malicious JavaScript to some customer projects. We've fixed the vulnerability and removed the injected code from affected projects. We've also taken steps to secure affected user accounts and put additional protections in place to prevent unauthorized code from being delivered.

History

24 incidentsin the last 90 days
90 days agoToday

Components 141

All 141 components are operational.

Past incidents 24

Minor
· lasted 39h 5m
Critical
· lasted 15h 22m
Major
· lasted 1h 32m
Minor
· lasted 3h 19m
Minor
· lasted 12h 30m
Minor
· lasted 3h 4m
Minor
· lasted 17m
Minor
· lasted under a minute
Minor
· lasted 23m
Minor
· lasted 21h 38m
Minor
· lasted 2h 49m
Critical
· lasted 4h 9m
Minor