Optimizely Outage History

We are currently investigating an issue affecting customers hosted on the AWS stack. Customers are experiencing failures when attempting to create tasks within the Optimizely Content Marketing Platform (CMP). Affected: Optimizely Content Marketing Platform (CMP) – Task Creation Infrastructure: AWS-hosted customers only Impact: Task creation failing Our Engineering team is actively working on a solution. We will share more information on this incident soon.

We are currently investigating an incident affecting multiple modules within the Optimizely Content Marketing Platform (CMP). The following modules are currently inaccessible to customers: - Plan - Requests - Library / DAM - Analytics Our Engineering team is actively working on a resolution. We will provide a further update as soon as more information is available.

We are aware of an ongoing incident with one of our third party vendors that could cause site management-related API calls to fail and/or errors to be displayed. CDN cached traffic and security features are not impacted. We will continue to monitor the situation along with our vendor and will continue to post updates here as they become available.

We are currently investigating an issue affecting customers hosted on the GCP stack. Starting this morning, calls to the DAM REST API endpoint 'GET /v3/assets/{asset_id}/renditions' appear to be returning a 500 Internal Server Error. As a result, configured image renditions (used for cropping and scaling images across channels) are not being served. Affected customers will see only the original/main asset image in place of their configured renditions. The rendition configuration UI in CMP Settings > Assets also appears to be impacted, with rendition setups failing to load correctly. Affected: Optimizely Content Marketing Platform (CMP) – DAM / Asset Renditions Infrastructure: GCP-hosted customers only Impact: Image renditions unavailable; 'GET /v3/assets/{asset_id}/renditions' returning 500 We are actively investigating the root cause and will provide an update soon.

We are currently investigating an issue affecting the Content Recommendation service in EMEA region. Due to an API disruption, we are unable to serve recommendations at this time. Users may notice missing or unavailable recommendations across the platform. Our team is actively investigating the issue and working to restore full functionality as quickly as possible. We will provide updates as more information becomes available. Thank you for your patience!

We are currently investigating the issue.

We are continuing to investigate this issue.

We are currently investigating a reported issue affecting the 'Requests' module, as well as the 'My Work', 'My Team's Work', and 'Watching' sections on the Home Page, which are appearing empty for a subset of customers. Our Engineering team is actively working on a resolution, and we hope to share further information on this matter shortly.

We are experiencing intermittent availability issue for the Optimizely Graph service, for one of the USEA production clusters. Our team is working on mitigating actions. We'll provide new updates.

We are currently aware of an active incident with Cloudflare that is affecting authoritative resolution for the .de TLD. We are continuing to investigate and correspond with Cloudflare to push for rapid mitigation.

We have identified an intermittent issue impacting Content Recommendations dashboard. Currently, a part of requests to the reporting dashboard may fail for a subset of customers. This incident is confined to the administrative dashboard only. End-user delivery, including recommendations and widgets, remains fully operational. We are working toward a resolution and appreciate your patience. New updates will be shared when available.

We are investigating an issue where changes to Web Experimentation projects may experience delays when publishing. Our team is actively working on a resolution.

We are investigating the problem with using GraphQL and the Segment API in the AU region.

We are currently investigating a potential issue that may be impacting DXP service. This appears to be related to an event experienced by one of our third-party suppliers. We are in close contact with their team and working diligently to understand the scope and impact of this situation. Currently one customer is identified as impacted. We will provide updates as soon as more information becomes available. Thank you for your patience and understanding.

We are continuing to investigate the issue. Currently one customer is identified as impacted. We will provide updates as soon as more information becomes available. Thank you for your patience and understanding!

We are currently investigating an issue in Web Experimentation that is preventing some users from updating Shared Code or Variation Code with long custom code solutions.

We are currently investigating an issue affecting the visibility of assets within CMP DAM for a subset of customers. This includes assets uploaded directly as well as those added through task completion. Our Engineering team is actively working to identify the root cause and restore normal functionality as quickly and safely as possible. We will continue to provide updates here as more information becomes available. Thank you for your patience while we work to resolve this matter.

We are currently investigating an event that is impacting the availability on the Search & Navigation (FIND) service in the US East region. A subset of clients will be experiencing high latency or 5xx-errors. The issue is currently limited to development indices. We will share additional updates if the scope changes or as soon as more information becomes available. Thank you for your patience.

A part of the emails for recipients addressed to gmail.com and gmx.de are delivered with a delay. (Emails won't be lost.) We are currently investigating.

We've rerouted emails from the impacted part of our sending infrastructure to the not impacted part. New emails shouldn't be delayed anymore, but queued emails still need to be processed. We're still looking for the underlying cause of the delay.

We are currently investigating an ongoing intermittent issue with CMS Headless deployments, wherein some customers may encounter a site is blocked error. We will provide additional updates as soon as they become available. Thank you for your patience!