Batch had 45 outages in the last 2 years totaling 132h 17m of downtime — averaging 1.8 incidents per month.
There were 45 Batch outages since May 20, 2025 totaling 132h 17m of downtime. Each is summarised below — incident details, duration, and resolution information.
Between September 16, 12:00 CEST and 13:30 CEST, some requests to our public APIs returned errors at an elevated rate (approximately 2% of all requests). Affected requests could be safely retried, and all services had returned to normal by 13:49 CEST. The incident was caused by a database issue.
Between September 5 at 11:45 CEST and September 7 at 08:25 CEST, we experienced delays in indexing MEP and CEP audiences. The situation is now back to normal, and we are continuing to monitor it closely.
Between 07:10 CEST and 10:18 CEST, some requests to create or update MEP Custom Audiences intermittently failed. A fix was applied at 10:18 CEST and no further errors have been observed since. We are continuing to monitor the situation closely.
We have identified an issue preventing the delivery of Android push notifications. Since August 15, 09:52 CEST, notifications sent to Android devices are not being delivered.
We have identified the cause of the issue and the delivery of Android push notifications is back to normal. The backlog has been fully processed and notifications are being delivered in real time again. No data has been lost, all notifications were delivered to the expected users. We continue to monitor the platform closely.
This incident has been resolved.
Since approximately 15:25 CEST, our email composer provider is experiencing an issue on their infrastructure, which impacts the email editor. You may be unable to edit email messages in the composer. Email delivery is not affected. The issue has been escalated to the provider and we will share updates as soon as more information becomes available.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
Since 11:40 CEST, push notifications to Android devices (FCM) are not being sent on CEP. MEP push delivery is not affected, and iOS push delivery on CEP works as expected. We are investigating the issue and will share updates as soon as more information becomes available.
iOS (APNs) push delivery on CEP is also impacted and currently heavily degraded, in addition to Android (FCM) notifications which are still not being sent. We have identified the root cause and are actively working on the fix. MEP push delivery remains unaffected.
Push delivery on CEP has recovered: notifications are being sent normally again on both Android (FCM) and iOS (APNs). We are monitoring the platform to confirm stability. We are still assessing whether notifications that could not be sent during the incident will be retried, we will share an update on this.
We are continuing to monitor for any further issues.
This incident has been resolved.
We are investigating increased processing delays affecting CEP Exports an Cloud Sync synchronizations since July 16, 22:00 CEST. Some operations may be processed later than expected. Our team is actively working to restore normal processing, and we will share further updates as soon as more information is available.
We are continuing to investigate this issue.
Processing has returned to normal for CEP Exports and Cloud Sync synchronizations. The backlog has been fully processed and no data has been lost.
We have identified an issue affecting the processing of CEP trigger automations. Since approximately 08:00 CEST, automation events have been processing with a delay of up to 30 minutes This affects the delivery of Push, Email, and SMS messages triggered by these automations. No data has been lost; messages will be delivered to the expected users as the backlog clears. We are working on resolving the issue and are monitoring the situation closely.
The issue has been resolved and the backlog has been fully processed.
This incident is now resolved.
Between 12:27 and 16:29 CEST, we experienced delays in serving in-app messages on both our MEP and CEP platforms. This impacted all applications using an SDK version 3.1 or higher. The issue has been resolved and performance is back to normal. We continue to monitor our systems closely to ensure everything remains stable.
We are currently investigating an issue affecting profile update processing on our CEP platform. Since approximately 09:20 CEST today, profile data (including custom attributes and events) is no longer being updated in real-time. As a result: - Campaigns targeting users based on profile attributes may reach an inaccurate audience. - Trigger automations based on profile attribute changes are currently not firing. Message delivery for ongoing orchestrations (push, email, and SMS) is unaffected, as are device installs and tokens. No data is lost, profile updates will be applied once the issue is resolved and the backlog is processed.
Profile attribute and event updates sent via the Profile API have returned to real-time as of 12:14 CEST. The backlog accumulated since 09:20 CEST has been fully processed. Updates ingested via the mobile SDK are currently running approximately 45 minutes behind. Trigger automations based on profile attribute changes also remain affected, the root cause has been identified and a fix is in progress.
Profile data updates ingested via the mobile SDK are now running approximately 10 minutes behind, down from 45 minutes previously. Data used for campaign selection and attribute-based trigger automations remains approximately 1 hour behind schedule. Our team continues to work on a full resolution. We will provide a further update as soon as more information is available, or within the next hour.
This incident has been resolved. Profile data is now being updated in real-time across all ingestion channels. Campaign selections and attribute-based trigger automations are back to normal. No data was lost during the incident. Profile updates that occurred between June 19, 09:20 CEST and the resolution time have been fully processed.
Between May 8 at 01:00 CEST and 7:14 CEST, a subset of CEP recurring automations failed to execute as scheduled. Affected automations were not sent during this window and were not retried. The issue has been resolved. The service has been operating normally since 7:14 CEST.
We are investigating an issue affecting push notification delivery via the [MEP] Transactional API. Notifications submitted since 14:20 CEST may not be delivered. Our team is working to identify the cause.
We have identified the cause of the issue. A recent configuration change caused push notifications submitted via the Transactional API to not reach our delivery pipeline. A fix is being deployed. Once it is in place, affected notifications will be delivered and no data will be lost.
A fix has been deployed and the backlog of delayed notifications has been processed. New notifications are being sent as expected. We are monitoring the results.
All delayed notifications have been processed, and new notifications are now being delivered as expected. The incident is resolved, and all services are operating normally.
Our profile data indexation pipeline experienced instability starting at May 7, 05:30 CEST, causing it to fall behind on processing. As a result, profile data used for CEP one-time and recurring campaign targeting was delayed by up to 2 hours 30 minutes for a subset of traffic. The issue has been resolved. Processing has resumed and is recovering. We are monitoring the situation closely.
Profile data indexation has returned to normal. One-time and recurring CEP campaigns are now using up-to-date profile data for targeting and personalization. No data has been lost during this incident.
Between May 4, 2026 at 00:00 CEST and May 4, 2026 at 09:30 CEST, approximately 25% of requests serving the Web SDK were failing. This prevented the SDK from loading on some web pages, and as a result, some events may not have been tracked during this period. Push notifications were not affected and were delivered as expected throughout the incident.
We are experiencing an infrastructure issue impacting parts of our platform. Campaign sending on MEP and the MEP Audiences API have been unavailable since 22:45 CET. CEP exports (recurring and API) have been experiencing slowdowns on some jobs since 23:10 CET. Other platform features are operating normally. Our team is actively working on restoring service.
We have identified the root cause of this incident. A failure on a subset of our infrastructure servers is preventing MEP campaigns from being sent and the MEP Audiences API from responding. CEP exports are also experiencing slowdowns on some jobs as a secondary effect. Our team is actively working on restoring the affected services.
MEP campaign delivery has been restored. Campaigns planned since 22:45 CET are currently being sent, and the MEP Audiences API is back to normal. We are monitoring the platform to ensure stability. CEP export slowdowns (recurring and API) remain under investigation.
This incident has been resolved. The exports have been back up since 09:45 CET, pending requests are still being processed.
We are investigating delays affecting CEP campaigns (one shot & recurring). As of writing, processing is approximately 1 hour behind schedule. In-app messages and automations are not affected. Campaigns will be sent to the expected users as the backlog clears.
CEP campaigns (one-shot and recurring automations) are back to normal. The backlog was fully processed at 16:25 CET, and campaigns sent as of now work as expected. No data has been lost.
The service has been restored and has been under monitoring for 48 hours with no regressions observed.
We are investigating a performance degradation within our profile processing pipeline. This issue specifically affects updates sent via our mobile SDKs. As of 21/02/2026 at 17:00 CET, processing times have increased, with current delays of up to 3 hours. This latency may result in delayed execution for triggered automations.
We have identified the issue and deployed a fix. The processing backlog is now beginning to clear, and delivery delays are steadily decreasing. We are monitoring the pipeline closely to ensure performance returns to nominal levels.
The processing backlog has been steadily decreasing over the last hour. We continue to monitor the situation closely until all updates are processed and real-time performance is restored.
This incident has been resolved.
We are currently experiencing an issue with our email composer provider that prevents image uploads from functioning correctly. The issue has been escalated to the provider, and we are awaiting a fix on their side. We will share further updates as soon as more information becomes available.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
Summary: Between 15 January at 18:00 CET and 15 January at 19:00 CET, a small subset of CEP trigger automations was delayed for up to an hour. Only trigger automations using timers and with timers scheduled to fire between 18:00 and 19:00 CET were affected; this represents less than 2% of all trigger automations during this time period. Impact for the affected trigger automations: * Timer firing was delayed by up to one hour. * As a consequence, the delivery of emails, SMS, and push notifications was delayed by up to one hour. Root Cause: some timers were not accepted by our database system due to an edge case in their data, which blocked the entire timer scheduling pipeline. Resolution: a fix was deployed on 15 January at 18:55 CET, which resolved the issue. By 19:00 CET, the backlog was cleared.
Jan 7, 07:54 UTC Resolved - Trigger automations ran late between 07:00 and 08:40 CET. All messages were delivered; none were lost.
Between November 22nd at 10:30 CET and 12:08 CET, a performance issue on a database cluster impacted the delivery of Push notifications, SMS, and emails. Impact: * Event processing: Delayed by up to 1 hour and 30 minutes for a subset of users. * Campaign processing: Delayed by up to 2 hours for a subset of campaigns. * Delivery failures: A subset of campaign tasks timed out during processing and were not delivered. Resolution: A mitigation was applied at 12:08 CET, which restored normal processing performance. The resulting backlog was fully cleared by 12:25 CET.
Between November 14th at 10:17 (CET) and November 14th at 10:31 (CET), the Profile API and Catalog API experienced an incident during which HTTP 500 errors were returned on all requests, impacting 100% of the traffic during this period. Those requests have not been processed and can be safely retried.