Optimizely had 85 outages in the last 2 years totaling 259h 34m of downtime — averaging 3.5 incidents per month.
There were 85 Optimizely outages since October 10, 2025 totaling 259h 34m of downtime. Each is summarised below — incident details, duration, and resolution information.
We are currently investigating this issue.
The issue has been identified, and a fix is being implemented.
A fix has been implemented, and we are monitoring the results.
This incident has been resolved.
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.
The issue has been fixed and all delayed emails have been processed.
Customers using the CMP Analytics module may notice that analytics data for the past 4+ days 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.
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 analytics data, please contact our support team.
The issue has been resolved.
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.
We continue investigating login failures affecting some DXP environments. Affected applications may receive a certificate trust error when connecting to our login service. The issue appears to affect applications running on older OS images and .NET versions earlier than .NET 8. Applications on .NET 8 or later seems not impacted based on the reports. Restarting the web application does not resolve the issue. Our engineering teams are working on a service-side resolution. Impacted regions are still being confirmed. We will continue to provide further updates.
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 we make progress. Thank you for your patience and understanding.
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!
A fix has been implemented and we are monitoring the results. Thank for your patience!
The issue has been resolved and the service is now operating normally. Thank you for your patience!
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 for the disruption to your operations. A further update will be provided as soon as there is a meaningful development to share.
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 continued impact.
A fix has been implemented and we're currently monitoring the results. Both products should now be accessible.
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.
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 your patience!
The third‑party provider has mitigated the issue. We are monitoring the results.
This incident has been resolved.
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 progresses. We're trying our utmost to share another update as soon as possible.
A fix has been implemented and we're currently monitoring the results.
The incident has been resolved.
We're investigating DXP multiple environments returning error 503 - affecting only non-production environments.
Our Engineering team has identified the root cause and is actively working on a resolution.
We are implementing the fix and have confirmed the impact affects a limited subset of clients.
This incident has been resolved.
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 the root cause and is actively working on a resolution. Your files are safe and no data loss has occurred. We will continue to provide updates as we make progress toward a fix. Thank you for your patience.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
We are currently investigating an issue with degraded performance for image delivery, processing of tracking requests and delivery of online version.
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.
The performance problems didn't show up again. The mitigation is no longer needed and will be removed. We are still monitoring.
Systems are running stable with the mitigation removed. The incident has been resolved.
We are currently investigating an issue with degraded performance for email dispatch.
The problem has been identified and a partial workaround has been applied. We are still working on a full solution.
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.
No further problems have been observed.
We are currently investigating an issue affecting our Netspring service (Netspring customers only). We will continue to provide timely updates as they become available.
We are continuing to investigate the issue. Thank you for your patience!
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.
The issue affecting the Netspring service has been resolved, and service has been restored to normal operation.
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.
The issue has been identified and a fix is being implemented.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
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.
The issue has been resolved.
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.
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.
The disruption with our identify provider has been resolved. Thank you for your patience with this issue.
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!
This issue has been identified and we are working with our third party vendor on mitigation efforts
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!
Our third party vendor is continuing to rollout mitigation actions
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.
This incident has been resolved and service availability and functionality fully restored.
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 will provide an update as soon as more information becomes available. Thank you for you patience!
A fix has been implemented and we are monitoring the result.
This incident has been resolved.
We are currently investigating an event that is impacting the availability of the graphical user interfaces for managing campaigns and content.
The affected component was identified and the problem was resolved at 19:06. Only a part of users was affected by this problem.
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 share more information soon.
A fix has been implemented and we're currently monitoring the results.
This incident has been resolved.
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 available. Thank you for your patience.
The issue has been identified and a fix is being implemented.
The incident has been resolved as the service has fully recovered and is stable.
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.
We have identified the issue, and put some changes in place to mitigate it - currently, ingest lag is minimal but still present.
This incident has been resolved.
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. Our engineering team is actively investigating the issue. We apologize for any inconvenience.
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 stability.
This incident has been resolved.
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 soon as we have more information. We apologize for any inconvenience and appreciate your patience.
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 double sends while processing catches up. We will resume normal campaign scheduling once processing has fully recovered. We will provide a further update as soon as we have more information. I appreciate your patience.
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 temporarily paused. We will resume normal campaign scheduling once the backlog has fully cleared, to ensure no duplicate or double sends occur. Our team is actively monitoring the recovery, and we will confirm once the system has fully returned to normal. Thank you for your continued patience.
We are continuing to monitor for any further issues.
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 final update once we have confirmed full recovery. We apologize for any inconvenience this may have caused.
This incident has been resolved.
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.
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.
We are continuing to investigate this issue. We also have a support thread open with Sendgrid.
We are still looking into this issue and will provide updates as they become available.
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.
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 partially dropped, we do not have a record of which individual recipients successfully received messages. As a result, if you choose to re-run an affected campaign (e.g., by sending it to a new campaign), some recipients may receive duplicate emails. We will provide a further update as monitoring continues.
We are continuing to monitor for any further issues.
This incident has been resolved.