Optimizely Status

Wed Apr 23 2025 20:44:52 GMT+0000 (Coordinated Universal Time)

Optimizely Campaign - Database Maintenance

Apr 23, 20:44 UTC
Completed - The scheduled maintenance has been completed.

Apr 23, 20:00 UTC
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.

Apr 8, 12:05 UTC
Scheduled - Dear customer,

on Wednesday, April 23rd 2025 from 22:00 to 23:00 CEST we have to perform a scheduled maintenance on our data management platform.

Within the maintenance window there will be a complete platform downtime, where neither the Campaign User Interface nor the APIs nor any other service will be available. We will work very hard to reduce this time to an unavoidable minimum and prioritize on availability of the most critical functions like tracking and API.
During this phase of the downtime the services will respond to http requests with http error status. Any unprocessed data received prior to the start of the downtime phase will be automatically processed after the end of the downtime phase. The same applies to any scheduled jobs.

Please do not schedule send-outs during the maintenance to minimize subsequent processing delays and ensure you re-sent not accepted API requests after the maintenance was finished! The Campaign Secured File Transfer Service (SFTP) will be available during the entire maintenance window, but no data will be processed during the downtime.

We realize this may create some short-term hassle for you and sincerely apologize for it. We hope you will understand the necessity of this action, which will enable us to continuously provide you with our stable, secure and usually uninterrupted service in the future.

Thank you for your understanding!

Your Optimizely Campaign Team


Wed Apr 23 2025 20:00:21 GMT+0000 (Coordinated Universal Time)

Optimizely Campaign - Database Maintenance

Apr 23, 20:00 UTC
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.

Apr 8, 12:05 UTC
Scheduled - Dear customer,

on Wednesday, April 23rd 2025 from 22:00 to 23:00 CEST we have to perform a scheduled maintenance on our data management platform.

Within the maintenance window there will be a complete platform downtime, where neither the Campaign User Interface nor the APIs nor any other service will be available. We will work very hard to reduce this time to an unavoidable minimum and prioritize on availability of the most critical functions like tracking and API.
During this phase of the downtime the services will respond to http requests with http error status. Any unprocessed data received prior to the start of the downtime phase will be automatically processed after the end of the downtime phase. The same applies to any scheduled jobs.

Please do not schedule send-outs during the maintenance to minimize subsequent processing delays and ensure you re-sent not accepted API requests after the maintenance was finished! The Campaign Secured File Transfer Service (SFTP) will be available during the entire maintenance window, but no data will be processed during the downtime.

We realize this may create some short-term hassle for you and sincerely apologize for it. We hope you will understand the necessity of this action, which will enable us to continuously provide you with our stable, secure and usually uninterrupted service in the future.

Thank you for your understanding!

Your Optimizely Campaign Team


Tue Apr 22 2025 17:30:45 GMT+0000 (Coordinated Universal Time)

Slow Responses When Managing Experimentation Projects

Apr 22, 17:30 UTC
Resolved - Application performance has been restored to normal.

Apr 22, 16:26 UTC
Update - 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.

Apr 22, 14:57 UTC
Update - We are actively investigating reports of slow response times when attempting to manage Experimentation projects.

Apr 22, 14:56 UTC
Update - We are continuing to investigate this issue.

Apr 22, 14:26 UTC
Investigating - We are actively investigating reports of slow response times when attempting to manage Experimentation projects.


Tue Apr 22 2025 16:26:32 GMT+0000 (Coordinated Universal Time)

Slow Responses When Managing Experimentation Projects

Apr 22, 16:26 UTC
Update - 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.

Apr 22, 14:57 UTC
Update - We are actively investigating reports of slow response times when attempting to manage Experimentation projects.

Apr 22, 14:56 UTC
Update - We are continuing to investigate this issue.

Apr 22, 14:26 UTC
Investigating - We are actively investigating reports of slow response times when attempting to manage Experimentation projects.


Tue Apr 22 2025 14:58:37 GMT+0000 (Coordinated Universal Time)

Slow Responses When Managing Experimentation Projects

Apr 22, 14:57 UTC
Update - We are actively investigating reports of slow response times when attempting to manage Experimentation projects.

Apr 22, 14:56 UTC
Update - We are continuing to investigate this issue.

Apr 22, 14:26 UTC
Investigating - We are actively investigating reports of slow response times when attempting to manage Experimentation projects.


Tue Apr 22 2025 14:56:44 GMT+0000 (Coordinated Universal Time)

Slow Responses When Managing Feature Experimentation Projects

Apr 22, 14:56 UTC
Update - We are continuing to investigate this issue.

Apr 22, 14:26 UTC
Investigating - We are actively investigating reports of slow response times when attempting to manage Experimentation projects.


Tue Apr 22 2025 14:56:18 GMT+0000 (Coordinated Universal Time)

Slow Responses When Managing Feature Experimentation Projects

Apr 22, 14:26 UTC
Investigating - We are actively investigating reports of slow response times when attempting to manage Experimentation projects.


Tue Apr 22 2025 14:26:45 GMT+0000 (Coordinated Universal Time)

Slow Responses When Managing Feature Experimentation Projects

Apr 22, 14:26 UTC
Investigating - We are actively investigating reports of slow response times when attempting to manage projects in Feature Experimentation.


Wed Apr 16 2025 20:01:12 GMT+0000 (Coordinated Universal Time)

Experimentation E3 Export File Availability

Apr 16, 20:01 UTC
Resolved - This incident has been resolved.

Apr 16, 20:00 UTC
Monitoring - All export files for 15 April 2025 have been generated and are available for download.

Apr 16, 16:13 UTC
Update - We are continuing to investigate this issue.

Apr 16, 15:20 UTC
Investigating - 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.


Wed Apr 16 2025 16:42:25 GMT+0000 (Coordinated Universal Time)

PIM background jobs stalling

Apr 16, 16:42 UTC
Resolved - This incident has been resolved and service has been restored to full functionality

Apr 16, 10:16 UTC
Monitoring - A fix has been implemented and we are monitoring the results.

Apr 15, 19:05 UTC
Update - We are continuing to work on the hotfix for this issue and will provide additional updates as they become available.

Apr 15, 13:06 UTC
Update - 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.

Apr 15, 02:54 UTC
Identified - The issue has been identified and we're working on implementing a fix.

Apr 14, 20:49 UTC
Investigating - 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