Episerver Outage History

Episerver is up right now

Pingoru has recorded 106 incidents for Episerver: 86 in the last 12 months and 27 in the last 90 days.

Source: status.episerver.com

106incidents recorded
86last 12 months
27last 90 days
19 hourstypical duration
Incidents per month
01020AprMayJunJulAugSepOctNov8
Share of hours with an open incident, any severity
0%50%100%AprMayJunJulAugSepOctNov28%
Pingoru began tracking Episerver in April 2026, so earlier months are not shown. Hover a bar for its value.
Show as a table
MonthIncidentsHours with an open incident
April 202623 of 720 (0%)
May 2026418 of 744 (2%)
June 202612196 of 720 (27%)
July 2026814 of 744 (2%)
August 2026737 of 744 (5%)
September 2026837 of 720 (5%)
October 2026937 of 744 (5%)
November 20268124 of 435 (28%)

Episerver reliability, month by month

In the last 12 months, Episerver posted 86 incidents on its official status page. Since Pingoru began tracking it in April 2026, at least one incident was open 8% of the time. Half of the incidents with a known end in the last 12 months were over within 4 hours 10 minutes; the longest, "CMP Library: Video Transcoding Is Temporarily Unavailable For AWS-Hosted Environments" on November 19, 2025, lasted 25 days. The components affected most often were Library (19 incidents), Requests (12) and Plan (11).

  • November 2026 (so far): 8 incidents, an incident was open 28% of the time, the longest lasted 2 days 21 hours.
  • October 2026: 9 incidents, an incident was open 5% of the time, the longest lasted 15 hours 21 minutes.
  • September 2026: 8 incidents, an incident was open 5% of the time, the longest lasted 21 hours 37 minutes.
  • August 2026: 7 incidents, an incident was open 5% of the time, the longest lasted 13 hours 33 minutes.
  • July 2026: 8 incidents, an incident was open 2% of the time, the longest lasted 5 hours 23 minutes.
  • June 2026: 12 incidents, an incident was open 27% of the time, the longest lasted 3 days 3 hours.
  • May 2026: 4 incidents, an incident was open 2% of the time, the longest lasted 13 hours 49 minutes.
  • April 2026 (tracking began this month): 2 incidents, an incident was open less than 1% of the time, the longest lasted 1 hour 41 minutes.

Incidents, newest first

Minor November 16, 2026 Partial Outage Affecting Recommendations Tracking and Reporting 1d 3h Product Recommendations Data ingestion and processing, Product Recommendations Data ingestion and processing

Started Nov 16, 2026, 04:29 PM UTC· resolved Nov 17, 2026, 07:41 PM UTC

  1. investigating Nov 16, 2026, 04:29 PM UTC

    We are investigating a partial outage affecting Recommendations tracking and reporting for some customer sites; recommendations continue to display, but learning and reporting are currently impacted.

  2. investigating Nov 16, 2026, 10:08 PM UTC

    We are continuing to investigate this issue

  3. identified Nov 17, 2026, 06:35 AM UTC

    We have identified the cause. An infrastructure issue affected the data pipeline for some customer sites. Recommendations were still served, but their quality was reduced and reporting was impacted. We took the necessary actions and the Sweden region has finished processing its backlog. The US region is still catching up.

  4. monitoring Nov 17, 2026, 09:43 AM UTC

    We have fixed the cause. The data pipeline has now caught up in both regions. Recommendations continue to be served, and they are being refreshed with the latest data, so quality should return to normal over the course of today. Reports may show incomplete numbers until they finish catching up. We will post another update later today.

  5. monitoring Nov 17, 2026, 01:09 PM UTC

    For the US region, recommendations continue to be served, and they are being refreshed with the latest data, so quality should return to normal over the course of today. Reports may show incomplete numbers until they finish catching up. For the SE region, we consider this issue to be resolved. We will post another update today regarding the US cluster becoming fully operational.

  6. resolved Nov 17, 2026, 07:41 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor November 13, 2026 Configured Commerce - Mission Control service degredation 2d 21h Configured Commerce - Mission Control

Started Nov 13, 2026, 05:19 PM UTC· resolved Nov 16, 2026, 03:11 PM UTC

  1. investigating Nov 13, 2026, 05:19 PM UTC

    Mission Control and the v1 Build Service are currently experiencing degraded performance due to an ongoing incident. Some Mission Control actions may fail, and all builds/deployments for customers using the v1 build service will fail. Action required for v1 build service customers If you are on the v1 build service, you must upgrade to v2 to continue processing builds and deployments. The v1 build service reached end of life on September 30, 2026, so it will not receive a fix for this incident. Upgrading to v2 is the way to restore your builds and deployments. See Build service v2: Upgrade existing instances for steps: https://docs.optimizely.com/configured-commerce/docs/build-service-v2#upgrade-existing-instances

  2. identified Nov 13, 2026, 09:56 PM UTC

    Efforts remains ongoing to restore full functionality to the service. - The "Generate Database Credentials" action in Mission Control is not operational and we are looking into remediation - Configured Commerce Build Service v1 builds and deployments are not operational; customers must move to build service v2 to remediate All other Mission Control actions, including build service v2 builds and deployments are operational

  3. resolved Nov 16, 2026, 03:11 PM UTC

    The Mission Control service degradation has been resolved, but two longer-term disruptions remain in place. Ongoing disruptions: - Database credentials remain disabled. The “Generate Database Credentials” action in Mission Control will stay disabled. If you need access to a database, use the Database Backup action to download a copy and review it. See the following URL: https://docs.optimizely.com/configured-commerce/mission-control/database-backup. Log a support ticket with Optimizely Support if additional assistance is needed. - Build Service v1 will not be fixed. v1 builds and deployments remain non-operational. The v1 build service reached end of life on September 30, 2026, and will not receive a fix. Customers must move to build service v2 to restore builds and deployments. See the following URL for the Build service v2: Upgrade existing instances: https://docs.optimizely.com/configured-commerce/docs/build-service-v2#upgrade-existing-instances All other Mission Control actions, including build service v2 builds and deployments, are fully operational.

Read the full incident report →

Critical November 13, 2026 Slow loading and performance issues in Content Marketing Platform (CMP) 2h 28m Library, Plan, Requests, Open API and 1 more

Started Nov 13, 2026, 04:02 PM UTC· resolved Nov 13, 2026, 06:30 PM UTC

  1. investigating Nov 13, 2026, 04:02 PM UTC

    We are investigating reports that the Optimizely Content Marketing Platform (CMP) is loading slowly or failing to load for some customers. Affected users may see a loading screen that does not finish, or pages that take much longer than usual to open. The issue is intermittent: pages may load, then slow down again when refreshed. Our Engineering team has reproduced the issue and is investigating the cause. We will post an update as soon as we learn more. We apologize for the disruption to your work.

  2. investigating Nov 13, 2026, 04:03 PM UTC

    We are continuing to investigate this issue.

  3. investigating Nov 13, 2026, 04:29 PM UTC

    We have narrowed down the behavior reported in Optimizely Content Marketing Platform (CMP). Based on our latest findings, CMP is not failing to load. Instead, the first load of the application may take up to approximately 60 seconds to complete, and a loading screen may appear during that time. We recommend allowing the page to finish loading rather than refreshing as a temporary workaround. Our Engineering team is continuing to investigate the cause of the delay and to improve load times. We will share more information as soon as we have them at our disposal. We apologize for any inconvenience caused.

  4. identified Nov 13, 2026, 05:34 PM UTC

    A GA4 (Google Analytics) slowdown caused slow loading and timeouts for CMP organizations using GA4 due to internal dependencies. Our engineering team is rolling out a fix and will update when service is restored.

  5. monitoring Nov 13, 2026, 05:52 PM UTC

    CMP homepage performance has returned to normal. In case you are still facing the issue, please try clearing your browser cache and reload the page. We are continuing to monitor closely and will post a final update once we confirm the issue is fully resolved.

  6. resolved Nov 13, 2026, 06:30 PM UTC

    The incident has been resolved.

Read the full incident report →

Critical November 12, 2026 Optimizely E-Mail Support Outage 1d 15h E-mail

Started Nov 12, 2026, 10:15 PM UTC· resolved Nov 14, 2026, 01:20 PM UTC

  1. investigating Nov 12, 2026, 10:15 PM UTC

    We are aware of a global outage affecting Microsoft 365 services, including email. As a result, support requests sent to Optimizely by email may be delayed or may not be delivered until Microsoft resolves the issue. Phone and the support portal are not affected and remain fully available. If your request is urgent, please contact us through one of those channels. If you emailed us during this outage, please resubmit your request through the support portal so we don't miss it. We will post updates here as more information becomes available.

  2. investigating Nov 13, 2026, 01:22 AM UTC

    The incident remains ongoing at this time. We are continuing to monitor the situation with our vendor very closely.

  3. identified Nov 13, 2026, 10:02 AM UTC

    Recovery is progressing, with early signs of stabilization. Service capacity remains below normal and service health continues to fluctuate as traffic is gradually restored. We will post updates here as more information becomes available.

  4. identified Nov 13, 2026, 01:26 PM UTC

    Recovery continues across affected regions. Some users of the affected Microsoft 365 services may still experience intermittent access issues or delayed email delivery. We will post updates here as more information becomes available.

  5. identified Nov 13, 2026, 06:20 PM UTC

    Broad recovery and stability is being seen across Microsoft 365 services. Microsoft has addressed the underlying issue and continues to restore service to remaining customers and regions. We will post updates here as more information becomes available.

  6. monitoring Nov 13, 2026, 10:12 PM UTC

    Recovery across the previously affected Microsoft services has remained stable. Due to the severity of impact this incident caused, Microsoft is monitoring for an extended period. We will post updates here as more information becomes available.

  7. resolved Nov 14, 2026, 01:20 PM UTC

    Microsoft has declared this incident resolved. If you emailed us during this outage, please resubmit your request so we don't miss it. Thank you!

Read the full incident report →

Minor November 9, 2026 Optimizely Graph in EMEA - Intermittent performance issues 4h 16m Optimizely Graph - EMEA Region

Started Nov 09, 2026, 08:24 PM UTC· resolved Nov 10, 2026, 12:41 AM UTC

  1. identified Nov 09, 2026, 08:24 PM UTC

    We have observed Intermittent performance issues for Optimizely Graph in EMEA region and are working on mitigations. Further updates will come. Thank you for your patience.

  2. monitoring Nov 09, 2026, 09:35 PM UTC

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

  3. monitoring Nov 09, 2026, 09:38 PM UTC

    We are continuing to monitor for any further issues.

  4. identified Nov 09, 2026, 10:06 PM UTC

    Correction to our previous update: service is still degraded. Optimizely Graph in EMEA region is continuing to experience intermittent performance issues, and our team is actively working on a fix. We apologize for the confusion. We will have an update again soon.

  5. monitoring Nov 09, 2026, 10:20 PM UTC

    Optimizely Graph in EMEA has recovered. We are continuing to monitor and will post a final update.

  6. investigating Nov 09, 2026, 11:02 PM UTC

    Optimizely Graph in EMEA returned to a degraded state following the recovery we reported earlier. Our team is actively investigating. We once again apologize for the confusion and appreciate the cooperation. We will have an update again soon.

  7. monitoring Nov 09, 2026, 11:36 PM UTC

    Service has been restored for Optimizely Graph in EMEA. Our team is closely monitoring to ensure it remains stable and prevent any further degradation.

  8. resolved Nov 10, 2026, 12:41 AM UTC

    This incident has been resolved.

Read the full incident report →

Minor November 9, 2026 Optimizely Graph in EMEA - Intermittent performance issues 1h 48m Optimizely Graph - EMEA Region

Started Nov 09, 2026, 02:55 PM UTC· resolved Nov 09, 2026, 04:43 PM UTC

  1. investigating Nov 09, 2026, 02:55 PM UTC

    We have observed Intermittent performance issues for Optimizely Graph in EMEA region and are working on mitigations. Further updates will come. Thank you for your patience.

  2. monitoring Nov 09, 2026, 03:33 PM UTC

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

  3. resolved Nov 09, 2026, 04:43 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor November 9, 2026 B2B Environment down, not accessible - Multiple environments affected 1h 30m Configured Commerce – EMEA Region

Started Nov 09, 2026, 09:57 AM UTC· resolved Nov 09, 2026, 11:27 AM UTC

  1. investigating Nov 09, 2026, 09:57 AM UTC

    We are currently investigating this issue.

  2. identified Nov 09, 2026, 10:00 AM UTC

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

  3. monitoring Nov 09, 2026, 10:19 AM UTC

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

  4. monitoring Nov 09, 2026, 10:19 AM UTC

    We are continuing to monitor for any further issues.

  5. resolved Nov 09, 2026, 11:27 AM UTC

    This incident has been resolved.

Read the full incident report →

Notice October 28, 2026 Content Graph Performance Degredation 2h 33m Optimizely Graph - APAC Region, Optimizely Graph - EMEA Region, Optimizely Graph - NA Region, Optimizely Graph - UAEN Region

Started Oct 28, 2026, 05:27 PM UTC· resolved Oct 28, 2026, 08:00 PM UTC

  1. monitoring Oct 28, 2026, 05:27 PM UTC

    Content Graph experienced http 500 and 404 errors, which we have remediated. We are continuing to monitor the health of the service closely.

  2. resolved Oct 28, 2026, 08:00 PM UTC

    This incident has been resolved and the service has remained healthy

Read the full incident report →

Major October 27, 2026 Asset uploads failing in Optimizely CMP and DAM 15h 21m Library, Plan, Requests

Started Oct 27, 2026, 03:51 PM UTC· resolved Oct 28, 2026, 07:13 AM UTC

  1. investigating Oct 27, 2026, 03:51 PM UTC

    We're aware of an issue where uploads are failing in Optimizely Content Marketing Platform (CMP) and Digital Asset Management (DAM). Users trying to upload assets may see an "Upload Error" message, and the upload won't finish. Our Engineering team is investigating right now and is working to find the cause and restore normal upload behavior as quickly as possible. We'll post more details on the investigation soon. We apologize for the disruption and thank you for your patience.

  2. identified Oct 27, 2026, 05:01 PM UTC

    We've identified the cause of the upload failures in Optimizely Content Marketing Platform (CMP) and Digital Asset Management (DAM). The issue is with a third-party service provider that supports file uploads. Their service is currently rejecting upload requests from our platform, which is why users see an "Upload Error" message. Our Engineering team has already contacted the provider and is working with them to restore uploads as quickly as possible. We don't have an estimated time for resolution yet. We'll share another update as soon as we have more information We apologize for the disruption and thank you for your patience.

  3. monitoring Oct 28, 2026, 12:14 AM UTC

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

  4. resolved Oct 28, 2026, 07:13 AM UTC

    This incident has been resolved.

Read the full incident report →

Minor October 23, 2026 Degraded Performance - CMS Edit Mode in DXP 1h 31m North Europe, Sweden Central

Started Oct 23, 2026, 02:14 PM UTC· resolved Oct 23, 2026, 03:46 PM UTC

  1. investigating Oct 23, 2026, 02:14 PM UTC

    We are investigating reports of elevated latency and intermittent errors affecting the CMS editing interface and background scheduled tasks across select DXP environments. We will continue to post updates as they come. Thank you for your understanding and cooperation.

  2. investigating Oct 23, 2026, 02:14 PM UTC

    We are continuing to investigate this issue.

  3. identified Oct 23, 2026, 02:41 PM UTC

    We have identified the root cause of the performance degradation and are actively working on a fix. We will share further updates as more information becomes available. Thank you once again for your understanding and cooperation.

  4. monitoring Oct 23, 2026, 02:55 PM UTC

    System performance has returned to normal levels, and the degradation has subsided. Our team is closely monitoring the environment to ensure continued stability

  5. resolved Oct 23, 2026, 03:46 PM UTC

    All services are performing normally and stability has been confirmed throughout the monitoring period.

Read the full incident report →

Minor October 22, 2026 Optimizely Campaign: Campaign user interface 3h 19m Campaign user interface

Started Oct 22, 2026, 11:17 AM UTC· resolved Oct 22, 2026, 02:37 PM UTC

  1. investigating Oct 22, 2026, 11:17 AM UTC

    We are currently investigating an event that is impacting performance of the graphical user interface.

  2. identified Oct 22, 2026, 11:18 AM UTC

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

  3. monitoring Oct 22, 2026, 12:06 PM UTC

    After a new login the problem is solved.

  4. resolved Oct 22, 2026, 02:37 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor October 21, 2026 ODP EU Region - Impact due to Snowflake incident 12h 29m ODP Application, Data Ingestion and Processing, Core App Experiences

Started Oct 21, 2026, 07:07 PM UTC· resolved Oct 22, 2026, 07:36 AM UTC

  1. identified Oct 21, 2026, 07:07 PM UTC

    ODP Reports, campaigns and exports are impacted due to a Snowflake EU incident. Real-time segments are unaffected.

  2. monitoring Oct 21, 2026, 10:25 PM UTC

    Snowflake services in the EU are returning to normal operation. The data processing lag in ODP has cleared. We are monitoring the situation.

  3. resolved Oct 22, 2026, 07:36 AM UTC

    The Snowflake issue affecting the EU region has been resolved. Data processing has caught up, and reports, exports, segments, and campaigns are working normally. Recurring campaigns paused during the incident have resumed, and they have completed their missed runs.

Read the full incident report →

Minor October 15, 2026 Degraded Snippet Publishing Performance 3h 4m Snippet Building

Started Oct 15, 2026, 10:35 AM UTC· resolved Oct 15, 2026, 01:39 PM UTC

  1. investigating Oct 15, 2026, 10:35 AM 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 is actively investigating the cause and working to restore normal publishing times.

  2. identified Oct 15, 2026, 12:00 PM 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 backlog, and our engineering team is actively working to restore normal processing times. Existing experiences continue to operate normally. We are closely monitoring recovery and will provide further updates as progress continues.

  3. resolved Oct 15, 2026, 01:39 PM 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 the disruption and appreciate your patience while we worked to restore service. Existing experiences remained available throughout this issue.

Read the full incident report →

Major October 13, 2026 Elevated GraphQL API errors and delayed data ingestion in ODP – US region 1h 5m

Started Oct 13, 2026, 03:05 PM UTC· resolved Oct 13, 2026, 04:10 PM UTC

  1. resolved Oct 13, 2026, 06:10 PM 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 of new data was delayed by up to about 65 minutes. All delayed data accepted during the incident was processed by 16:10 UTC. Our engineers applied infrastructure changes that resolved the issue in the US region. The same changes have been applied to our other regions to prevent a similar issue there. We apologize for the disruption.

Read the full incident report →

Minor October 9, 2026 Content Graph Performance Degradation 16m Optimizely Graph - APAC Region, Optimizely Graph - EMEA Region, Optimizely Graph - NA Region, Optimizely Graph - UAEN Region

Started Oct 09, 2026, 01:24 PM UTC· resolved Oct 09, 2026, 01:41 PM UTC

  1. investigating Oct 09, 2026, 01:24 PM 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 soon as we have more information.

  2. resolved Oct 09, 2026, 01:41 PM 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.

Read the full incident report →

Minor October 6, 2026 Data processing delays in EMEA –

Started Oct 06, 2026, 05:00 PM UTC· resolved Oct 06, 2026, 05:00 PM UTC

  1. resolved Oct 06, 2026, 05:00 PM 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.

Read the full incident report →

Notice September 30, 2026 Optimizely Graph - All region's production clusters experienced failed stored queries 4h 9m Optimizely Graph - APAC Region, Optimizely Graph - EMEA Region, Optimizely Graph - NA Region, Optimizely Graph - UAEN Region

Started Sep 30, 2026, 01:57 PM UTC· resolved Sep 30, 2026, 06:07 PM UTC

  1. monitoring Sep 30, 2026, 01:57 PM 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 Sep 30, 2026, 06:07 PM UTC

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

Read the full incident report →

Minor September 23, 2026 Optimizely Graph - USEA production clusters experiencing intermittent availability issues 2h 52m Optimizely Graph - NA Region

Started Sep 23, 2026, 02:21 PM UTC· resolved Sep 23, 2026, 05:13 PM UTC

  1. investigating Sep 23, 2026, 02:21 PM 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 Sep 23, 2026, 02:46 PM 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 Sep 23, 2026, 05:13 PM UTC

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

Read the full incident report →

Major September 20, 2026 CMP: Data Not Loading in Plan, Resources, Library, and Other Modules (GCP Stack) 1h 43m Library, Plan, Requests, Analytics

Started Sep 20, 2026, 11:24 AM UTC· resolved Sep 20, 2026, 01:08 PM UTC

  1. investigating Sep 20, 2026, 11:24 AM 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 and is actively investigating the root cause. We understand the impact this has on your workflows and appreciate your patience while we work toward a resolution. We will provide a follow-up update as soon as new information becomes available.

  2. identified Sep 20, 2026, 11:29 AM UTC

    The issue has been identified and a fix is being implemented

  3. monitoring Sep 20, 2026, 11:51 AM UTC

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

  4. resolved Sep 20, 2026, 01:08 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor September 17, 2026 Optimizely Identity is redirecting users to the wrong SSO login page. 3m Optimizely Identity

Started Sep 17, 2026, 10:23 PM UTC· resolved Sep 17, 2026, 10:26 PM UTC

  1. investigating Sep 17, 2026, 10:23 PM UTC

    We are currently investigating this issue.

  2. identified Sep 17, 2026, 10:24 PM UTC

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

  3. monitoring Sep 17, 2026, 10:26 PM UTC

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

  4. resolved Sep 17, 2026, 10:26 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor September 16, 2026 Delay of E-Mails Submitted via SMTP API 23m Campaign E-Mail Submission via SMTP

Started Sep 16, 2026, 08:33 AM UTC· resolved Sep 16, 2026, 08:56 AM UTC

  1. identified Sep 16, 2026, 08:33 AM 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 Sep 16, 2026, 08:56 AM UTC

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

Read the full incident report →

Minor September 8, 2026 CMP Analytics Data Not Displaying 21h 37m Analytics

Started Sep 08, 2026, 07:34 AM UTC· resolved Sep 09, 2026, 05:12 AM UTC

  1. identified Sep 08, 2026, 07:34 AM 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 Sep 08, 2026, 06:40 PM 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 analytics data, please contact our support team.

  3. resolved Sep 09, 2026, 05:12 AM UTC

    The issue has been resolved.

Read the full incident report →

Major September 2, 2026 SSL trust issue causing login failures across multiple DXP environments 7h 18m Australia East, East US

Started Sep 02, 2026, 08:05 AM UTC· resolved Sep 02, 2026, 03:23 PM UTC

  1. investigating Sep 02, 2026, 08:05 AM 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 Sep 02, 2026, 08:51 AM 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 content. 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.

  3. identified Sep 02, 2026, 10:26 AM 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 we make progress. Thank you for your patience and understanding.

  4. identified Sep 02, 2026, 11:35 AM 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 Sep 02, 2026, 12:15 PM UTC

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

  6. resolved Sep 02, 2026, 03:23 PM UTC

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

Read the full incident report →

Critical September 2, 2026 CMP and DAM are inaccessible 2h 48m Library, Plan, Requests, Open API and 1 more

Started Sep 02, 2026, 05:00 AM UTC· resolved Sep 02, 2026, 07:49 AM UTC

  1. investigating Sep 02, 2026, 05:00 AM 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 for the disruption to your operations. A further update will be provided as soon as there is a meaningful development to share.

  2. identified Sep 02, 2026, 05:20 AM 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 continued impact.

  3. monitoring Sep 02, 2026, 06:44 AM UTC

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

  4. resolved Sep 02, 2026, 07:49 AM 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.

Read the full incident report →

Minor August 25, 2026 Service degradation due to network connectivity issue in Southeast Asia 2h 21m Singapore, Australia East, Australia East

Started Aug 25, 2026, 05:15 AM UTC· resolved Aug 25, 2026, 07:37 AM UTC

  1. investigating Aug 25, 2026, 05:15 AM 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 your patience!

  2. monitoring Aug 25, 2026, 06:58 AM UTC

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

  3. resolved Aug 25, 2026, 07:37 AM UTC

    This incident has been resolved.

Read the full incident report →