Optimizely Outage History

Optimizely's Content Recommendations dashboard experienced intermittent issues in the APAC region, causing some reporting dashboard requests to fail for a subset of customers over 1.7 hours. The incident was limited to the administrative dashboard only, while end-user delivery of recommendations and widgets continued operating normally. The issue was resolved after implementing a fix and monitoring the results.

Optimizely experienced a 1.4-hour incident where Web Experimentation project changes faced publishing delays, with some experiments stuck in a processing state. The issue affected the Snippet Building component, causing a backlog of pending changes in the publishing queue. The problem was identified and resolved, with the publishing queue actively processing the backlog and affected experiments completing automatically.

Optimizely's Data Platform experienced issues with GraphQL and Segment API functionality in the AU region, affecting the ODP Application and Data Ingestion and Processing components. The incident lasted 12.9 hours before a fix was implemented and the service was restored to normal operation.

Optimizely's Events Export API experienced an issue causing some requests to return errors, specifically affecting the ability to generate temporary export credentials. Event data collection remained unaffected throughout the incident. The root cause was identified and resolved after 2.7 hours of downtime.

A Cloudflare outage caused image loading and uploading failures across Optimizely's CMP and DAM services, along with inconsistent behavior in public links. The incident affected the Library, Plan, and Requests components for 9.4 hours. The Product Development Engineering team implemented a fix that restored normal image functionality and public link behavior.

Optimizely's DXP service in Sweden Central experienced a partial availability issue caused by a third-party supplier problem, affecting one customer who experienced intermittent site responses. The third-party supplier worked to restore service stability while Optimizely monitored the situation closely. The incident was resolved after 2.2 hours with confirmed service stability.

Optimizely's Search & Navigation (FIND) service in the US West region experienced unstable performance for 3.3 hours, causing a subset of clients to encounter high latency, 5xx errors, and failed requests. The issue was identified as impacting only a minor subset of customers and was subsequently fixed. The service was fully resolved with no further impacts observed and all systems returned to normal operation.

Optimizely's Web Experimentation service experienced an issue where users were unable to update Shared Code or Variation Code when using long custom code solutions, affecting the Snippet Building component. The problem was caused by a validation limitation that prevented longer custom code from being applied to experiments and campaigns, which was addressed and resolved after 1.3 hours.