Is Optimizely Service Down Right Now? Check if there is a current outage ongoing.

We are currently investigating reports of a third-party outage affecting DXP and/or Graph services for a subset of customers. We are working closely with the third-party provider to understand and mitigate the impact. We will provide more updates as soon as they become available. Thank you for your patience!

We are currently investigating an issue related to a Third Party Cloud provider.

The Search and Navigation Service (FIND) EMEA26 cluster, in EUROPE region, has shown continued stable health. This incident have been resolved.

We are currently monitoring an availability issue for EMEA26, that have impacted the availability on the Search & Navigation (FIND) service in the EUROPE region - EMEA26. The service has been fully restored since 9:49 (UTC). A subset of clients might have experienced high latency or 5xx-errors during the event and when service was recovering. We will continue monitoring and post additional updates when we have information available.

The Search and Navigation Service (FIND) EMEA26 cluster, in EUROPE region, has shown continued stable health. This incident have been resolved.

We are currently monitoring an availability issue for EMEA26, that have impacted the availability on the Search & Navigation (FIND) service in the EUROPE region - EMEA26. The service has been fully restored since 9:49 (UTC). A subset of clients might have experienced high latency or 5xx-errors during the event and when service was recovering. We will continue monitoring and post additional updates when we have information available.

On Monday June 2nd at 20:19 UTC, we experienced a network issue affecting a limited number of Everweb customers in the SE2 Datacenter. Our engineering team rapidly found the fault, and restored functionality back to normal. All sites are back online with no further alerting. We apologize for the inconvenience which this may have caused.

On Monday June 2nd at 20:19 UTC, we experienced a network issue affecting a limited number of Everweb customers in the SE2 Datacenter. Our engineering team rapidly found the fault, and restored functionality back to normal. All sites are back online with no further alerting. We apologize for the inconvenience which this may have caused.

The issue has been resolved and at this point all export files for yesterday should be available

Daily E3 export files will be delayed. We are currently working with our vendors to resolve the issue and will update this status as we learn more.

The issue has been resolved and at this point all export files for yesterday should be available

Daily E3 export files will be delayed. We are currently working with our vendors to resolve the issue and will update this status as we learn more.

The Search and Navigation Service (FIND) EMEA03 cluster, in the EUROPE region, has shown continued stable health. This incident have been resolved.

A fix was implemented and the availability on the Search & Navigation (FIND) service in the EUROPE region - EMEA03 has been stable since then, 9:00 (UTC). We'll continue to monitor closely.

We are currently investigating an event that is impacting the availability on the Search & Navigation (FIND) service in the EUROPE region - EMEA03. A subset of clients will be experiencing high latency or 5xx-errors. We will post additional updates hourly or when we have information available. Thank you for your patience.

The Search and Navigation Service (FIND) EMEA03 cluster, in the EUROPE region, has shown continued stable health. This incident have been resolved.

A fix was implemented and the availability on the Search & Navigation (FIND) service in the EUROPE region - EMEA03 has been stable since then, 9:00 (UTC). We'll continue to monitor closely.

We are currently investigating an event that is impacting the availability on the Search & Navigation (FIND) service in the EUROPE region - EMEA03. A subset of clients will be experiencing high latency or 5xx-errors. We will post additional updates hourly or when we have information available. Thank you for your patience.

This incident has been resolved.

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

We are continuing to investigate an intermittent issue resulting in increased errors rate in Feature Experimentation management capabilities. We appreciate your patience and will continue to keep you updated.

We are investigating an issue where some customers are experiencing increased error rates in Feature Experimentation management capabilities and APIs.

This incident has been resolved.

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

We are continuing to investigate an intermittent issue resulting in increased errors rate in Feature Experimentation management capabilities. We appreciate your patience and will continue to keep you updated.

We are investigating an issue where some customers are experiencing increased error rates in Feature Experimentation management capabilities and APIs.

This incident has been resolved.

Mitigation actions have been implemented and we are closely monitoring the results.

We are currently investigating an event that is impacting the availability on the Search & Navigation (FIND) service in the EUROPE region - EMEA03 A subset of clients will be experiencing high latency or 5xx-errors. We will post additional updates hourly or when we have information available. Thank you for your patience.

This incident has been resolved. The service continues to function normally from the time the fix was implemented.

A fix has been deployed for the reported issue and we are currently monitoring the results. If the situation changes, then we will provide a new update ASAP. We sincerely apologize for the inconvenience!

We are investigating an issue involving documents not loading properly within tasks, with users instead getting greeted with an error message in Edit mode. We will post additional updates once we obtain more information. Thank you for your patience!

This incident has been resolved. The service continues to function normally from the time the fix was implemented.

A fix has been deployed for the reported issue and we are currently monitoring the results. If the situation changes, then we will provide a new update ASAP. We sincerely apologize for the inconvenience!

We are investigating an issue involving documents not loading properly within tasks, with users instead getting greeted with an error message in Edit mode. We will post additional updates once we obtain more information. Thank you for your patience!

This incident has been resolved.

The hotfix release is in its final stages. Deployments appear to continue to function normally and monitoring shows no stuck deployments since we switched to the updated automation account at 11:05 AM (UTC). We will continue to monitor closely until the hotfix release is fully completed.

An ongoing system release with a fix is still progressing. New Customer deployments should work as normal now and any ongoing Customer deployments are advised to keep on running. Thank you for your patience!

An ongoing system release with a fix is progressing. New Customer deployments should work as normal now and any ongoing Customer deployments are advised to keep on running.

We are currently experiencing an ongoing issue with deployments and therefore recommend that you do not start any new deployments at this time. We expect the issue to be solved in a short time. We will provide additional updates as soon as they become available. Thank you for your patience!

This incident has been resolved.

The hotfix release is in its final stages. Deployments appear to continue to function normally and monitoring shows no stuck deployments since we switched to the updated automation account at 11:05 AM (UTC). We will continue to monitor closely until the hotfix release is fully completed.

An ongoing system release with a fix is still progressing. New Customer deployments should work as normal now and any ongoing Customer deployments are advised to keep on running. Thank you for your patience!

An ongoing system release with a fix is progressing. New Customer deployments should work as normal now and any ongoing Customer deployments are advised to keep on running.

We are currently experiencing an ongoing issue with deployments and therefore recommend that you do not start any new deployments at this time. We expect the issue to be solved in a short time. We will provide additional updates as soon as they become available. Thank you for your patience!

The team has continued monitoring and we have confirmed we have are longer seeing these intermittent errors. Completing this incident as resolved.

The team is reporting we no longer have errors in the UI. The team is reviewing the implementations from today and confirming we are resolved. We will monitor the site and resolve shortly.

We are experiencing intermittent "Something went wrong" errors affecting both the Web Experimentation and Feature Experimentation UI.

This incident has been resolved.

We are continuing to monitor for any further issues.

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

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

We are continuing to investigate this issue.

We are currently investigating a network issue impacting our Everweb environment. We will post additional updates hourly or when we have information available. Thank you for your patience.

We’ve observed no further issues and will now close this incident.

Services hosted in Data Center SE2 are back online. We are continuing to closely monitor the situation to ensure full stability. A root cause analysis (RCA) will be shared as soon as it is available. Thank you for your patience.

We are currently investigating a hardware issue at data center SE2. An engineer is on-site to assess and address the problem.

This incident has been resolved.

We are currently working on short and long term corrective actions to stabilize the service. At this moment, service is reporting full functionality and we are continuing to closely monitor the health of the service. If the situation changes, we will provide a new update. We sincerely apologize for the inconvenience!

We are currently investigating a recurring event that is impacting the availability on the Search & Navigation (FIND) service in the North Europe region, EMEADEV02. A subset of clients may experience high latency or 5xx-errors. We will post additional updates as information is available. Thank you for your patience.

The issue impacting flag creation has been resolved.

We are currently investigating an issue impacting the creation or update of some Feature Experimentation flags.

This incident has been resolved and workaround has been implemented.

We are currently investigating an recurring event that is impacting the availability on the Search & Navigation (FIND) service in the Europe North region, EMEA05. A subset of clients will be experiencing high latency or 5xx-errors. We will post additional updates hourly or when we have information available. Thank you for your patience.

This incident has been resolved.

A fix was implemented and the service was back to operational at 9:10am UTC.

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

We are currently investigating an event that is impacting the availability on the Search & Navigation (FIND) service in the EU region, EMEA05. A subset of clients will be experiencing high latency or 5xx-errors. We will post additional updates hourly or when we have information available. Thank you for your patience.

This incident has been resolved. The service continues to function normally from the time the fix was implemented.

A fix has been implemented for the reported issue and we are monitoring the results. If the situation changes, we will provide a new update. We sincerely apologize for the inconvenience!

We are investigating an issue which involves task creation from work requests failing. We will post additional updates once we obtain more information. Thank you for your patience!

This incident has been resolved. The service continues to function normally from the time the fix was implemented.

A fix has been implemented and we are monitoring the results. If the situation changes, we will provide a new update. We sincerely apologize for the inconvenience!

We are investigating an issue concerning degraded performance in the Library. We will post additional updates once we obtain more information. Thank you for your patience.

Application performance has been restored to normal.

Application performance has been restored by increasing system capacity. While we continue monitoring and investigating the root cause, all core functionality is now operating at normal latency levels.

We are actively investigating reports of slow response times when attempting to manage Experimentation projects.

We are continuing to investigate this issue.

We are actively investigating reports of slow response times when attempting to manage Experimentation projects.

This incident has been resolved.

All export files for 15 April 2025 have been generated and are available for download.

We are continuing to investigate this issue.

E3 export files for yesterday (15 April 2025) are not yet available. We are investigating the cause and will update here when we have resolution.

This incident has been resolved and service has been restored to full functionality

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

We are continuing to work on the hotfix for this issue and will provide additional updates as they become available.

We've identified a backend bug affecting the Import Asset feature in PIM. In rare cases, jobs with the Overwrite Files option enabled can get stuck and impact overall performance. This is currently limited to a few clients but may affect others due to resource usage. As long as the import job isn’t run, there’s no risk of impact. We’re testing a hotfix and will provide updates as soon as more information becomes available. Thank you for your patience and understanding.

The issue has been identified and we're working on implementing a fix.

We are currently investigating an issue causing our background PIM jobs to stall. As a result, some jobs are remaining in the queue for an extended period of time. Our team is actively working on identifying the root cause and implementing a resolution as quickly as possible

This incident has been resolved. Service has been restored and stabilized and deployments are now successful.

A fix has been implemented and we are monitoring the results. Customers who previously experienced the error can redeploy.

Our engineering team has started implementing the fix and we will provide update once it's ready to roll out.

The issue has been identified and we are working diligently to provide a fix.

We are currently investigating ongoing deployment failures affecting a subset of clients deploying new code packages. We will provide more updates as soon as they become available.

Customers using Optimizely's Configured Commerce naked domain -> www redirect server were impacted from (2147 UTC) to (2231 UTC) due to load on our redirect servers, where navigating to a naked domain showed an SSL problem due to lack of available connections.

This incident has been resolved. A fix has been implemented but as previously noted, a redeployment of site code is needed for the fix to be applied. Additional details are provided in the following Optimizely Support Article: https://support.optimizely.com/hc/en-us/articles/35521173909901-Recent-Performance-issues-related-to-Datadog

An issue has been identified in a previous version of a third-party monitoring tool used for Configured Commerce platform management, which can cause a very gradual buildup in CPU usage and ultimately result in performance degradation on affected sites. The fix for this has been implemented by Optimizely Platform Support, but requires a redeployment of site code in order to be applied. Please perform a site redeploy at your earliest convenience to ensure the utilities update has been applied to your site(s).

This incident has been resolved. Public links for Collections should now function as expected.

We have identified an issue with public links for Collections, and we're actively working on a fix. We will share an update once we have more information, so expect to hear from us soon!

This incident has been resolved as the service has fully recovered

We can confirm that from 12 UTC all impacted services have fully recovered. We are continuing to monitor for any further issues. Thank you for your patience.

We are continuing to monitor for any further issues. Thank you for your patience.

Most of the impacted services have recovered, with a limited subset not yet fully recovered. We continue to monitor the situation closely.

We can confirm that the issue is related to resources hosted in the North Europe region by our third-party supplier. We are in close contact with their team. We will continue to share updates as more information becomes available. Thank you for your continued patience and understanding.

After further investigation, we have identified that the issue is currently affecting multiple services. Our team is actively working to resolve the problem and will provide updates as soon as more information becomes available. Currently affected products in the North Europe region are Search & Navigation, Digital Experience Cloud (DXP) and CMS SaaS.

We are currently investigating an event that is impacting the availability on the Search & Navigation (FIND) service in the EU region. Clients will be experiencing high latency or 5xx-errors. We will post additional updates once we obtain more information. Thank you for your patience.

This incident has been resolved.

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

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

We are currently investigating an event that is impacting the availability on the Search & Navigation (FIND) service in the Europe region - EMEA26. A subset of clients might experiencing high latency or 5xx-errors. We will post additional updates when we have information available. Thank you for your patience.

This incident has been resolved.

A fix has been implemented by our service provider. ODP components in the US are operational. We are continuing to monitor the status.

Our service provider has identified an additional issue and is implementing multiple mitigations.

One of our service providers reported disruptions in the US region. We are continuing to investigate and monitor this issue.

We are observing the degraded performance of data ingestion, export, and campaign execution in the ODP US region.

This incident has been resolved.

A fix has been implemented and the services have been back to normal state since around 14:00 CET.

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

We are currently investigating an incident that is affecting multiple Optimizely Campaign services.

This incident has been resolved.

We're currently investigating a platform outage, which has led to the CMP being inaccessible at the moment for some customers. We will post additional updates once we obtain more information. Thank you for your patience.

This incident has been resolved.

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

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

We are continuing to investigate this issue.

We are currently investigating an issue related to an unresponsive UI in the Feature Experimentation application.

This incident has been resolved.

Monitoring shows continuous good service health. This incident is resolved.

A fix has been implemented and service is operational. We are continuing to monitor the health of the service and will provide additional updates as they become available.

The issue has been identified and we are currently working on mitigation efforts.

We are currently investigating the performance issue with Search and Navigation on EMEA17. Some customers may experience high response times, and/or 5xx errors. We will inform as soon we will have more information. Thank you for your patience!

This incident has been resolved.

The cluster health has been restored and stabilized and we will continue to monitor its performance

The issue has been identified and a fix is being implemented. We are actively monitoring it. Thank you for your patience!

We are currently investigating the performance issue with Search and Navigation on SWEC01. Some customers may experience high response times, and/or 504 errors. We will inform as soon we will have more information. Thank you for your patience!

The fix was successfully implemented and the service is confirmed to be in a continued healthy operational state. Incident is resolved.

The issue has been identified and mitigating actions were applied. Monitoring shows performance started to recover. We will continue close monitoring.

We are investigating a performance issue for one Optimizely Graph production data node in the EMEA region. Requests takes longer time to execute. A limited subset of customer tenants in the EMEA Prod environment are affected. We are working on fixing this issue.

The service has been fully restored and the incident is now resolved

We are continuing to investigate this issue

We are currently investigating an issue affecting our Netspring service (Netspring customers only) who may be seeing a 504 error. We will continue to provide timely updates as they become available.

Our 3rd party provider has resolved the issue with their E-mail platform.

We are monitoring the state of our 3rd party provider's Email service. Their service issue appears to be resolved at this time.

Due to the ongoing issues that Microsoft is having with Outlook 365, you may experience difficulty raising a support ticket with us via email. As an alternative, you can always log into our support portal support.optimizely.com and raise a ticket directly.

This incident has been resolved.

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

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

We are continuing to investigate this issue.

We are continuing to investigate this issue.

We are currently investigating reports of "Something went wrong - the server encountered an internal error" when trying to access projects from the Experimentation Application UI.

This incident has been resolved with no further difficulties observed.

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

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

The issue has been identified and a fix is being implemented. We are actively monitoring it. Thank you for your patience!

We are currently investigating the performance issue with Search and Navigation on SWEC01. We will inform as soon we will have more information. Thank you for your patience!

We experienced technical issues in the US Region that prevented customers from using ODP APIs between 17:28 UTC to 18:30 UTC. The service has been fully restored.

This incident has been resolved.

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

We are currently investigating an issue affecting the processing of incoming data for individual ODP accounts in the NA region, which is causing a data processing lag. We will provide updates as soon as we have more information. Thank you for your patience.

This incident has been resolved.

All services have recovered and we continue to monitor closely.

Most of the impacted services have recovered, with a limited subset not yet fully recovered. We continue to monitor the situation closely. We will provide more updates as they become available. Thank you for your patience.

We are seeing that impacted services are slowly recovering, with several sites gradually becoming operational again. We continue to monitor the situation closely. Our team is in close contact with our third-party supplier and will provide further updates as soon as there is more information to share.

The issue has been identified and a fix is being implemented. Thank you for your patience!

We are continuing to investigate this issue.

This issue is impacting multiple services hosted on Norway East Data Center. Currently, we have identified the following services affected by this issue are, Search & Navigation (Find), DXP, and CMS SaaS. This is related to an event experienced by one of our third-party suppliers. We are in close contact with their team and working diligently to resolve this issue as soon as possible. We will provide updates as soon as more information becomes available. Thank you for your patience and understanding.

We are continuing to investigate this issue.

We are continuing to investigate this issue.

We are currently investigating a potential issue that may be impacting Search and Navigation (Find) and CMS SaaS services in Norway East. Customers may receive intermittent HTTP 500-level response codes, experience timeouts or high latency or disturbance in deployment functionalities. 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. We will provide updates as soon as more information becomes available. Thank you for your patience and understanding.

The availability on the Search & Navigation (FIND) service in the US West region (USWE01) has held in a healthy state. This incident is now resolved.

The availability on the Search & Navigation (FIND) service in the US West region (USWE01) is back to a healthy state. We will keep monitoring closely.

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 might experiencing high latency or 5xx-errors. We will post additional updates hourly or when we have information available. Thank you for your patience.

This incident has been resolved. The problem was mitigated and we are working on a permanent fix now.

We are continuing to monitor for any further issues.

We are currently investigating an event that impacted the availability of the graphical user interfaces for managing campaigns and content between 16:30 and 16:45 CET.

This incident has been resolved.

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

We are currently investigating an issue where attempting to open a Feature Experimentation report will redirect you to the Flags list page.

CMP experienced high volume of requests from an API client, which affected CMP login, Open API token generation and webhook deliveries intermittently. We scaled up our services to handle increased load.

We are investigating intermittent CMP application errors, and we have scaled up platform related services to resolve the errors. We're currently monitoring the results. Additional updates will be posted once we obtain more information. Thank you for your patience.

This incident has been resolved.

The issue for ODP Application was resolved and we continue to monitor further. Thank you for your patience.

The issue for ODP Application has reverted and we continue to investigate further. Issue with Data Ingestion and Processing has been resolved and we are monitoring the result. We will provide new updates as soon as we have more information. Thank you for your patience.

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

We are currently investigating an issue with lists views, they show as empty in the ODP app, and error "503 Service Temporarily Unavailable" is returned in the developer console browser. The issue can also affect pass-through, new lists will not be able to be created. We will provide new updates as soon as we have more information. Thank you for your patience.

This issue has been resolved as Search and Navigation on EMEA03 has remained stable following early corrections.. All normal functionality remains available.

The Search and Navigation service on EMEA03 has stabilized, and service is reporting full functionality. We will continue to monitor and will reassess if the situation changes.

Search and Navigation EMEA03 is still experiencing some fluctuations, and as a result, some customers might encounter intermittent issues. We're actively working on both short-term and long-term solutions to stabilize the service. Currently, the service is reporting full functionality, and we're closely monitoring its health. If there are any changes, we'll provide an update right away. We sincerely apologize for any inconvenience this may cause and appreciate your understanding!

We are currently working on short and long term corrective actions to stabilize the service. At this moment, service is reporting full functionality and we are continuing to closely monitor the health of the service. If the situation changes, we will provide a new update. We sincerely apologize for the inconvenience!

Our team continues to work towards fully resolving this as quickly as possible. Thank you for your patience.

We are continuing to work on a fix for this issue.

Our team continues to work towards fully resolving this as quickly as possible. Thank you for your patience.

We are continuing to work on a fix for this issue.

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

We are aware that the issue has reappeared, and our team is continuing to investigate the root cause. We are working to resolve this as quickly as possible and will provide further updates as we make progress. Thank you for your patience.

We are aware that the issue has reappeared, and our team is continuing to investigate the root cause. We are working to resolve this as quickly as possible and will provide further updates as we make progress. Thank you for your patience.

The cause was identified and mitigated. cluster is back to a healthy state. We continue to monitor the service closely.

Search and Navigation EMEA03 experiencing issues with failed requests. We are currently investigating this issue.

This issue has been resolved.

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

We are currently investigating an event that is impacting the availability on the Search & Navigation (FIND) service in the US region, [USWE01]. A subset of clients will be experiencing high latency or 5xx-errors. We will post additional updates hourly or when we have information available. Thank you for your patience.

This incident has been resolved.

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

The issue with EMEA03 is back again with the status red. We are continuing to investigate this issue.

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

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

We are continuing to investigate this issue.

We are currently investigating issue with Search & Navigation for EMEA03 that is currently experiencing issues which may lead to some failed requests for some users.

This incident has been resolved.

Work continues with a subsequent hotfix deployed and implementation ongoing with resources showing improvement. We will continue to monitor and work with our third-party support to identify initial root cause. Additional updates shall be posted as we have them. Thank you for your patience.

While an initial issue has been identified and a fix has been deployed, a subset of customers has reported ongoing difficulty. We continue to work with our third-party support to identify additional underlying fault which may have been revealed by the first deployment. Additional updates shall be posted as we have them. Thank you for your patience.

An issue has been identified and a fix has been deployed. We will continue to monitor and evaluate as the fix is implemented.

We are continuing to work with our third-party vendor on this issue. As a current workaround to improve the request latency, add the following query-string parameter to the request send to Graph: &stored=true Additional updates will be posted as we obtain more information. Thank you for your patience.

We are continuing to investigate the issue with request latency. Meanwhile the following work around can be used to improve the request latency, add the following query-string parameter to the request send to Graph: &stored=true. We will post additional updates once we obtain more information. Thank you for your patience.

We are continuing to investigate this issue.

We are currently investigating a latency issue in Optimizely Graph in all regions. We will post additional updates when we have information available. Thank you for your patience.

This incident has been resolved.

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

We are currently investigating reports of 'Something went wrong' errors when saving changes to a Ruleset.