Optimizely

Affected: Snippet Building

Failure mode: Exhausted memory, disk, CPU, queues, connection pools or quotas. Root cause: Not enough capacity for the load. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-10-15 10:35 UTC

   We are investigating an issue causing delays when publishing experiments and other changes. Customers may see deployments remain in an "Uploading to CDN" state longer than expected before becoming available. Existing experiences continue to serve normally. Our engineering team...

2. identified 2026-10-15 12:00 UTC

   We have identified the cause of the delayed publishing issue. A surge in snippet upload activity created a backlog in our processing queue, which resulted in extended "Uploading to CDN" times for some customers. Mitigation actions have been taken to stop the source of the...

3. resolved 2026-10-15 13:39 UTC

   We have resolved the issue that caused delayed publishing and extended "Uploading to CDN" times for some customers. Publishing requests are now processing normally. The issue was caused by a temporary backlog in snippet upload processing, which has been cleared. We apologize for...

Excerpts are shortened. Read the full incident on Optimizely's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. resolved 2026-10-13 18:10 UTC

   Between 15:05 and 16:10 UTC on October 13, 2026, Data Platform customers in the US region experienced delayed data ingestion and elevated error rates on the GraphQL API. From about 15:20 to 16:07 UTC, most GraphQL API requests failed with HTTP 5xx errors or timeouts. Ingestion...

Excerpts are shortened. Read the full incident on Optimizely's status page.

Affected: Optimizely Graph - APAC Region, Optimizely Graph - EMEA Region, Optimizely Graph - NA Region, Optimizely Graph - UAEN Region

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-10-09 13:24 UTC

   We have identified an issue affecting Content Graph. When content is published, cache eviction and webhook processing are not completing as expected. As a result, queries to Graph may return outdated content. Our team is actively investigating and we will provide an update as...

2. resolved 2026-10-09 13:41 UTC

   The cache eviction and webhook delivery issues impacting Content Graph have been resolved. Stale content is no longer being served, and publishing workflows have returned to normal operation.

Excerpts are shortened. Read the full incident on Optimizely's status page.

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. resolved 2026-10-06 17:00 UTC

   We're seeing delays in processing incoming data in the EU region. Campaigns that depend on recent data may be delayed or may not send. A fix is in place and data processing is back to normal. We're watching to make sure it stays stable.

Excerpts are shortened. Read the full incident on Optimizely's status page.

Affected: Optimizely Graph - APAC Region, Optimizely Graph - EMEA Region, Optimizely Graph - NA Region, Optimizely Graph - UAEN Region

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. monitoring 2026-09-30 13:57 UTC

   We have identified the root cause and applied a mitigation. The service has returned to normal operation and we are actively monitoring to confirm stability.

2. resolved 2026-09-30 18:07 UTC

   This incident has been resolved as the service has remained healthy and stable since the mitigation was applied.

Excerpts are shortened. Read the full incident on Optimizely's status page.

Affected: Optimizely Graph - NA Region

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-09-23 14:21 UTC

   We are experiencing intermittent availability issue for the Optimizely Graph service impacting one of the USEA production clusters. Our team is working on mitigating actions.

2. monitoring 2026-09-23 14:46 UTC

   We have identified the root cause and applied a mitigation. The service has returned to normal operation and we are actively monitoring to confirm stability.

3. resolved 2026-09-23 17:13 UTC

   The service has remained stable. The issue is now considered resolved.

Excerpts are shortened. Read the full incident on Optimizely's status page.

Affected: Library, Plan, Requests, Analytics

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

Names an upstream provider: Google Cloud.

1. investigating 2026-09-20 11:24 UTC

   We are currently investigating an issue affecting the Optimizely Content Marketing Platform (CMP), where data is failing to load across multiple modules — including Plan, Resources, and Library — for a subset of customers on the GCP stack. Our Engineering team has been engaged...

2. identified 2026-09-20 11:29 UTC

   The issue has been identified and a fix is being implemented

3. monitoring 2026-09-20 11:51 UTC

   A fix has been implemented and we're now monitoring the results.

4. resolved 2026-09-20 13:08 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Optimizely's status page.

Affected: Optimizely Identity

Failure mode: Login, tokens, certificates or credentials failed. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-09-17 22:23 UTC

   We are currently investigating this issue.

2. identified 2026-09-17 22:24 UTC

   The issue has been identified, and a fix is being implemented.

3. monitoring 2026-09-17 22:26 UTC

   A fix has been implemented, and we are monitoring the results.

4. resolved 2026-09-17 22:26 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Optimizely's status page.

Affected: Campaign E-Mail Submission via SMTP

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. identified 2026-09-16 08:33 UTC

   Starting around 10:00 CEST processing of emails submitted via our SMTP API is delayed. We already identified the underlying problem and are in the process of fixing the issue.

2. resolved 2026-09-16 08:56 UTC

   The issue has been fixed and all delayed emails have been processed.

Excerpts are shortened. Read the full incident on Optimizely's status page.

Affected: Analytics

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

Names an upstream provider: AWS.

1. identified 2026-09-08 07:34 UTC

   Customers on the AWS stack using the CMP Analytics module may notice that analytics data from September 3, 2026 to present is not visible in their dashboards. This is a display issue only — all data has been safely recorded and will be backfilled once the fix is deployed.

2. monitoring 2026-09-08 18:40 UTC

   Analytics data should be visible in the CMP Analytics module. We are in an active monitoring phase to confirm full data restoration across all affected AWS stack customers. A final resolution update will be posted once monitoring is complete. If you are still not seeing...

3. resolved 2026-09-09 05:12 UTC

   The issue has been resolved.

Excerpts are shortened. Read the full incident on Optimizely's status page.

Affected: Australia East, East US

Failure mode: Login, tokens, certificates or credentials failed. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-09-02 08:05 UTC

   We are currently investigating an SSL trust issue causing login failures across multiple DXP environments and working on mitigating actions. We will provide new updates.

2. identified 2026-09-02 08:51 UTC

   We continue investigating login failures affecting some DXP environments. Affected applications may receive a certificate trust error when connecting to our login service. Affected customers cannot log in to the CMS management interface and are currently unable to create or edit...

3. identified 2026-09-02 10:26 UTC

   We continue to actively work on measures to restore normal operations as quickly as possible. Our investigation has identified a probable root cause, and our team is currently working to resolve it. We are closely monitoring the situation and will continue to provide updates as...

4. identified 2026-09-02 11:35 UTC

   We are continuing to work on fix for this issue. We will let you know as soon we have new updates. Thank you for your patience!

5. monitoring 2026-09-02 12:15 UTC

   A fix has been implemented and we are monitoring the results. Thank for your patience!

6. resolved 2026-09-02 15:23 UTC

   The issue has been resolved and the service is now operating normally. Thank you for your patience!

Excerpts are shortened. Read the full incident on Optimizely's status page.

Affected: Library, Plan, Requests, Open API, Analytics

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-09-02 05:00 UTC

   The CMP and DAM products are currently experiencing a critical service disruption affecting all users. Our Engineering teams have been engaged and are actively working to restore service with the highest priority. We understand the severity of this impact and sincerely apologize...

2. identified 2026-09-02 05:20 UTC

   Our Engineering teams have identified the root cause of the disruption affecting CMP and DAM. A fix is being actively implemented, and restoring full service remains our highest priority. We will provide a further update as soon as service has been restored. We apologize for the...

3. monitoring 2026-09-02 06:44 UTC

   A fix has been implemented and we're currently monitoring the results. Both products should now be accessible.

4. resolved 2026-09-02 07:49 UTC

   CMP and DAM are fully operational. Our Engineering teams have confirmed sustained stability following remediation, and this incident is now closed. We apologize for the disruption and thank you for your patience.

Excerpts are shortened. Read the full incident on Optimizely's status page.

Affected: Singapore, Australia East, Australia East

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. investigating 2026-08-25 05:15 UTC

   A subset of Optimizely customers may experience connectivity issues or service degradation in the Southeast Asia region due to a network connectivity issue reported by our third-party provider. We will provide additional updates as soon as they become available. Thank you for...

2. monitoring 2026-08-25 06:58 UTC

   The third‑party provider has mitigated the issue. We are monitoring the results.

3. resolved 2026-08-25 07:37 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Optimizely's status page.

Affected: Library

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-08-24 06:53 UTC

   We are investigating reports of assets not appearing in the DAM following a successful upload in CMP. Our Engineering team is actively working to determine the cause and scope of impact. Uploaded assets are not believed to be lost — we will confirm this as the investigation...

2. monitoring 2026-08-24 08:20 UTC

   A fix has been implemented and we're currently monitoring the results.

3. resolved 2026-08-24 11:01 UTC

   The incident has been resolved.

Excerpts are shortened. Read the full incident on Optimizely's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-08-14 02:38 UTC

   We're investigating DXP multiple environments returning error 503 - affecting only non-production environments.

2. identified 2026-08-14 03:06 UTC

   Our Engineering team has identified the root cause and is actively working on a resolution.

3. identified 2026-08-14 05:15 UTC

   We are implementing the fix and have confirmed the impact affects a limited subset of clients.

4. resolved 2026-08-14 08:39 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Optimizely's status page.

Affected: Library, Plan, Requests

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. identified 2026-08-12 10:38 UTC

   We have identified a platform-wide issue affecting PDF file preview generation within the Content Marketing Platform (CMP). Users attempting to preview PDF assets in the Library may encounter an error and be unable to view document previews. Our Engineering team has identified...

2. monitoring 2026-08-12 13:13 UTC

   A fix has been implemented and we are monitoring the results.

3. resolved 2026-08-12 16:03 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Optimizely's status page.

Affected: Tracking, Online versions of mailings, Hosting of images and files

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-08-06 15:04 UTC

   We are currently investigating an issue with degraded performance for image delivery, processing of tracking requests and delivery of online version.

2. identified 2026-08-06 15:09 UTC

   We have put a mitigation at place, so the mentioned services should be fully available again. The problem started around 16:38 CEST. Mitigation was activated at 17:00 CEST. We are continuing to our investigation.

3. monitoring 2026-08-06 15:51 UTC

   The performance problems didn't show up again. The mitigation is no longer needed and will be removed. We are still monitoring.

4. resolved 2026-08-06 16:28 UTC

   Systems are running stable with the mitigation removed. The incident has been resolved.

Excerpts are shortened. Read the full incident on Optimizely's status page.

Affected: E-mail dispatch

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-08-04 13:11 UTC

   We are currently investigating an issue with degraded performance for email dispatch.

2. investigating 2026-08-04 13:27 UTC

   The problem has been identified and a partial workaround has been applied. We are still working on a full solution.

3. monitoring 2026-08-04 16:08 UTC

   The problem has been resolved. Unfortunately the Online Versions were impacted between 17:30 and 18:00 CEST as well. We are now monitoring the system.

4. resolved 2026-08-04 17:32 UTC

   No further problems have been observed.

Excerpts are shortened. Read the full incident on Optimizely's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-08-03 02:30 UTC

   We are currently investigating an issue affecting our Netspring service (Netspring customers only). We will continue to provide timely updates as they become available.

2. investigating 2026-08-03 13:46 UTC

   We are continuing to investigate the issue. Thank you for your patience!

3. identified 2026-08-03 14:11 UTC

   We have identified the underlying cause of the issue affecting the Netspring service and are actively working toward resolution. We will continue to provide timely updates on our progress as they become available.

4. resolved 2026-08-03 16:04 UTC

   The issue affecting the Netspring service has been resolved, and service has been restored to normal operation.

Excerpts are shortened. Read the full incident on Optimizely's status page.

Affected: Library, Plan, Requests

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-07-31 17:53 UTC

   We're aware that the Home Page, Plan module, and Requests module in CMP are currently not loading for some customers. Our team is actively investigating the root cause. We'll post an update here as soon as we know more — thanks for bearing with us.

2. identified 2026-07-31 18:39 UTC

   The issue has been identified and a fix is being implemented.

3. monitoring 2026-07-31 19:31 UTC

   A fix has been implemented and we are monitoring the results.

4. resolved 2026-07-31 20:10 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Optimizely's status page.

Affected: ODP Application, Portal UI, Campaigns

Failure mode: A zone, region or data center became unavailable. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-07-29 19:35 UTC

   Optimizely ODP App, ODP Campaigns, and OCP Portal UI are currently unavailable in the US region. We are investigating and will provide an update shortly.

2. resolved 2026-07-29 20:46 UTC

   The issue has been resolved.

Excerpts are shortened. Read the full incident on Optimizely's status page.

Affected: Optimizely Identity

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. investigating 2026-07-23 15:26 UTC

   We're aware of an issue affecting access to some products, caused by a disruption with our identity provider (Okta). We're engaged with Okta support and working to restore service. Updates to follow as soon as possible.

2. identified 2026-07-23 17:51 UTC

   We have identified an issue stemming from a disruption with our identity provider. We are seeing some improvement as we work to mitigate the problem and we continue to work with them on a full resolution.

3. resolved 2026-07-23 18:41 UTC

   The disruption with our identify provider has been resolved. Thank you for your patience with this issue.

Excerpts are shortened. Read the full incident on Optimizely's status page.

Affected: West US

Failure mode: A zone, region or data center became unavailable. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

Names an upstream provider: Azure.

Started during Azure: Network connectivity – Issues accessing resources in West US.

1. investigating 2026-07-23 15:10 UTC

   We are currently investigating an issue reported for customer located in the West US Azure DC. We will provide additional updates as soon as they become available. Thank you for your patience!

2. identified 2026-07-23 16:10 UTC

   This issue has been identified and we are working with our third party vendor on mitigation efforts

3. identified 2026-07-23 17:16 UTC

   The potential cause of the degregation of the West US Azure Data Center has been identified. Mitigation efforts are currently underway. We will provide additional updates as soon as they become available. Thank you for your patience!

4. identified 2026-07-23 18:10 UTC

   Our third party vendor is continuing to rollout mitigation actions

5. monitoring 2026-07-23 18:35 UTC

   We are seeing continued restoration of sites across the platform, with services gradually returning to normal. Our teams are closely monitoring the situation and will share further updates as soon as they are available.

6. resolved 2026-07-23 20:34 UTC

   This incident has been resolved and service availability and functionality fully restored.

Excerpts are shortened. Read the full incident on Optimizely's status page.

Affected: Content Recommendations API, Content Recommendations Management Interface

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-07-23 06:57 UTC

   We are investigating an issue affecting the Content Recommendations service in the North America region. Users may experience increased latency, delayed recommendation updates, or intermittent failures with search and indexing operations. We are continuing our investigation and...

2. monitoring 2026-07-23 09:12 UTC

   A fix has been implemented and we are monitoring the result.

3. resolved 2026-07-23 09:35 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Optimizely's status page.

Affected: Campaign user interface

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-07-17 16:59 UTC

   We are currently investigating an event that is impacting the availability of the graphical user interfaces for managing campaigns and content.

2. resolved 2026-07-17 17:17 UTC

   The affected component was identified and the problem was resolved at 19:06 CEST. Only a part of users was affected by this problem.

Excerpts are shortened. Read the full incident on Optimizely's status page.

Affected: Library

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

Names an upstream provider: Google Cloud.

1. investigating 2026-07-13 08:56 UTC

   We're currently investigating an issue involving DAM assets returning 404s for thumbnails while not generating downloads as well for a subset of customers. Our engineering teams are actively working on a solution, and this incident is being treated as a priority. We hope to...

2. monitoring 2026-07-13 09:32 UTC

   A fix has been implemented and we're currently monitoring the results.

3. resolved 2026-07-13 10:46 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Optimizely's status page.

Affected: US West

Failure mode: A zone, region or data center became unavailable. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-07-09 18:39 UTC

   We are currently investigating an event that is impacting the availability on the Search & Navigation (FIND) service in the US West region. A subset of clients will be experiencing high latency or 5xx-errors and failed requests. We will continue to provide updates as they become...

2. identified 2026-07-09 19:03 UTC

   The issue has been identified and a fix is being implemented.

3. resolved 2026-07-09 20:38 UTC

   The incident has been resolved as the service has fully recovered and is stable.

Excerpts are shortened. Read the full incident on Optimizely's status page.

Affected: Data Ingestion and Processing

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-06-30 13:05 UTC

   For a small subset of EU ODP accounts, we are observing an ingest lag. We are investigating this and aiming to reduce said lag back to zero.

2. identified 2026-06-30 16:08 UTC

   We have identified the issue, and put some changes in place to mitigate it - currently, ingest lag is minimal but still present.

3. resolved 2026-06-30 17:58 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Optimizely's status page.

Affected: Data Ingestion and Processing, Campaigns

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-06-29 12:15 UTC

   We are currently investigating delays in data processing affecting customers in the North America (NA) region. As a result, some data may take longer than usual to be reflected in the platform, and time-sensitive operations such as continuous campaign execution may be delayed....

2. monitoring 2026-06-29 14:55 UTC

   We have identified and resolved the issue. Data processing has returned to normal, and queued data is being processed. Continuous campaign execution and other time-sensitive operations have resumed normal operation. Our team is actively monitoring the system to confirm full...

3. resolved 2026-06-30 12:35 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Optimizely's status page.

Affected: Data Ingestion and Processing, Campaigns

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-06-22 20:30 UTC

   We are currently experiencing data processing delays in the North America region. As a result, continuous campaigns will not run until the processing lag has cleared. Our team is actively investigating and working to restore normal processing times. We will provide an update as...

2. identified 2026-06-23 18:27 UTC

   Our team is actively working on a fix to resolve delayed data processing. Customers may continue to experience data processing lag while remediation is underway. As a precautionary measure, we are temporarily pausing recurring campaigns in the US region to prevent duplicate or...

3. monitoring 2026-06-23 21:00 UTC

   We have implemented a fix, and data processing has resumed. The accumulated processing delay is now clearing, though it may take some time to fully catch up. Customers may continue to see some lag until the backlog has been processed. Recurring campaigns in the US region remain...

4. monitoring 2026-06-24 09:20 UTC

   We are continuing to monitor for any further issues.

5. monitoring 2026-06-24 10:25 UTC

   The data processing delay has been resolved, and processing has returned to normal. Recurring campaigns have been resumed, and continuous campaigns are now running as usual. Our team is actively monitoring the system to ensure continued stable performance. We will provide a...

6. resolved 2026-06-25 14:53 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Optimizely's status page.

Affected: Application UI, App UI, Optimizely REST API

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. resolved 2026-06-22 13:03 UTC

   We have resolved an issue that was resulting in some users receiving errors in the application and configuration-related REST APIs (500 or 502 status codes). There was no impact to experiment execution or ingestion related to the issue.

Excerpts are shortened. Read the full incident on Optimizely's status page.

Affected: Campaigns

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. investigating 2026-06-17 14:00 UTC

   We are investigating an issue causing some email campaign messages to be dropped in the North America region. Some emails are still being delivered. Accounts using email campaigns in the region may be affected. We will update as we learn more.

2. investigating 2026-06-19 12:13 UTC

   We are continuing to investigate this issue. We also have a support thread open with Sendgrid.

3. investigating 2026-06-19 19:02 UTC

   We are still looking into this issue and will provide updates as they become available.

4. identified 2026-06-19 19:51 UTC

   We have likely identified the root cause as a recent SendGrid change that introduced an incompatibility in header processing. We are sharing our findings with SendGrid and implementing a workaround to restore compatibility.

5. monitoring 2026-06-19 21:50 UTC

   We have deployed a fix to unblock affected customers and are actively monitoring the system to confirm stability. We are also working with our email vendor (SendGrid) to put a more complete solution in place on their side. Please note: during the period when emails were...

6. monitoring 2026-06-19 22:29 UTC

   We are continuing to monitor for any further issues.

7. resolved 2026-06-20 17:41 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Optimizely's status page.

Affected: Library, Plan, Requests, Open API

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

Names an upstream provider: AWS.

1. investigating 2026-06-17 06:47 UTC

   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...

2. monitoring 2026-06-17 07:38 UTC

   A fix has been implemented and we're currently monitoring the situation.

3. resolved 2026-06-17 11:40 UTC

   The incident has been resolved.

Excerpts are shortened. Read the full incident on Optimizely's status page.

Affected: Library, Plan, Requests, Open API, Analytics

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-06-16 07:04 UTC

   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...

2. monitoring 2026-06-16 07:32 UTC

   A fix has been implemented and we're currently monitoring the situation.

3. resolved 2026-06-16 08:52 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Optimizely's status page.

Affected: Digital Experience Cloud Service - Management Portal, Configured Commerce – APAC Region, Configured Commerce – EMEA Region, Configured Commerce – NA Region

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. investigating 2026-06-12 14:50 UTC

   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...

2. identified 2026-06-12 15:03 UTC

   Our vendor has confirmed the issue has been identified and a fix is being implemented.

3. monitoring 2026-06-12 15:09 UTC

   Our vendor has confirmed that a fix has been implemented and they are monitoring the results. We will continue to monitor the situation closely.

4. monitoring 2026-06-12 15:24 UTC

   System performance should be restored but we will continue to monitor closely.

5. resolved 2026-06-12 15:40 UTC

   Our vendor has confirmed this issue has been resolved

Excerpts are shortened. Read the full incident on Optimizely's status page.

Affected: Library, Plan, Requests, Open API, Analytics

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-06-10 11:49 UTC

   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 Our Engineering team is actively working on a...

2. monitoring 2026-06-10 12:31 UTC

   A fix has been implemented and we're currently monitoring the situation.

3. resolved 2026-06-10 19:20 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Optimizely's status page.

Affected: Library, Open API

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

Names an upstream provider: Google Cloud.

1. investigating 2026-06-08 09:27 UTC

   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...

2. monitoring 2026-06-08 10:05 UTC

   A fix has been implemented for the issue affecting DAM asset renditions on the GCP stack. We are actively monitoring the situation to confirm full stability. If you are still experiencing issues, please contact Optimizely Technical Support Services for assistance. We will...

3. resolved 2026-06-08 14:44 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Optimizely's status page.

Failure mode: Login, tokens, certificates or credentials failed. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. resolved 2026-06-04 08:00 UTC

   A partial outage affected OCP Job Scheduler, where scheduled jobs across multiple apps failed to execute due to an expired certificate in the env‑injector mutating webhook, in the US region only. This prevented required environment variables from being injected into workloads,...

Excerpts are shortened. Read the full incident on Optimizely's status page.

Affected: Content Recommendations API

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-06-02 07:48 UTC

   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...

2. monitoring 2026-06-02 08:51 UTC

   A fix has been implemented and we are closely monitoring the results.

3. monitoring 2026-06-02 10:45 UTC

   We continue to monitor the service.

4. resolved 2026-06-02 12:25 UTC

   The incident is resolved.

Excerpts are shortened. Read the full incident on Optimizely's status page.

Affected: Application UI, Optimizely REST API

Failure mode: Login, tokens, certificates or credentials failed. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-05-20 09:42 UTC

   We are currently investigating the issue.

2. investigating 2026-05-20 10:01 UTC

   We are continuing to investigate this issue.

3. monitoring 2026-05-20 10:10 UTC

   A fix has been implemented and we are monitoring the results.

4. resolved 2026-05-20 11:30 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Optimizely's status page.

Affected: Requests

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-05-18 09:20 UTC

   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,...

2. monitoring 2026-05-18 09:41 UTC

   A fix has been implemented and we're currently monitoring the results.

3. resolved 2026-05-18 10:54 UTC

   The incident has been resolved

Excerpts are shortened. Read the full incident on Optimizely's status page.

Affected: Optimizely Graph - EMEA Region

Failure mode: A zone, region or data center became unavailable. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-05-06 12:49 UTC

   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.

2. identified 2026-05-06 13:10 UTC

   The issue has been identified and a fix is being implemented.

3. identified 2026-05-06 14:05 UTC

   We are continuing to work on a fix for this issue. Thank you for your patience!

4. monitoring 2026-05-06 14:51 UTC

   The cluster is performing better now and we are continuing to monitor. Thank you for your patience!

5. resolved 2026-05-07 02:38 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Optimizely's status page.

Affected: North Europe

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

Names an upstream provider: Cloudflare.

1. investigating 2026-05-05 21:54 UTC

   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.

2. identified 2026-05-05 22:28 UTC

   The issue has been identified, and a fix is being implemented.

3. monitoring 2026-05-05 22:30 UTC

   A fix has been put in place, and we are monitoring the results.

4. resolved 2026-05-05 22:36 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Optimizely's status page.

Affected: Content Recommendations Management Interface

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-04-09 08:50 UTC

   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...

2. monitoring 2026-04-09 09:16 UTC

   A fix has been implemented and we are monitoring the results.

3. resolved 2026-04-09 10:31 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Optimizely's status page.

Affected: Snippet Building

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-04-07 01:43 UTC

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

2. monitoring 2026-04-07 02:24 UTC

   We identified and resolved an issue that caused delays when publishing Web Experimentation changes. Some customers may have experienced experiments remaining in a processing state during this window. The publishing queue is now actively processing and clearing a backlog of...

3. resolved 2026-04-07 03:03 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Optimizely's status page.

Affected: ODP Application, Data Ingestion and Processing

Failure mode: A zone, region or data center became unavailable. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-03-30 09:00 UTC

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

2. monitoring 2026-03-30 16:55 UTC

   A fix has been implemented and we are monitoring the results.

3. resolved 2026-03-30 21:48 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Optimizely's status page.

Affected: Event Export, Event Export

Failure mode: Login, tokens, certificates or credentials failed. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. identified 2026-03-27 14:01 UTC

   We are aware of an issue affecting the Events Export API, which is causing some requests to this endpoint to return errors. Our team has identified the root cause and is actively working on a resolution. No event data collection is impacted by this issue, only the ability to...

2. monitoring 2026-03-27 15:32 UTC

   The issue affecting the Events Export API has been resolved and we will continue to monitor the improvement.

3. resolved 2026-03-27 16:44 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Optimizely's status page.

Affected: Library, Plan, Requests

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

Names an upstream provider: Cloudflare.

1. identified 2026-03-24 23:57 UTC

   We are currently aware of an issue affecting image loading and uploading across the CMP and DAM. This is caused by an ongoing Cloudflare outage that has impacted our image server. In addition, inconsistent behaviour has been reported with public links. We are monitoring this as...

2. monitoring 2026-03-25 00:31 UTC

   A fix has been implemented and the reported issue, along with all associated symptoms, should now be resolved. Images should load and upload as expected, and public links should function normally. We will continue to monitor the situation following the release of this solution...

3. resolved 2026-03-25 09:16 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Optimizely's status page.

Affected: Sweden Central

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. investigating 2026-03-05 10:23 UTC

   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...

2. investigating 2026-03-05 11:37 UTC

   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!

3. monitoring 2026-03-05 12:02 UTC

   Our third-party supplier are working on restoring service stability for their affected customers. We verified that impacted Optimizely customer site(s) responds intermittently since around 15 minutes. We are continuing to monitor closely.

4. resolved 2026-03-05 12:29 UTC

   This incident has been resolved. The stability of the service has been monitored and confirmed stable.

Excerpts are shortened. Read the full incident on Optimizely's status page.

Affected: US West

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. identified 2026-03-04 14:04 UTC

   We are currently investigating an event that is impacting the availability on the Search & Navigation (FIND) service in the US West region. A subset of clients will be experiencing high latency or 5xx-errors and failed requests. We will post additional updates hourly or when we...

2. monitoring 2026-03-04 14:32 UTC

   The issue have been fixed. We identified it was a minor subset of customers impacted. We continue to monitor the service.

3. resolved 2026-03-04 17:19 UTC

   Resolved. No further impacts have been observed, and all systems remain nominal.

Excerpts are shortened. Read the full incident on Optimizely's status page.