- Detected by Pingoru
- Jul 31, 2026, 05:53 PM UTC
- Resolved
- Jul 31, 2026, 08:10 PM UTC
- Duration
- 2h 17m
Affected: LibraryPlanRequests
Timeline · 4 updates
-
investigating Jul 31, 2026, 05:53 PM UTC
We're aware that the Home Page, Plan module, and Requests module in CMP are currently not loading for some customers. Our team is actively investigating the root cause. We'll post an update here as soon as we know more — thanks for bearing with us.
-
identified Jul 31, 2026, 06:39 PM UTC
The issue has been identified and a fix is being implemented.
-
monitoring Jul 31, 2026, 07:31 PM UTC
A fix has been implemented and we are monitoring the results.
-
resolved Jul 31, 2026, 08:10 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Jul 29, 2026, 07:35 PM UTC
- Resolved
- Jul 29, 2026, 08:46 PM UTC
- Duration
- 1h 10m
Affected: ODP ApplicationCampaignsPortal UI
Timeline · 2 updates
-
investigating Jul 29, 2026, 07:35 PM UTC
Optimizely ODP App, ODP Campaigns, and OCP Portal UI are currently unavailable in the US region. We are investigating and will provide an update shortly.
-
resolved Jul 29, 2026, 08:46 PM UTC
The issue has been resolved.
Read the full incident report →
- Detected by Pingoru
- Jul 23, 2026, 03:26 PM UTC
- Resolved
- Jul 23, 2026, 06:41 PM UTC
- Duration
- 3h 15m
Affected: Optimizely Identity
Timeline · 3 updates
-
investigating Jul 23, 2026, 03:26 PM UTC
We're aware of an issue affecting access to some products, caused by a disruption with our identity provider (Okta). We're engaged with Okta support and working to restore service. Updates to follow as soon as possible.
-
identified Jul 23, 2026, 05:51 PM UTC
We have identified an issue stemming from a disruption with our identity provider. We are seeing some improvement as we work to mitigate the problem and we continue to work with them on a full resolution.
-
resolved Jul 23, 2026, 06:41 PM UTC
The disruption with our identify provider has been resolved. Thank you for your patience with this issue.
Read the full incident report →
- Detected by Pingoru
- Jul 23, 2026, 03:10 PM UTC
- Resolved
- Jul 23, 2026, 08:34 PM UTC
- Duration
- 5h 23m
Affected: West US
Timeline · 6 updates
-
investigating Jul 23, 2026, 03:10 PM UTC
We are currently investigating an issue reported for customer located in the West US Azure DC. We will provide additional updates as soon as they become available. Thank you for your patience!
-
identified Jul 23, 2026, 04:10 PM UTC
This issue has been identified and we are working with our third party vendor on mitigation efforts
-
identified Jul 23, 2026, 05:16 PM UTC
The potential cause of the degregation of the West US Azure Data Center has been identified. Mitigation efforts are currently underway. We will provide additional updates as soon as they become available. Thank you for your patience!
-
identified Jul 23, 2026, 06:10 PM UTC
Our third party vendor is continuing to rollout mitigation actions
-
monitoring Jul 23, 2026, 06:35 PM UTC
We are seeing continued restoration of sites across the platform, with services gradually returning to normal. Our teams are closely monitoring the situation and will share further updates as soon as they are available.
-
resolved Jul 23, 2026, 08:34 PM UTC
This incident has been resolved and service availability and functionality fully restored.
Read the full incident report →
- Detected by Pingoru
- Jul 23, 2026, 06:57 AM UTC
- Resolved
- Jul 23, 2026, 09:35 AM UTC
- Duration
- 2h 37m
Affected: Content Recommendations APIContent Recommendations Management Interface
Timeline · 3 updates
-
investigating Jul 23, 2026, 06:57 AM UTC
We are investigating an issue affecting the Content Recommendations service in the North America region. Users may experience increased latency, delayed recommendation updates, or intermittent failures with search and indexing operations. We are continuing our investigation and will provide an update as soon as more information becomes available. Thank you for you patience!
-
monitoring Jul 23, 2026, 09:12 AM UTC
A fix has been implemented and we are monitoring the result.
-
resolved Jul 23, 2026, 09:35 AM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Jul 17, 2026, 04:59 PM UTC
- Resolved
- Jul 17, 2026, 05:17 PM UTC
- Duration
- 17m
Affected: Campaign user interface
Timeline · 2 updates
-
investigating Jul 17, 2026, 04:59 PM UTC
We are currently investigating an event that is impacting the availability of the graphical user interfaces for managing campaigns and content.
-
resolved Jul 17, 2026, 05:17 PM UTC
The affected component was identified and the problem was resolved at 19:06. Only a part of users was affected by this problem.
Read the full incident report →
- Detected by Pingoru
- Jul 13, 2026, 08:56 AM UTC
- Resolved
- Jul 13, 2026, 10:46 AM UTC
- Duration
- 1h 50m
Affected: Library
Timeline · 3 updates
-
investigating Jul 13, 2026, 08:56 AM UTC
We're currently investigating an issue involving DAM assets returning 404s for thumbnails while not generating downloads as well for a subset of customers. Our engineering teams are actively working on a solution, and this incident is being treated as a priority. We hope to share more information soon.
-
monitoring Jul 13, 2026, 09:32 AM UTC
A fix has been implemented and we're currently monitoring the results.
-
resolved Jul 13, 2026, 10:46 AM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Jul 09, 2026, 06:39 PM UTC
- Resolved
- Jul 09, 2026, 08:38 PM UTC
- Duration
- 1h 58m
Affected: US West
Timeline · 3 updates
-
investigating Jul 09, 2026, 06:39 PM UTC
We are currently investigating an event that is impacting the availability on the Search & Navigation (FIND) service in the US West region. A subset of clients will be experiencing high latency or 5xx-errors and failed requests. We will continue to provide updates as they become available. Thank you for your patience.
-
identified Jul 09, 2026, 07:03 PM UTC
The issue has been identified and a fix is being implemented.
-
resolved Jul 09, 2026, 08:38 PM UTC
The incident has been resolved as the service has fully recovered and is stable.
Read the full incident report →
- Detected by Pingoru
- Jun 30, 2026, 01:05 PM UTC
- Resolved
- Jun 30, 2026, 05:58 PM UTC
- Duration
- 4h 53m
Affected: Data Ingestion and Processing
Timeline · 3 updates
-
investigating Jun 30, 2026, 01:05 PM UTC
For a small subset of EU ODP accounts, we are observing an ingest lag. We are investigating this and aiming to reduce said lag back to zero.
-
identified Jun 30, 2026, 04:08 PM UTC
We have identified the issue, and put some changes in place to mitigate it - currently, ingest lag is minimal but still present.
-
resolved Jun 30, 2026, 05:58 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Jun 29, 2026, 12:15 PM UTC
- Resolved
- Jun 30, 2026, 12:35 PM UTC
- Duration
- 1d
Affected: Data Ingestion and ProcessingCampaigns
Timeline · 3 updates
-
investigating Jun 29, 2026, 01:16 PM UTC
We are currently investigating delays in data processing affecting customers in the North America (NA) region. As a result, some data may take longer than usual to be reflected in the platform, and time-sensitive operations such as continuous campaign execution may be delayed. Our engineering team is actively investigating the issue. We apologize for any inconvenience.
-
monitoring Jun 29, 2026, 02:55 PM UTC
We have identified and resolved the issue. Data processing has returned to normal, and queued data is being processed. Continuous campaign execution and other time-sensitive operations have resumed normal operation. Our team is actively monitoring the system to confirm full stability.
-
resolved Jun 30, 2026, 12:35 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Jun 22, 2026, 08:30 PM UTC
- Resolved
- Jun 25, 2026, 02:53 PM UTC
- Duration
- 2d 18h
Affected: Data Ingestion and ProcessingCampaigns
Timeline · 6 updates
-
investigating Jun 22, 2026, 11:43 PM UTC
We are currently experiencing data processing delays in the North America region. As a result, continuous campaigns will not run until the processing lag has cleared. Our team is actively investigating and working to restore normal processing times. We will provide an update as soon as we have more information. We apologize for any inconvenience and appreciate your patience.
-
identified Jun 23, 2026, 06:27 PM UTC
Our team is actively working on a fix to resolve delayed data processing. Customers may continue to experience data processing lag while remediation is underway. As a precautionary measure, we are temporarily pausing recurring campaigns in the US region to prevent duplicate or 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.
-
monitoring Jun 23, 2026, 10:56 PM UTC
We have implemented a fix, and data processing has resumed. The accumulated processing delay is now clearing, though it may take some time to fully catch up. Customers may continue to see some lag until the backlog has been processed. Recurring campaigns in the US region remain 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.
-
monitoring Jun 24, 2026, 09:20 AM UTC
We are continuing to monitor for any further issues.
-
monitoring Jun 24, 2026, 10:25 AM UTC
The data processing delay has been resolved, and processing has returned to normal. Recurring campaigns have been resumed, and continuous campaigns are now running as usual. Our team is actively monitoring the system to ensure continued stable performance. We will provide a final update once we have confirmed full recovery. We apologize for any inconvenience this may have caused.
-
resolved Jun 25, 2026, 02:53 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Jun 22, 2026, 01:03 PM UTC
- Resolved
- Jun 22, 2026, 01:03 PM UTC
- Duration
- —
Affected: Application UIApp UIOptimizely REST API
Timeline · 1 update
-
resolved Jun 22, 2026, 01:03 PM UTC
We have resolved an issue that was resulting in some users receiving errors in the application and configuration-related REST APIs (500 or 502 status codes). There was no impact to experiment execution or ingestion related to the issue.
Read the full incident report →
- Detected by Pingoru
- Jun 17, 2026, 02:00 PM UTC
- Resolved
- Jun 20, 2026, 05:41 PM UTC
- Duration
- 3d 3h
Affected: Campaigns
Timeline · 7 updates
-
investigating Jun 18, 2026, 10:05 PM UTC
We are investigating an issue causing some email campaign messages to be dropped in the North America region. Some emails are still being delivered. Accounts using email campaigns in the region may be affected. We will update as we learn more.
-
investigating Jun 19, 2026, 12:13 PM UTC
We are continuing to investigate this issue. We also have a support thread open with Sendgrid.
-
investigating Jun 19, 2026, 07:02 PM UTC
We are still looking into this issue and will provide updates as they become available.
-
identified Jun 19, 2026, 07:51 PM UTC
We have likely identified the root cause as a recent SendGrid change that introduced an incompatibility in header processing. We are sharing our findings with SendGrid and implementing a workaround to restore compatibility.
-
monitoring Jun 19, 2026, 09:50 PM UTC
We have deployed a fix to unblock affected customers and are actively monitoring the system to confirm stability. We are also working with our email vendor (SendGrid) to put a more complete solution in place on their side. Please note: during the period when emails were 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.
-
monitoring Jun 19, 2026, 10:29 PM UTC
We are continuing to monitor for any further issues.
-
resolved Jun 20, 2026, 05:41 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Jun 17, 2026, 06:47 AM UTC
- Resolved
- Jun 17, 2026, 11:40 AM UTC
- Duration
- 4h 52m
Affected: LibraryPlanRequestsOpen API
Timeline · 3 updates
-
investigating Jun 17, 2026, 06:47 AM UTC
We are currently investigating an issue affecting customers hosted on the AWS stack. Customers are experiencing failures when attempting to create tasks within the Optimizely Content Marketing Platform (CMP). Affected: Optimizely Content Marketing Platform (CMP) – Task Creation Infrastructure: AWS-hosted customers only Impact: Task creation failing Our Engineering team is actively working on a solution. We will share more information on this incident soon.
-
monitoring Jun 17, 2026, 07:38 AM UTC
A fix has been implemented and we're currently monitoring the situation.
-
resolved Jun 17, 2026, 11:40 AM UTC
The incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Jun 16, 2026, 07:04 AM UTC
- Resolved
- Jun 16, 2026, 08:52 AM UTC
- Duration
- 1h 48m
Affected: LibraryPlanRequestsOpen APIAnalytics
Timeline · 3 updates
-
investigating Jun 16, 2026, 07:04 AM UTC
We are currently investigating an incident affecting multiple modules within the Optimizely Content Marketing Platform (CMP). The following modules are currently inaccessible to customers: - Plan - Requests - Library / DAM - Analytics Our Engineering team is actively working on a resolution. We will provide a further update as soon as more information is available.
-
monitoring Jun 16, 2026, 07:32 AM UTC
A fix has been implemented and we're currently monitoring the situation.
-
resolved Jun 16, 2026, 08:52 AM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Jun 12, 2026, 02:50 PM UTC
- Resolved
- Jun 12, 2026, 03:40 PM UTC
- Duration
- 49m
Affected: Digital Experience Cloud Service - Management PortalConfigured Commerce – APAC RegionConfigured Commerce – EMEA RegionConfigured Commerce – NA Region
Timeline · 5 updates
-
investigating Jun 12, 2026, 02:50 PM UTC
We are aware of an ongoing incident with one of our third party vendors that could cause site management-related API calls to fail and/or errors to be displayed. CDN cached traffic and security features are not impacted. We will continue to monitor the situation along with our vendor and will continue to post updates here as they become available.
-
identified Jun 12, 2026, 03:03 PM UTC
Our vendor has confirmed the issue has been identified and a fix is being implemented.
-
monitoring Jun 12, 2026, 03:09 PM UTC
Our vendor has confirmed that a fix has been implemented and they are monitoring the results. We will continue to monitor the situation closely.
-
monitoring Jun 12, 2026, 03:24 PM UTC
System performance should be restored but we will continue to monitor closely.
-
resolved Jun 12, 2026, 03:40 PM UTC
Our vendor has confirmed this issue has been resolved
Read the full incident report →
- Detected by Pingoru
- Jun 09, 2026, 08:34 AM UTC
- Resolved
- Jun 04, 2026, 08:00 AM UTC
- Duration
- —
Timeline · 1 update
-
resolved Jun 09, 2026, 08:34 AM UTC
A partial outage affected OCP Job Scheduler, where scheduled jobs across multiple apps failed to execute due to an expired certificate in the env‑injector mutating webhook, in the US region only. This prevented required environment variables from being injected into workloads, causing job failures. Non-job features (e.g., configuration, webhooks) remained functional. No data loss occurred, and all affected jobs caught up after the issue was resolved, though customers may have experienced delays (e.g., stale audience syncs)
Read the full incident report →
- Detected by Pingoru
- Jun 08, 2026, 09:27 AM UTC
- Resolved
- Jun 08, 2026, 02:44 PM UTC
- Duration
- 5h 16m
Affected: LibraryOpen API
Timeline · 3 updates
-
investigating Jun 08, 2026, 09:27 AM UTC
We are currently investigating an issue affecting customers hosted on the GCP stack. Starting this morning, calls to the DAM REST API endpoint 'GET /v3/assets/{asset_id}/renditions' appear to be returning a 500 Internal Server Error. As a result, configured image renditions (used for cropping and scaling images across channels) are not being served. Affected customers will see only the original/main asset image in place of their configured renditions. The rendition configuration UI in CMP Settings > Assets also appears to be impacted, with rendition setups failing to load correctly. Affected: Optimizely Content Marketing Platform (CMP) – DAM / Asset Renditions Infrastructure: GCP-hosted customers only Impact: Image renditions unavailable; 'GET /v3/assets/{asset_id}/renditions' returning 500 We are actively investigating the root cause and will provide an update soon.
-
monitoring Jun 08, 2026, 10:05 AM UTC
A fix has been implemented for the issue affecting DAM asset renditions on the GCP stack. We are actively monitoring the situation to confirm full stability. If you are still experiencing issues, please contact Optimizely Technical Support Services for assistance. We will provide a final update once the incident is fully resolved.
-
resolved Jun 08, 2026, 02:44 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Jun 02, 2026, 07:48 AM UTC
- Resolved
- Jun 02, 2026, 12:25 PM UTC
- Duration
- 4h 36m
Affected: Content Recommendations API
Timeline · 4 updates
-
investigating Jun 02, 2026, 07:48 AM UTC
We are currently investigating an issue affecting the Content Recommendation service in EMEA region. Due to an API disruption, we are unable to serve recommendations at this time. Users may notice missing or unavailable recommendations across the platform. Our team is actively investigating the issue and working to restore full functionality as quickly as possible. We will provide updates as more information becomes available. Thank you for your patience!
-
monitoring Jun 02, 2026, 08:51 AM UTC
A fix has been implemented and we are closely monitoring the results.
-
monitoring Jun 02, 2026, 10:45 AM UTC
We continue to monitor the service.
-
resolved Jun 02, 2026, 12:25 PM UTC
The incident is resolved.
Read the full incident report →
- Detected by Pingoru
- May 20, 2026, 09:42 AM UTC
- Resolved
- May 20, 2026, 11:30 AM UTC
- Duration
- 1h 48m
Affected: Application UIOptimizely REST API
Timeline · 4 updates
-
investigating May 20, 2026, 09:42 AM UTC
We are currently investigating the issue.
-
investigating May 20, 2026, 10:01 AM UTC
We are continuing to investigate this issue.
-
monitoring May 20, 2026, 10:10 AM UTC
A fix has been implemented and we are monitoring the results.
-
resolved May 20, 2026, 11:30 AM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- May 18, 2026, 09:20 AM UTC
- Resolved
- May 18, 2026, 10:54 AM UTC
- Duration
- 1h 33m
Affected: Requests
Timeline · 3 updates
-
investigating May 18, 2026, 09:20 AM UTC
We are currently investigating a reported issue affecting the 'Requests' module, as well as the 'My Work', 'My Team's Work', and 'Watching' sections on the Home Page, which are appearing empty for a subset of customers. Our Engineering team is actively working on a resolution, and we hope to share further information on this matter shortly.
-
monitoring May 18, 2026, 09:41 AM UTC
A fix has been implemented and we're currently monitoring the results.
-
resolved May 18, 2026, 10:54 AM UTC
The incident has been resolved
Read the full incident report →
- Detected by Pingoru
- May 06, 2026, 12:49 PM UTC
- Resolved
- May 07, 2026, 02:38 AM UTC
- Duration
- 13h 49m
Affected: Optimizely Graph - EMEA Region
Timeline · 5 updates
-
investigating May 06, 2026, 12:49 PM UTC
We are experiencing intermittent availability issue for the Optimizely Graph service, for one of the USEA production clusters. Our team is working on mitigating actions. We'll provide new updates.
-
identified May 06, 2026, 01:10 PM UTC
The issue has been identified and a fix is being implemented.
-
identified May 06, 2026, 02:05 PM UTC
We are continuing to work on a fix for this issue. Thank you for your patience!
-
monitoring May 06, 2026, 02:51 PM UTC
The cluster is performing better now and we are continuing to monitor. Thank you for your patience!
-
resolved May 07, 2026, 02:38 AM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- May 05, 2026, 09:54 PM UTC
- Resolved
- May 05, 2026, 10:36 PM UTC
- Duration
- 42m
Affected: North Europe
Timeline · 4 updates
-
investigating May 05, 2026, 09:54 PM UTC
We are currently aware of an active incident with Cloudflare that is affecting authoritative resolution for the .de TLD. We are continuing to investigate and correspond with Cloudflare to push for rapid mitigation.
-
identified May 05, 2026, 10:28 PM UTC
The issue has been identified, and a fix is being implemented.
-
monitoring May 05, 2026, 10:30 PM UTC
A fix has been put in place, and we are monitoring the results.
-
resolved May 05, 2026, 10:36 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Apr 09, 2026, 08:50 AM UTC
- Resolved
- Apr 09, 2026, 10:31 AM UTC
- Duration
- 1h 41m
Affected: Content Recommendations Management Interface
Timeline · 3 updates
-
investigating Apr 09, 2026, 08:50 AM UTC
We have identified an intermittent issue impacting Content Recommendations dashboard. Currently, a part of requests to the reporting dashboard may fail for a subset of customers. This incident is confined to the administrative dashboard only. End-user delivery, including recommendations and widgets, remains fully operational. We are working toward a resolution and appreciate your patience. New updates will be shared when available.
-
monitoring Apr 09, 2026, 09:16 AM UTC
A fix has been implemented and we are monitoring the results.
-
resolved Apr 09, 2026, 10:31 AM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Apr 07, 2026, 01:43 AM UTC
- Resolved
- Apr 07, 2026, 03:03 AM UTC
- Duration
- 1h 19m
Affected: Snippet Building
Timeline · 3 updates
-
investigating Apr 07, 2026, 01:43 AM UTC
We are investigating an issue where changes to Web Experimentation projects may experience delays when publishing. Our team is actively working on a resolution.
-
monitoring Apr 07, 2026, 02:24 AM UTC
We identified and resolved an issue that caused delays when publishing Web Experimentation changes. Some customers may have experienced experiments remaining in a processing state during this window. The publishing queue is now actively processing and clearing a backlog of pending changes. Experiments that were affected should complete automatically. We are continuing to monitor to confirm full resolution.
-
resolved Apr 07, 2026, 03:03 AM UTC
This incident has been resolved.
Read the full incident report →