Companies / Optimizely / changes

Optimizely change history

14Major incident
When (UTC)ChangeKind
Major incident: Elevated GraphQL API errors and delayed data ingestion in ODP – US region
Optimizely reported a major ODP US incident between 15:05 and 16:10 UTC on October 13, 2026: elevated GraphQL API errors and delayed ingestion. Most GraphQL requests failed; ingestion lagged up to about 65 minutes, with all accepted delayed data processed by 16:10 UTC. Recorded start/resolution: 2026-10-13 18:10 UTC; computed duration: 0 min.
Major incident
Major incident: CMP: Data Not Loading in Plan, Resources, Library, and Other Modules (GCP Stack)
Optimizely reported a major CMP outage affecting a subset of GCP-stack customers: data failed to load in Plan, Resources, Library, and other modules. The incident started at 2026-09-20 11:24 UTC and was resolved at 2026-09-20 13:08 UTC, lasting 1 h 43 min. A fix was implemented at 11:51 UTC; no cause was stated.
Major incident
Major incident: SSL trust issue causing login failures across multiple DXP environments
Optimizely reported a major SSL trust outage affecting DXP environments in Australia East and East US, preventing affected customers from logging into the CMS management interface or creating/editing content. It lasted 7 h 18 min, from 2026-09-02 08:05 UTC to 2026-09-02 15:23 UTC; Optimizely implemented a fix and confirmed normal service.
Major incident
Critical incident: CMP and DAM are inaccessible
Optimizely reported a critical CMP and DAM outage affecting all users, starting 2026-09-02 05:00 UTC and resolved at 2026-09-02 07:49 UTC, lasting 2 h 48 min. A fix was implemented by 06:44 UTC, when both products were reported accessible; sustained stability was confirmed at closure. The root cause was identified but not disclosed.
Major incident
Major incident: Netspring outage
Optimizely Analytics (Netspring) experienced a major outage affecting Netspring customers only, starting 2026-08-03 02:30 UTC and resolved at 2026-08-03 16:04 UTC, lasting 13 h 33 min. Optimizely reported identifying the underlying cause without disclosing details and confirmed service was restored to normal operation.
Major incident
Major incident: CMP: Modules are not loading in the platform
Optimizely reported a major CMP outage: the Home Page, Plan module, and Requests module failed to load for some customers. It started at 2026-07-31 17:53 UTC and was resolved at 2026-07-31 20:10 UTC, lasting 2 h 17 min. A fix was implemented; no cause was stated.
Major incident
Major incident: Login results in 429 error
Optimizely reported a major outage in which login returned 429 errors, affecting access to some products through Optimizely Identity. It started at 2026-07-23 15:26 UTC and was resolved at 2026-07-23 18:41 UTC, lasting 3 h 15 min; Optimizely attributed it to a disruption with its identity provider, Okta.
Major incident
Major incident: Campaign user interface partially unavailable
Optimizely reported a major partial outage of Campaign’s graphical interfaces for managing campaigns and content, including the EMEA Region interface, affecting only some users. It started at 2026-07-17 16:59 UTC and was marked resolved at 2026-07-17 17:17 UTC; the computed duration was 17 min. The vendor identified the affected component and resolved the problem.
Major incident
Major incident: Email Campaign Delivery Drops — NA Region
Optimizely reported a major degradation dropping some email campaign messages in the NA Region from 2026-06-17 14:00 UTC to 2026-06-20 17:41 UTC, lasting 3 days 3 h. Optimizely cited a likely SendGrid header-processing incompatibility and deployed a fix; it lacked records identifying which recipients received messages, complicating decisions about rerunning affected campaigns.
Major incident
Major incident: CMP: Modules are inaccessible
Optimizely reported a major CMP outage making Plan, Requests, Library / DAM and Analytics inaccessible to customers. It started at 2026-06-16 07:04 UTC and was resolved at 2026-06-16 08:52 UTC, lasting 1 h 48 min; a fix was implemented by 07:32 UTC.
Major incident
Major incident: CMP: Modules are inaccessible
Optimizely reported a major CMP outage: Plan, Requests, and Library / DAM were inaccessible to customers. The incident started at 2026-06-10 11:49 UTC and lasted 7 h 31 min, resolving at 2026-06-10 19:20 UTC; a fix was implemented by 06-10 12:31 UTC, followed by monitoring.
Major incident
Major incident: Investigating – Content Recommendation Service Degradation in EMEA region
Optimizely’s Content Recommendations API in EMEA could not serve recommendations during a major-impact incident from 2026-06-02 07:48 UTC to 2026-06-02 12:25 UTC, lasting 4 h 36 min. Users could see missing or unavailable recommendations across the platform. Optimizely reported an API disruption, implemented a fix at 08:51 UTC, and confirmed resolution.
Major incident
Critical incident: Flags permission issue.
Optimizely reported a critical flags permission issue affecting Application UI and Optimizely REST API, including Feature Experimentation. It started at 2026-05-20 09:42 UTC and was resolved at 2026-05-20 11:30 UTC, lasting 1 h 48 min; a fix was implemented at 10:10 UTC, but no cause or specific customer impact was stated.
Major incident
Major incident: CMP: Some Home Page Sections & Requests Module Displaying No Data
Optimizely reported a major CMP outage: Requests and the Home Page’s My Work, My Team’s Work, and Watching sections appeared empty for a subset of customers. It started at 2026-05-18 09:20 UTC and resolved at 2026-05-18 10:54 UTC, lasting 1 h 33 min. A fix was implemented at 09:41 UTC; no cause was stated.
Major incident