Episerver Outage History

Started Nov 18, 2025, 11:57 AM UTC· resolved Nov 18, 2025, 06:57 PM UTC

1. investigating Nov 18, 2025, 11:57 AM UTC

   Cloudflare is investigating an issue which potentially impacts multiple customers. Further detail will be provided as more information becomes available.

2. investigating Nov 18, 2025, 12:08 PM UTC

   We are continuing to investigate this issue.

3. investigating Nov 18, 2025, 12:11 PM UTC

   We are continuing to investigate this issue.

4. investigating Nov 18, 2025, 12:13 PM UTC

   Cloudflare is investigating an issue which potentially impacts multiple customers. Further detail will be provided as more information becomes available. Thank you for your patience!

5. investigating Nov 18, 2025, 12:34 PM UTC

   Cloudflare are seeing services recover, but customers may continue to observe higher-than-normal error rates as they continue remediation efforts.

6. investigating Nov 18, 2025, 12:48 PM UTC

   Cloudflare still continuing to investigate this issue.

7. investigating Nov 18, 2025, 12:52 PM UTC

   Cloudflare are seeing services recover, but customers may continue to observe higher-than-normal error rates as they continue remediation efforts.

8. investigating Nov 18, 2025, 01:09 PM UTC

   During Cloudflare attempts to remediate, they have disabled WARP access in London. Users in London trying to access the Internet via WARP will see a failure to connect.

9. identified Nov 18, 2025, 01:22 PM UTC

   The issue has been identified and a fix is being implemented. Cloudflare are continuing to work towards restoring other services.

10. identified Nov 18, 2025, 01:40 PM UTC

    Cloudflare continuing working on restoring service for application services customers.

11. identified Nov 18, 2025, 02:03 PM UTC

    Cloudflare still continuing working on restoring service for application services customers. Thank you for your patience!

12. identified Nov 18, 2025, 02:25 PM UTC

    Cloudflare still continuing to work on a fix for this issue.

13. identified Nov 18, 2025, 02:45 PM UTC

    Cloudflare deployed a change which has restored dashboard services. They are still working to remediate broad application services impact.

14. monitoring Nov 18, 2025, 02:46 PM UTC

    A fix has been implemented and Cloudflare believe the incident is now resolved. They are continuing to monitor for errors to ensure all services are back to normal.

15. monitoring Nov 18, 2025, 02:59 PM UTC

    Some customers may be still experiencing issues logging into or using the Cloudflare dashboard. Cloudflare are working on a fix to resolve this, and continuing to monitor for any further issues.

16. identified Nov 18, 2025, 03:25 PM UTC

    Cloudflare are continuing to monitor for any further issues.

17. monitoring Nov 18, 2025, 03:58 PM UTC

    Cloudflare is continuing to focus on restoring service post-fix. They are mitigating several issues that remain post-deployment.

18. monitoring Nov 18, 2025, 05:12 PM UTC

    Cloudflare reports continued reduction in errors & latency, but intermittent errors may still occur as services stabilize. Cloudflare is pursuing options to accelerate the recovery process.

19. resolved Nov 18, 2025, 06:57 PM UTC

    Cloudflare has declared the issue resolved, and our platform teams have confirmed all services have successfully recovered.

Read the full incident report →

Started Nov 17, 2025, 08:00 AM UTC· resolved Nov 18, 2025, 03:13 AM UTC

1. investigating Nov 17, 2025, 08:00 AM UTC

   We are currently investigating an event that is impacting the response time on the Search & Navigation (FIND) service for EMEA09. 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.

2. monitoring Nov 17, 2025, 09:15 AM UTC

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

3. investigating Nov 17, 2025, 10:37 AM UTC

   We are currently investigating this issue.

4. investigating Nov 17, 2025, 11:31 AM UTC

   We are continuing to investigate the issue and work on mitigation measures. Customers may experience intermittent slower response times in the North Europe region. A new update will be provided as soon as it is available.

5. investigating Nov 17, 2025, 12:37 PM UTC

   We still continuing to investigate the issue and work on mitigation measures. Customers may experience intermittent slower response times in the North Europe region. A new update will be provided as soon as it is available. Thank you for your patience!

6. investigating Nov 17, 2025, 02:18 PM UTC

   The investigation is ongoing, and we are working on measures to resolve the issue. Customers may experience intermittent slower response times in the North Europe region. A new update will be provided as soon as it is available. Thank you for your patience!

7. investigating Nov 17, 2025, 03:47 PM UTC

   We still continuing to investigate the issue and work on mitigation measures. Customers may experience intermittent slower response times in the North Europe region. A new update will be provided as soon as it is available. Thank you for your patience!

8. resolved Nov 18, 2025, 03:13 AM UTC

   The cluster response time returns to normal level. This incident has been resolved.

Read the full incident report →

Started Nov 10, 2025, 02:38 AM UTC· resolved Nov 10, 2025, 01:01 PM UTC

1. investigating Nov 10, 2025, 02:38 AM UTC

   We are currently investigating ongoing deployment failures within DXP Management Portal (PaaS-portal), and therefore we recommend you to not start any new deployments at this time. We will provide more updates as soon as they become available. Thank you for your patience.

2. identified Nov 10, 2025, 03:07 AM UTC

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

3. identified Nov 10, 2025, 04:16 AM UTC

   We are continuing to develop the code fix for the issue identified, and additional updates will be provided as they become available.

4. identified Nov 10, 2025, 07:20 AM UTC

   Development of a fix continues for the issue we identified. We will provide additional updates as they become available.

5. monitoring Nov 10, 2025, 11:42 AM UTC

   A fix was implemented around 11:00 (UTC) and we see that deployments have been successful since then. We will continue to monitor closely.

6. resolved Nov 10, 2025, 01:01 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Nov 07, 2025, 12:30 PM UTC· resolved Nov 21, 2025, 04:46 PM UTC

1. investigating Nov 07, 2025, 06:36 PM UTC

   We are investigating the problem with identity resolution in EMEA.

2. identified Nov 07, 2025, 09:34 PM UTC

   Customers may experience the creation of duplicate profiles with new identities for those who have been previously seen. We are collaborating with our vendor to identify and test a potential solution for one of the underlying data storage systems.

3. identified Nov 08, 2025, 02:04 AM UTC

   We are continuing to work with our vendor to test a potential solution for one of the underlying data storage systems.

4. identified Nov 08, 2025, 08:39 AM UTC

   We have successfully recovered identity data for profiles that were seen before the incident. This recovery enables working with the original profiles instead of profile duplicates that may have been created during the incident. We will continue to examine the data to identify potential inconsistencies and develop a plan for resolving them.

5. identified Nov 11, 2025, 08:23 AM UTC

   We're still analysing the affected dataset to identify potential inconsistencies and develop a plan for resolving them.

6. identified Nov 12, 2025, 10:12 PM UTC

   We have identified all the variations of potential inconsistencies and now working on a solution to resolve them.

7. identified Nov 13, 2025, 10:13 PM UTC

   We are working on a solution to resolve the remaining data inconsistencies. An estimated completion time will be provided in due course.

8. identified Nov 16, 2025, 02:52 PM UTC

   We anticipate commencing data repair operations on Monday evening (CET). Once we begin, we can provide an estimated completion timeline.

9. identified Nov 19, 2025, 09:28 AM UTC

   We expect to complete the data repair operations by Friday, 21 November, in the evening (CET).

10. resolved Nov 21, 2025, 04:46 PM UTC

    We have finished the large majority of the planned data operations, all duplicates that were created as a part of the incident were removed and all campaign activity returned to normal. Over the coming weeks, we will be prioritising low-impact data clean-up operations.

Read the full incident report →

Started Nov 06, 2025, 11:54 PM UTC· resolved Nov 07, 2025, 12:21 AM UTC

1. investigating Nov 06, 2025, 11:54 PM UTC

   We are in investigating and issue where a "Something went wrong" error appear when trying to make changes to a running experiment in Feature Experimentation.

2. monitoring Nov 07, 2025, 12:10 AM UTC

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

3. resolved Nov 07, 2025, 12:21 AM UTC

   This incident has been resolved.

Read the full incident report →

Started Nov 06, 2025, 08:45 AM UTC· resolved Nov 06, 2025, 06:49 PM UTC

1. investigating Nov 06, 2025, 10:30 AM UTC

   We are investigating the degraded performance of the data processing and issues when using the List API, Profiles API, and GraphQL API.

2. identified Nov 06, 2025, 10:52 AM UTC

   We are working with our vendor to resolve the issue with one of underlying data storages.

3. identified Nov 06, 2025, 02:22 PM UTC

   We are continuing to work with our vendor to resolve the issue with one of the underlying data storage systems.

4. monitoring Nov 06, 2025, 04:08 PM UTC

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

5. monitoring Nov 06, 2025, 05:52 PM UTC

   Data processing and ODP APIs are operational.

6. resolved Nov 06, 2025, 06:49 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Nov 04, 2025, 02:32 PM UTC· resolved Nov 04, 2025, 04:46 PM UTC

1. resolved Nov 04, 2025, 04:46 PM UTC

   At approximately 14:32 UTC, we experienced an issue with the cloud license check API used by DXP customer sites running on Optimizely CMS. During this period, CMS administrators may have seen a warning banner when logging into the backend. End users browsing live sites were not affected. The issue was mitigated by approximately 16:30 UTC, and the warning banner disappeared once the service recovered. We continue to monitor the system to ensure ongoing stability.

Read the full incident report →

Started Oct 29, 2025, 04:12 PM UTC· resolved Oct 29, 2025, 11:29 PM UTC

1. investigating Oct 29, 2025, 04:12 PM UTC

   We have identified an issue with our cloud hosting platform affecting a subset of customers, resulting in some sites failing to load. We are investigating and will provide updates as soon as they are available.

2. identified Oct 29, 2025, 04:46 PM UTC

   This has been identified by our cloud platform vendor as a DNS issue resulting in availability degradation of some services, including the service management portal. We have been informed that the vendor has taken remedial steps to address and restore portal access issues. The underlying issue is under investigation; further updates will be provided as progress is made.

3. monitoring Oct 29, 2025, 06:26 PM UTC

   Our platform team has taken several mitigative actions, but is still working on an overarching fix for this issue. Currently a configuration rollback is being initiated, and customers should begin seeing positive results around approximately 19:00 UTC, but full restoration will require further steps to normalize network traffic. Some configuration changes may be restricted while the platform team rolls out these fix efforts.

4. monitoring Oct 29, 2025, 07:26 PM UTC

   Our platform team has taken several mitigative actions, but is still working on an overarching fix for this issue. Currently a configuration rollback is being initiated, and customers should begin seeing positive results around approximately 19:00 UTC, but full restoration will require further steps to normalize network traffic. Some configuration changes may be restricted while the platform team rolls out these fix efforts. ----- Critical Note: The source of the issue has been confirmed to lie primarily within the Azure Front Door services, resulting in the primary impact of the outage being customer sites that significantly rely on Azure Front Door in their configuration.

5. monitoring Oct 29, 2025, 09:02 PM UTC

   We are seeing recovery across most affected sites. While some services still remain partially degraded, we anticipate recovery to continue as platform health stabilizes.

6. resolved Oct 29, 2025, 11:29 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Oct 27, 2025, 02:46 PM UTC· resolved Oct 27, 2025, 05:22 PM UTC

1. investigating Oct 27, 2025, 02:46 PM UTC

   We are investigating an issue affecting the Content Recommendations service for a subset of customers in the EMEA region, which may cause increased latency in rendering some content, such as serving images. Teams are working to identify a fix as soon as possible.

2. monitoring Oct 27, 2025, 04:02 PM UTC

   A fix has been implemented by our upstream platform vendor, and we are monitoring the results.

3. resolved Oct 27, 2025, 05:22 PM UTC

   Performance has remained steady and healthy. This incident has been resolved.

Read the full incident report →

Started Oct 27, 2025, 01:26 PM UTC· resolved Oct 30, 2025, 09:09 AM UTC

1. investigating Oct 27, 2025, 01:26 PM UTC

   We have identified an issue affecting deployments for some DXP customers, and are actively investigating.

2. investigating Oct 27, 2025, 02:34 PM UTC

   We are experiencing an ongoing issue with the DXP Management Portal (PaaS) that affects a subset of customers' ability to make deployments. Waiting and trying again may help with the issue. We are working to resolve this as quickly as possible.

3. investigating Oct 27, 2025, 03:48 PM UTC

   We are continuing to investigate the issue, and have engaged our platform support vendor for assistance. We will provide further updates as information becomes available.

4. identified Oct 28, 2025, 02:56 AM UTC

   We have identified the cause of the issue and are currently working on a fix. While the problem may still persist for a subset of clients, retrying the deployment could be successful. We appreciate your patience as we work towards a resolution.

5. monitoring Oct 29, 2025, 09:20 AM UTC

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

6. resolved Oct 30, 2025, 09:09 AM UTC

   This incident has been resolved.

Read the full incident report →

Started Oct 23, 2025, 06:47 AM UTC· resolved Oct 23, 2025, 08:19 AM UTC

1. investigating Oct 23, 2025, 06:47 AM UTC

   We are currently investigating an availability issue with Cloud license portal. It can result in CMS backend license check failure and longer DXP provisioning. We will post additional updates when we have information available. Thank you for your patience.

2. monitoring Oct 23, 2025, 07:36 AM UTC

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

3. resolved Oct 23, 2025, 08:19 AM UTC

   This incident has been resolved.

Read the full incident report →

Started Oct 22, 2025, 12:45 AM UTC· resolved Oct 24, 2025, 05:58 PM UTC

1. investigating Oct 22, 2025, 08:01 AM UTC

   We are investigating the issue with ODP APIs that can lead to high request latency and errors.

2. identified Oct 22, 2025, 08:03 AM UTC

   The issue has been identified and a fix is being implemented for the event collection and other APIs. We are still investigating the issue with GraphQL API. Customers may experience high request latency and errors when using GraphQL.

3. identified Oct 22, 2025, 02:12 PM UTC

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

4. identified Oct 22, 2025, 05:23 PM UTC

   We thank you for your patience as our efforts on a fix remain ongoing. Additional updates will be provided as they become available.

5. identified Oct 22, 2025, 09:03 PM UTC

   We are continuing to work on a fix for this issue. Teams have taken all steps available to mitigate the issue, though some customers may still experience intermittent symptoms. We thank you for your patience as teams work toward a solution.

6. identified Oct 23, 2025, 07:07 AM UTC

   We are continuing to work on the fix for the issue identified earlier, and additional updates will be provided as they become available. We thank you for your patience as teams work toward a solution.

7. identified Oct 23, 2025, 09:21 AM UTC

   We are continuing to work on the fix for the issue and additional updates will be provided as they become available. Thank you for your patience!

8. monitoring Oct 23, 2025, 06:04 PM UTC

   We are currently addressing two issues affecting the performance of our services. Please find the details of these issues and their current status below: Issue 1: Increased GraphQL Usage. We observed an unexpected surge in GraphQL usage that resulted in service performance degradation across multiple customers. To address this, we have implemented enhanced rate-limiting controls to better distribute system resources and prevent a single source from impacting overall service availability. These actions have successfully stabilized performance, allowing all customers to use GraphQL without errors. We are continuing to optimize our infrastructure to better handle variable load patterns and support growing usage demands across our customer base. Issue 2: Elevated GraphQL Request Latency. Since around 5 am UTC, there has been an increase in GraphQL request latency, leading to slower segment evaluations for customers. While requests are completing, they are taking longer than usual. We are currently investigating the cause, which appears to be related to routine maintenance. We expect this maintenance to be completed shortly, with improvements in latency anticipated soon after.

9. resolved Oct 24, 2025, 05:58 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Oct 21, 2025, 02:47 PM UTC· resolved Oct 21, 2025, 08:09 PM UTC

1. monitoring Oct 21, 2025, 02:47 PM UTC

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

2. resolved Oct 21, 2025, 08:09 PM UTC

   Performance has remained healthy and steady. This issue has been determined fully resolved.

Read the full incident report →

Started Oct 21, 2025, 01:22 PM UTC· resolved Oct 21, 2025, 07:40 PM UTC

1. investigating Oct 21, 2025, 01:22 PM UTC

   We have identified an issue impacting the US-West region in which DXP customers may receive intermittent HTTP 500-level response codes, experience timeouts or high latency when accessing App Service (Web, Mobile, and API Apps), App Service (Linux), or Function deployments hosted in this region. Teams are working to mitigate impacts and are pursuing further information from the platform team.

2. investigating Oct 21, 2025, 02:23 PM UTC

   The Platform team has acknowledged the issue and is actively investigating; the situation is being closely monitored, and updates will be provided as soon as they are made available.

3. monitoring Oct 21, 2025, 02:48 PM UTC

   We are currently seeing sites recovering across the affected region, and we are closely monitoring performance as services stabilize.

4. monitoring Oct 21, 2025, 05:17 PM UTC

   The Platform team has declared the issue mitigated. Site services are confirmed operational, but we will continue to monitor performance.

5. resolved Oct 21, 2025, 07:40 PM UTC

   This issue has been declared fully resolved. No further impacts have occurred, and services remain healthy and stable.

Read the full incident report →

Started Oct 20, 2025, 11:46 AM UTC· resolved Oct 21, 2025, 02:38 PM UTC

1. identified Oct 20, 2025, 11:46 AM UTC

   Given that some of our vendors are still reporting performance issues, all continuous campaigns in NA region of ODP are paused.

2. identified Oct 20, 2025, 01:46 PM UTC

   Our cloud platform and storage vendors are working on mitigation and are in the recovery process. However, some Data Platform services are still experiencing issues. As a result, all continuous campaigns in the NA region of ODP are paused. Customers might also encounter data ingestion delays and failures when using the Export API or viewing data in the ODP App.

3. identified Oct 20, 2025, 04:41 PM UTC

   Our cloud platform and storage vendors are working on mitigation and are in the recovery process. However, some Data Platform and Connect Platform services are still experiencing issues. As a result, all continuous campaigns in the NA region of ODP are paused. Customers might also encounter data ingestion delays and failures when using the Export API or viewing data in the ODP App.

4. monitoring Oct 21, 2025, 01:01 AM UTC

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

5. monitoring Oct 21, 2025, 09:42 AM UTC

   We are continuing to monitor for any further issues.

6. resolved Oct 21, 2025, 02:38 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Oct 20, 2025, 07:58 AM UTC· resolved Oct 20, 2025, 11:21 AM UTC

1. investigating Oct 20, 2025, 07:58 AM UTC

   We are investigating an ongoing issue with AWS for Increased Error Rates and Latencies affecting Content Marketing Platform availability. 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.

2. monitoring Oct 20, 2025, 09:33 AM UTC

   Our third party service provider has identified the cause and has applied initial mitigations. We are observing signs of recovery for our impacted services such as ODP, CMP, and Experimentation. We will continue to monitor the situation and provide additional update once available. Thanks for your patience.

3. resolved Oct 20, 2025, 11:21 AM UTC

   This incident has been resolved.

Read the full incident report →

Started Oct 19, 2025, 11:39 AM UTC· resolved Oct 19, 2025, 03:42 PM UTC

1. investigating Oct 19, 2025, 01:39 PM UTC

   We are investigating the issue with data processing. Data collection and API are not affected.

2. identified Oct 19, 2025, 01:52 PM UTC

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

3. monitoring Oct 19, 2025, 02:00 PM UTC

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

4. resolved Oct 19, 2025, 03:42 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Oct 16, 2025, 11:11 AM UTC· resolved Oct 16, 2025, 01:26 PM UTC

1. investigating Oct 16, 2025, 11:11 AM UTC

   We are currently investigating issue with Cloud license portal. It can result in CMS backend license check may fail and longer DXP provisioning.

2. identified Oct 16, 2025, 11:23 AM UTC

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

3. monitoring Oct 16, 2025, 11:35 AM UTC

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

4. monitoring Oct 16, 2025, 11:59 AM UTC

   We are continuing to monitor for any further issues.

5. resolved Oct 16, 2025, 01:26 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Oct 13, 2025, 04:09 AM UTC· resolved Oct 13, 2025, 07:41 AM UTC

1. investigating Oct 13, 2025, 04:09 AM UTC

   We are investigating an ongoing issue with one of the Optimizely public websites: nuget.optimizely.com where clients using the service will be experiencing high latency or 5xx-errors. We will provide additional updates as they become available. Thanks for your patience!

2. monitoring Oct 13, 2025, 04:29 AM UTC

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

3. resolved Oct 13, 2025, 07:41 AM UTC

   This incident has been resolved.

Read the full incident report →

Started Oct 10, 2025, 06:24 AM UTC· resolved Oct 10, 2025, 08:04 AM UTC

1. investigating Oct 10, 2025, 06:24 AM UTC

   We are currently investigating an event that is intermittently impacting performance on the Search & Navigation service in the US region, [USEA01]. A subset of clients will be experiencing high latency or failed requests. We will post additional updates hourly or when we have information available. Thank you for your patience.

2. monitoring Oct 10, 2025, 07:06 AM UTC

   The service has been restored and we're closely monitoring the service health.

3. resolved Oct 10, 2025, 08:04 AM UTC

   This incident has been resolved.

Read the full incident report →