Optimove Outage History

Started Aug 07, 2026, 03:27 AM UTC· resolved Aug 07, 2026, 07:26 PM UTC

1. investigating Aug 07, 2026, 03:27 AM UTC

   On August 6, we experienced an internal issue affecting Email campaign execution. As a result, some campaigns scheduled during the affected timeframe were not executed as expected. Where possible, eligible affected campaigns were rerun. Campaigns with future recurring occurrences will continue according to their regular schedule. We apologize for the inconvenience caused.

2. investigating Aug 07, 2026, 03:28 AM UTC

   We are continuing to investigate this issue.

3. investigating Aug 07, 2026, 06:54 AM UTC

   Investigating - We have identified an issue affecting the execution of some Optimail campaigns on August 6 and August 7. Our teams are currently reviewing the affected campaigns and monitoring campaign execution while Engineering continues to investigate the issue. We will provide further updates as more information becomes available.

4. investigating Aug 07, 2026, 10:08 AM UTC

   We continue to investigate an issue affecting the execution of some Optimail campaigns on August 6 and August 7. Our teams are reviewing affected campaigns, rerunning eligible campaigns where possible, and closely monitoring campaign execution. We will provide further updates as more information becomes available.

5. identified Aug 07, 2026, 11:35 AM UTC

   Identified – We have identified the issue affecting some Optimail campaign executions in the EU region. Customers in the EU region are advised not to manually rerun affected campaigns at this time while our team deploys a fix. Our teams are actively working on remediation. Campaigns in the US region are not affected and can be retried as needed. We will provide an update once affected campaigns can be safely retried.

6. monitoring Aug 07, 2026, 11:49 AM UTC

   Monitoring – The fix has been completed, and Optimail campaigns in the EU region are now processing normally. Campaign execution retries in the EU are safe to resume. Our teams will continue monitoring campaign execution to ensure stability. Please feel free to rerun campaigns now.

7. resolved Aug 07, 2026, 07:26 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Jul 19, 2026, 09:12 AM UTC· resolved Jul 19, 2026, 11:50 AM UTC

1. monitoring Jul 19, 2026, 09:12 AM UTC

   What's happening Meta (Facebook) is experiencing a service disruption. Because campaign delivery to this channels depends on Meta's APIs, some Optimove campaigns targeting Meta audiences are affected. How this may affect you - Campaigns sending to Meta may fail - Audience syncs to Meta Custom Audiences may stall or error out - Delivery reports and channel metrics for Meta may be delayed or incomplete Important: This is a Meta-side outage, not an Optimove platform issue. Campaigns on all other channels (email, SMS, push, web, and other integrations) are unaffected and running normally. What we're doing Monitoring Meta's status. We will confirm here when Meta service is restored and Meta-channel execution is back to normal.

2. resolved Jul 19, 2026, 11:50 AM UTC

   Meta services have recovered and campaign delivery to Facebook has resumed.

Read the full incident report →

Started Jul 08, 2026, 01:21 PM UTC· resolved Jul 08, 2026, 02:02 PM UTC

1. investigating Jul 08, 2026, 01:21 PM UTC

   We are currently experiencing errors leading to delays in Daily Batch. As a result, some campaigns may remain in a “Not Run” status. 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

2. resolved Jul 08, 2026, 02:02 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Jul 04, 2026, 12:15 PM UTC· resolved Jul 04, 2026, 06:43 PM UTC

1. investigating Jul 04, 2026, 12:15 PM UTC

   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

2. investigating Jul 04, 2026, 12:16 PM UTC

   We are continuing to investigate this issue.

3. monitoring Jul 04, 2026, 01:58 PM UTC

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

4. monitoring Jul 04, 2026, 06:36 PM UTC

   We are continuing to monitor for any further issues.

5. resolved Jul 04, 2026, 06:43 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Jun 06, 2026, 04:19 AM UTC· resolved Jun 06, 2026, 12:52 PM UTC

1. investigating Jun 06, 2026, 04:19 AM UTC

   We are currently experiencing errors leading to delays in the daily data update process for some instances. As a result, campaigns scheduled to run after the daily update may be delayed or may remain in a “Not Run” status. This issue affects only some instances using the impacted daily update workflow. Instances using other daily update workflows are not affected. This typically occurs when the daily data update process after the ETL phase is delayed or fails, preventing campaign execution from starting as scheduled and 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.

2. monitoring Jun 06, 2026, 06:36 AM UTC

   A fix has been applied, and the affected daily data update process is now showing signs of recovery. We are currently re-initiating previously failed batch updates in a controlled manner to avoid creating additional load. Some customers may continue to experience delays while these updates are being processed. Next Steps: We are continuing to resume the affected batch update processes and monitor their successful completion. Next Update: We will provide another update within 1–2 hours, or sooner if normal operation is fully restored.

3. resolved Jun 06, 2026, 12:52 PM UTC

   This incident has been resolved.

Read the full incident report →

Started May 19, 2026, 01:06 PM UTC· resolved May 19, 2026, 02:37 PM UTC

1. monitoring May 19, 2026, 01:06 PM UTC

   We identified and resolved a service degradation in our EU environment that impacted some customers. During the affected window, Web SDK events delivery into the Triggered Campaigns path was disrupted, which delayed or prevented triggered campaigns from firing for the impacted accounts. Server-side events, as well as standard Web SDK events, were unaffected throughout the incident. IMPACT - Affected: Triggered Campaigns powered by Web SDK events in the EU region. - Not affected: Server-side event ingestion, scheduled campaigns, Standard Wed SDK Events - Customers may observe a temporary dip in Triggered Campaign volume corresponding to the affected window. ROOT CAUSE The disruption was caused by an infrastructure change deployed in our EU environment on May 18-19, which inadvertently affected the path used to deliver Web SDK events into the platform. NEXT STEPS - We are conducting an internal post-incident review to prevent recurrence. - We are reinforcing our pre-deployment validation for infrastructure changes that affect event ingestion paths. - Events that did not reach the platform during the incident window cannot be retroactively replayed; data captured via server-side integrations during this period is intact. NEED HELP? If you believe your account experienced impact beyond what is described above, please contact us at [email protected] We sincerely apologize for the disruption and appreciate your patience.

2. resolved May 19, 2026, 02:37 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Apr 22, 2026, 06:56 PM UTC· resolved Apr 22, 2026, 07:34 PM UTC

1. investigating Apr 22, 2026, 06:56 PM UTC

   We are currently investigating reports of slow response times and intermittent errors when logging into the platform, and our engineering team is actively working to restore full service as quickly as possible.

2. identified Apr 22, 2026, 07:01 PM UTC

   Our authentication service is currently experiencing performance degradation that may result in slow response times or errors when accessing the site, and we are closely monitoring their progress toward a resolution.

3. monitoring Apr 22, 2026, 07:10 PM UTC

   The issues affecting our login service have been resolved, and we are now closely monitoring performance to ensure continued stability for all users.

4. resolved Apr 22, 2026, 07:34 PM UTC

   This incident has been resolved

Read the full incident report →

Started Apr 20, 2026, 08:00 AM UTC· resolved Apr 20, 2026, 08:00 AM UTC

1. monitoring Apr 20, 2026, 07:00 AM UTC

   THIS IS A SCHEDULED EVENT Apr 20, 07:00 - 08:00 UTC Mar 31, 12:33 UTC Scheduled - We will be performing a scheduled upgrade to the Templates Service. During this window, Templates Service will be unavailable for up to 15 minutes. This means that Template retrieval and updates will fail, causing scheduled and triggered campaign failures for native channels within the 15 minute maintenance window. Transactional sends are not expected to be impacted. Further updates will be shared as needed.

Read the full incident report →

Started Apr 19, 2026, 08:53 PM UTC· resolved Apr 22, 2026, 09:48 AM UTC

1. monitoring Jun 15, 2026, 10:00 AM UTC

   THIS IS A SCHEDULED EVENT Jun 15, 10:00 - 13:00 UTC Jan 27, 16:16 UTC Scheduled - 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 [email protected] 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.

Read the full incident report →

Started Apr 19, 2026, 08:53 PM UTC· resolved Apr 22, 2026, 09:48 AM UTC

1. monitoring Apr 27, 2026, 11:00 AM UTC

   THIS IS A SCHEDULED EVENT Apr 27, 11:00 - 12:00 UTC Apr 15, 09:24 UTC Scheduled - Optimove’s SFTP infrastructure in the EU region is getting updated. We do not expect service interruption beyond the brief SFTP unavailability, and our teams are actively monitoring throughout the maintenance. Maintenance Window & Impact During the update, SFTP file loading may be unavailable for up to 10 minutes. Customers may receive Missing file notifications, which will only occur once the tenant’s batch process begins. These notifications are independent of the exact timing of the maintenance window. Additional Considerations There is higher risk for very large files to be affected during this period. Customers are advised to proactively verify file availability after the maintenance window to ensure smooth processing. Support For any questions or assistance, please contact [email protected].

Read the full incident report →

Started Apr 19, 2026, 08:53 PM UTC· resolved Apr 22, 2026, 09:48 AM UTC

1. monitoring May 04, 2026, 11:00 AM UTC

   THIS IS A SCHEDULED EVENT May 4, 11:00 - 12:00 UTC Apr 15, 09:23 UTC Scheduled - Optimove’s SFTP infrastructure in the US region is getting updated. We do not expect service interruption beyond the brief SFTP unavailability, and our teams are actively monitoring throughout the maintenance. Maintenance Window & Impact During the update, SFTP file loading may be unavailable for up to 10 minutes. Customers may receive Missing file notifications, which will only occur once the tenant’s batch process begins. These notifications are independent of the exact timing of the maintenance window. Additional Considerations There is higher risk for very large files to be affected during this period. Customers are advised to proactively verify file availability after the maintenance window to ensure smooth processing. Support For any questions or assistance, please contact [email protected].

Read the full incident report →

Started Apr 14, 2026, 02:00 PM UTC· resolved Apr 14, 2026, 02:00 PM UTC

1. monitoring Apr 14, 2026, 02:00 PM UTC

   Apr 14, 14:00 UTC Completed - The scheduled maintenance has been completed. Apr 14, 13:00 UTC In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary. Mar 12, 10:20 UTC Scheduled - Optimove’s SFTP infrastructure in the US region will undergo an upgrade to improve stability and performance. We do not expect service interruption beyond the brief SFTP unavailability, and our teams are actively monitoring throughout the maintenance. Maintenance Window & Impact During the update, SFTP file loading may be unavailable for up to 10 minutes. Customers may experience Missing file notifications, which will only occur once the tenant’s batch process begins. These notifications are independent of the exact timing of the maintenance window. Additional Considerations There is higher risk for very large files to be affected during this period. Customers are advised to proactively verify file availability after the maintenance window to ensure smooth processing. Support For any questions or assistance, please contact [email protected].

Read the full incident report →

Started Apr 10, 2026, 10:24 AM UTC· resolved Apr 10, 2026, 10:24 AM UTC

1. monitoring Apr 10, 2026, 10:24 AM UTC

   Apr 10, 10:24 UTC Resolved - This incident has been resolved. Apr 10, 10:05 UTC Monitoring - A fix has been implemented for the issue affecting campaign creation in the Campaign Builder. We are monitoring the results to ensure stability. Apr 10, 08:49 UTC Identified - The issue has been identified and a fix is being implemented. Apr 10, 08:41 UTC Investigating - We are investigating an issue affecting the Campaign Builder, where some users may be unable to create campaigns. Our team is working to identify the root cause and restore normal functionality as quickly as possible.

Read the full incident report →

Started Apr 07, 2026, 09:22 AM UTC· resolved Apr 07, 2026, 09:22 AM UTC

1. monitoring Apr 07, 2026, 09:22 AM UTC

   Apr 7, 09:22 UTC Resolved - This incident has been resolved. Apr 7, 09:22 UTC Monitoring - A fix has been implemented and we are monitoring the results. Apr 7, 08:10 UTC Identified - The issue has been identified and a fix is being implemented. Apr 7, 07:51 UTC Investigating - We are currently investigating this issue.

Read the full incident report →

Started Mar 23, 2026, 04:46 PM UTC· resolved Mar 23, 2026, 04:46 PM UTC

1. monitoring Mar 23, 2026, 04:46 PM UTC

   Mar 23, 16:46 UTC Resolved - We have confirmed that the issue affecting the Target Group Configuration section has been resolved, and the "Show Size" functionality is now operating normally. We will continue to monitor to ensure ongoing stability. Mar 23, 15:15 UTC Monitoring - We identified an issue affecting the Target Group Configuration section, where the "Show Size" functionality could return "N/A" or fail to load. We have rolled back a recent change, and service is improving. This issue is limited to the UI display only. Target Group size continues to be calculated correctly during campaign execution, and campaigns are not impacted. We are continuing to monitor the situation to ensure full resolution. Mar 23, 15:05 UTC Identified - We are currently experiencing an issue where the Target Group (TG) size cannot be calculated in the Target Group Configuration section. As a result, the "Show Size" functionality may return "N/A" or fail to load. This issue is limited to the UI display only. Target Group size is still calculated correctly during campaign execution, and campaigns are not impacted. Our team is actively investigating the issue and working toward a resolution.

Read the full incident report →

Started Mar 23, 2026, 01:00 PM UTC· resolved Mar 23, 2026, 01:00 PM UTC

1. monitoring Mar 23, 2026, 01:00 PM UTC

   Mar 23, 13:00 UTC Completed - The scheduled maintenance has been completed. Mar 23, 07:00 UTC In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary. Mar 22, 15:13 UTC Scheduled - On March 23rd starting at 07:00 UTC, we will be performing an infrastructure update to improve system stability. No downtime or customer impact is expected. The update will be applied across all regions simultaneously, and our team will closely monitor the process.

Read the full incident report →

Started Mar 23, 2026, 12:00 PM UTC· resolved Mar 23, 2026, 12:00 PM UTC

1. monitoring Mar 23, 2026, 12:00 PM UTC

   Mar 23, 12:00 UTC Completed - The scheduled maintenance has been completed. Mar 23, 11:00 UTC In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary. Mar 12, 10:23 UTC Scheduled - Optimove’s SFTP infrastructure in the EU region will undergo an upgrade to improve stability and performance. We do not expect service interruption beyond the brief SFTP unavailability, and our teams are actively monitoring throughout the maintenance. Maintenance Window & Impact During the update, SFTP file loading may be unavailable for up to 10 minutes. Customers may experience Missing file notifications, which will only occur once the tenant’s batch process begins. These notifications are independent of the exact timing of the maintenance window. Additional Considerations There is higher risk for very large files to be affected during this period. Customers are advised to proactively verify file availability after the maintenance window to ensure smooth processing. Support For any questions or assistance, please contact [email protected].

Read the full incident report →

Started Mar 17, 2026, 02:55 PM UTC· resolved Mar 17, 2026, 02:55 PM UTC

1. monitoring Mar 17, 2026, 02:55 PM UTC

   Mar 17, 14:55 UTC Resolved - This incident has been resolved. Mar 17, 14:13 UTC Update - A fix has been implemented and we are monitoring the results. Mar 17, 14:01 UTC Monitoring - A fix has been implemented and we are monitoring the results. Mar 17, 13:37 UTC Update - We have identified the source of the issue leading to delays in campaign execution - Mitigation is in progress. Our team is working to restore normal service and will provide another update soon. Mar 17, 12:49 UTC Identified - We are currently experiencing an issue causing unexpected errors and delays in campaign execution. What we’re doing- Our engineering team is actively investigating the root cause and working to restore normal execution as quickly as possible. Next update- We will provide an update within 1–2 hours, or sooner if there are any significant developments.

Read the full incident report →

Started Mar 14, 2026, 10:10 AM UTC· resolved Mar 14, 2026, 10:10 AM UTC

1. monitoring Mar 14, 2026, 10:10 AM UTC

   Mar 14, 10:10 UTC Resolved - This incident has been resolved. Mar 14, 09:02 UTC Investigating - We are currently experiencing unexpected errors leading to delays in campaign execution. What We’re Doing: Our engineering team is actively investigating the root cause and working to restore normal execution as quickly as possible. Next Update: We will provide an update within 1–2 hours, or sooner if new information becomes available

Read the full incident report →

Started Mar 10, 2026, 02:00 PM UTC· resolved Mar 10, 2026, 02:00 PM UTC

1. monitoring Mar 10, 2026, 02:00 PM UTC

   Mar 10, 14:00 UTC Completed - The scheduled maintenance has been completed. Mar 10, 13:00 UTC In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary. Jan 12, 08:39 UTC Scheduled - 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: [email protected]

Read the full incident report →

Started Mar 09, 2026, 12:30 PM UTC· resolved Mar 09, 2026, 12:30 PM UTC

1. monitoring Mar 09, 2026, 12:30 PM UTC

   Mar 9, 12:30 UTC Completed - The scheduled maintenance has been completed. Mar 9, 11:30 UTC In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary. Feb 2, 13:30 UTC Scheduled - 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: [email protected]

Read the full incident report →

Started Mar 03, 2026, 12:20 PM UTC· resolved Mar 03, 2026, 12:20 PM UTC

1. monitoring Mar 03, 2026, 12:20 PM UTC

   Mar 3, 12:20 UTC Resolved - The issue affecting all Support email inboxes has been resolved. Email processing has resumed, and queued messages are being processed. You may experience short-term delays as we work through the backlog. We do not expect further impact. Thank you for your patience. Mar 3, 11:48 UTC Identified - We have identified the root cause of the issue affecting all Support email inboxes and are working with our service provider on remediation. We expect the issue to be resolved within the next 45 minutes. Emails remain queued and will be processed once service is fully restored. Some response delays and potential SLA impact may occur. For urgent matters, please continue using the Optimove Academy “Submit a request” form or the in-app /help widget. We will provide confirmation once the issue is fully resolved. Mar 3, 10:21 UTC Update - Note: Emails are being queued and will be processed once service is restored. Some response delays and potential SLA impact may occur. Mar 3, 10:20 UTC Investigating - We’re currently investigating an issue where emails sent to our Support inbox are not being processed as expected, which may delay ticket creation and responses. Workaround: Please submit your request via the Optimove Academy “Submit a request” form or use the in-app/help widget to reach our Support teams while we work to restore normal email processing.

Read the full incident report →

Started Jan 24, 2026, 02:46 PM UTC· resolved Jan 24, 2026, 02:46 PM UTC

1. monitoring Jan 24, 2026, 02:46 PM UTC

   Jan 24, 14:46 UTC 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:24 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:03 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, 12:58 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.

Read the full incident report →

Started Jan 22, 2026, 09:12 AM UTC· resolved Jan 22, 2026, 09:12 AM UTC

1. monitoring Jan 22, 2026, 09:12 AM UTC

   Jan 22, 09:12 UTC Resolved - This incident has been resolved. Jan 21, 20:48 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, 19:58 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:04 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.

Read the full incident report →

Started Jan 20, 2026, 01:22 PM UTC· resolved Jan 20, 2026, 01:22 PM UTC

1. monitoring Jan 20, 2026, 01:22 PM UTC

   Jan 20, 13:22 UTC Resolved - This incident has been resolved. Jan 20, 12:19 UTC Monitoring - A fix has been implemented and we are monitoring the results. Jan 20, 09:35 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, 08:06 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.

Read the full incident report →