All Systems Operational

Uptime over the past 90 days. View historical uptime.
Europe Operational
90 days ago
100.0 % uptime
Today
Core App Operational
90 days ago
100.0 % uptime
Today
API Operational
90 days ago
100.0 % uptime
Today
Batch Data Process Operational
Track & Trigger Operational
90 days ago
100.0 % uptime
Today
OptiPromo Operational
90 days ago
100.0 % uptime
Today
USA Operational
90 days ago
100.0 % uptime
Today
Core App Operational
90 days ago
100.0 % uptime
Today
API Operational
90 days ago
100.0 % uptime
Today
Batch Data Process Operational
Track & Trigger Operational
90 days ago
100.0 % uptime
Today
OptiPromo Operational
90 days ago
100.0 % uptime
Today
Campaigns Channels Operational
90 days ago
99.98 % uptime
Today
Exact Target (Salesforce Marketing Cloud) Operational
Acoustic (SilverPop) Operational
Optimail Operational
90 days ago
100.0 % uptime
Today
Facebook Operational
Google Operational
TextLocal Operational
Bronto Operational
Criterio Operational
Emarsys Operational
Responsys Operational
Optipush Operational
DynamicMail Operational
XtremePush Operational
Others (API) Operational
90 days ago
100.0 % uptime
Today
Optimobile Operational
90 days ago
100.0 % uptime
Today
OptiText SMS Operational
90 days ago
99.62 % uptime
Today
Opti-X Operational
90 days ago
99.99 % uptime
Today
User Interface Operational
90 days ago
100.0 % uptime
Today
Smart Campaigns Operational
90 days ago
100.0 % uptime
Today
Smart Search Operational
90 days ago
100.0 % uptime
Today
Recommend service Operational
90 days ago
99.98 % uptime
Today
Auth0 User Authentication Operational
Auth0 Management API Operational
Auth0 User Authentication Operational
Auth0 Management API Operational
SendGrid API Operational
SendGrid Email Activity Operational
SendGrid API v3 Operational
SendGrid API v2 Operational
SendGrid SMTP Operational
SendGrid Marketing Campaigns Operational
Operational
Degraded Performance
Partial Outage
Major Outage
Maintenance
Major outage
Partial outage
No downtime recorded on this day.
No data exists for this day.
had a major outage.
had a partial outage.

No incidents or maintenance related to this downtime.

Scheduled Maintenance

EU - Batch Update process - ETL - Infrastructure Maintenance Feb 2, 2026 11:30-12:30 UTC

Optimove ETL infrastructure is getting updated.
During this upgrade, Optimoves ETL stage in the batch process will have reduced performance.

Some tenants might experience delay in batch update process completion, which could delay campaign execution by up to 2 hours ( we expect no delay ).

For more information, please reach out to our Support team at: Support@optimove.com
Posted on Jan 12, 2026 - 08:37 UTC

US - Batch Update process - ETL - Infrastructure Maintenance Feb 3, 2026 13:00-14:00 UTC

Optimove ETL infrastructure is getting updated.
During this upgrade, Optimoves ETL stage in the batch process will have reduced performance.

Some tenants might experience delay in batch update process completion, which could delay campaign execution by up to 2 hours ( we expect no delay ).

For more information, please reach out to our Support team at: Support@optimove.com
Posted on Jan 12, 2026 - 08:39 UTC

Action Required: SFTP Connections Must Be Restricted by IP by June 15 Jun 15, 2026 10:00-13:00 UTC

As Optimove works to strengthen security and align with industry best practices, Optimove is changing how SFTP connections are configured.

What is changing
Effective June 15, 2026, all SFTP connections to Optimove must be restricted to one or more specific source IP addresses or IP ranges. Connectivity to Optimove's SFTP from IPs which haven't been whitelisted will no longer be supported.

Action required
To ensure uninterrupted service, please email Support@optimove.com with the following details so we can configure IP allowlist for your SFTP connection:

1. SFTP username used to connect to Optimove
2. Either:
* Your source public IP address(es) used for the connection (static egress IPs), or
* Your IP range(s) (CIDR notation accepted, for example 203.0.113.0/24)

Important
If you use multiple usernames or multiple egress IPs/ranges, please include all relevant details. Once this change is applied, only the IP addresses or ranges you provide will be permitted to access Optimove’s SFTP. Please ensure the information you share is complete and accurate.

Impact if not completed
After June 15, 2026, SFTP connections that are not restricted to approved IPs may be blocked, which can interrupt file transfers.

Need help?
If you are unsure which public egress IP or range to provide, your IT or infrastructure team should be able to confirm it. Our support team can also help validate formatting.
Posted on Jan 27, 2026 - 16:16 UTC
Feb 2, 2026

No incidents reported today.

Feb 1, 2026

No incidents reported.

Jan 31, 2026

No incidents reported.

Jan 30, 2026

No incidents reported.

Jan 29, 2026

No incidents reported.

Jan 28, 2026

No incidents reported.

Jan 27, 2026

No incidents reported.

Jan 26, 2026

No incidents reported.

Jan 25, 2026

No incidents reported.

Jan 24, 2026
Campaign execution - Some campaigns are in failed status
Resolved - The issue is resolved and systems are fully operational. Please verify your campaign statuses and manually run any campaigns that remain in "Not Run" or "Failed" status directly from the site.
Jan 24, 14:46 UTC
Monitoring - Backend recovery is underway and systems are stable. However, to avoid further delays while the queue clears, we continue to advise manually re-running any critical campaigns via the UI.
Jan 24, 14:24 UTC
Identified - We are addressing execution errors affecting a limited number of campaigns. Due to potential delays and a risk of "Not Run" statuses, we advise manually triggering any high-priority campaigns via the UI for immediate delivery.
Jan 24, 14:03 UTC
Investigating - We have identified an issue causing a small percentage of campaigns to fail during execution. Please note that the majority of campaigns are proceeding successfully.
​Our team is currently executing a manual rerun for the affected campaigns. However, this recovery process will take some time to complete and risks campaigns going into "Not Run" status.

​Recommendation:
If you have a high-priority campaign that has failed, we recommend manually re-running it immediately via the user interface (using the "Play" button in the campaign status window) rather than waiting for the backend recovery.
Jan 24, 12:58 UTC
Jan 23, 2026
Batch Update Process - Delay in Campaign execution
Resolved - The issue causing both campaign execution failures and delays has been fully resolved. During the incident, some campaigns may have remained in a Not Run status. This can occur when the Batch Data Update is delayed, and campaign execution begins later than scheduled, resulting in certain campaigns missing their designated run window.

Force Run Behavior
If your instance has Force Run enabled, affected campaigns may still be executed automatically as part of the batch process, provided the incident was resolved within the configured grace period. More details on Force Run can be found here:
https://academy.optimove.com/hc/en-us/articles/10701094593565-Using-Force-Run

To enable Force Run for your instance, please reach out to your Customer Success Manager.

Current Status
Campaign execution has stabilized, failure rates have returned to normal, and all systems are fully operational.

'Not Run' campaigns can be manually run by clicking on the 'Play' button in the relevant campaign status window.
Jan 23, 14:04 UTC
Monitoring - A fix for the campaign execution failures is rolled out across all environments.
We are gradually resuming campaign execution processes for customers.

Next Steps:
We are continuing to resume execution processes and monitor their successful completion.
We will provide additional updates once normal operation is restored.

Next Update:
Another update will be shared within 1-2 hours.
Jan 23, 13:04 UTC
Update - The fix has been developed and rolled out to the production environment.
We are continuing to gradually proceed with the campaign execution processes for customers.

Next Steps
We will monitor the execution process for customers and continue gradually with batch updates.
We will provide additional updates once normal operation is restored.

Next Update
You can expect another update within 1-2 hours or sooner if the fix is fully validated.
Jan 23, 11:24 UTC
Identified - We have identified the root cause of the campaign execution failures. A fix has been developed and is now being prepared for rollout.
We are beginning to run the campaign execution for the first batch of customers.

Next Steps
Our engineering team is rolling out the fix and monitoring its impact closely. We will provide confirmation once the rollout is complete and normal operation is restored.

Next Update
You can expect another update within 1-2 hours or sooner if the fix is fully validated.

Recovery Options are unchanged from previous updates.
Jan 23, 09:16 UTC
Update - We are continuing to experience delays in campaign execution, affecting a subset of customers.
Some campaigns may remain in a “Not Run” status. Not all customers are impacted.

Relevant engineering teams are actively investigating and working to stabilize execution. At this time, the behavior is consistent with delayed batch processing, which may cause certain campaigns to miss their scheduled run window.

What We’re Doing:
Engineering teams remain fully engaged and focused on restoring normal execution as quickly as possible. We are closely monitoring the system and the affected tenants.

Recovery Options are unchanged from previous updates.

Next Update:
We will share another update within 1-2 hours, or sooner if there are any significant changes.
Jan 23, 08:47 UTC
Update - We continue to experience delays in campaign execution impacting some customers, which may result in certain campaigns remaining in a “Not Run” status. Not all customers are affected.

Our engineering team is actively continuing the investigation and working to stabilize execution. At this time, the behavior remains consistent with delayed batch processing causing some campaigns to miss their scheduled run window.

What We’re Doing:
Engineering remains engaged and focused on restoring normal execution as quickly as possible. We are closely monitoring the system and affected tenants.

Recovery Options (unchanged):

Manual Run: High-priority campaigns can be triggered manually using Run Now in Mission Control.

Force Run: If enabled, campaigns will still deliver once the issue is resolved within the grace period.

Next Update:
We will provide another update within 1–2 hours, or sooner if there are any meaningful changes.
Jan 23, 05:47 UTC
Investigating - We are currently experiencing errors leading to delays in campaign execution. As a result, some campaigns may remain in a “Not Run” status.
This typically occurs when the Batch Data Update is delayed and campaign execution starts later than scheduled, causing some campaigns to miss their designated run time.

What We’re Doing:
Our engineering team is actively investigating the root cause and working to restore normal execution as quickly as possible.

Recovery Options:

Manual Run:
For high-priority campaigns, you can run them manually via the Run Now feature in Mission Control. Hover over the relevant campaign or use the three-dot menu to access the option. https://academy.optimove.com/hc/en-us/articles/8649444827549-Using-Run-Now-Capability

Force Run:
If your instance has Force Run enabled, campaigns will still be delivered as part of the batch process if this incident is resolved within the grace period. https://academy.optimove.com/hc/en-us/articles/10701094593565-Using-Force-Run.
To enable Force Run, please reach out to your Customer Success Manager.

Next Update:
We will provide an update within 1–2 hours, or sooner if new information becomes available
Jan 23, 02:43 UTC
Jan 22, 2026
Degraded performance in Real Time Track and Trigger (USA)
Resolved - This incident has been resolved.
Jan 22, 09:12 UTC
Monitoring - Our teams are investigating the issue and have identified conditions that affected system stability. We are actively working to restore normal operation and have placed the service under close monitoring to ensure continued stability. Additional updates will follow.
Jan 21, 20:48 UTC
Update - We are continuing to work on stabilizing the system. At this time, the service remains in a degraded state, and while mitigation efforts are ongoing, the root cause has not yet been identified. Our teams are actively investigating and will provide further updates as soon as more information becomes available.
Jan 21, 19:58 UTC
Investigating - We are seeing degraded performance affecting the Real Time Track and Trigger component in the USA region. This can result in delays or slower processing of real-time events and may impact US Track and Trigger campaigns.
Jan 21, 19:04 UTC
Jan 21, 2026
Jan 20, 2026
OptiText SMS - Processing and delivery failures
Resolved - This incident has been resolved.
Jan 20, 13:22 UTC
Monitoring - A fix has been implemented and we are monitoring the results.
Jan 20, 12:19 UTC
Identified - We’ve identified an issue impacting OptiText SMS message sending/delivery related to a change made by an external SMS provider. We’re working closely with the provider to restore normal service.
Jan 20, 09:35 UTC
Investigating - We’re investigating an issue impacting OptiText SMS message sending/delivery. Our team is working to identify the cause and restore normal service.
Jan 20, 08:06 UTC
Jan 19, 2026

No incidents reported.

← Incident History Powered by Atlassian Statuspage