Batch had 44 outages in the last 2 years totaling 547h 43m of downtime — averaging 1.8 incidents per month.
There were 44 Batch outages since March 24, 2025 totaling 547h 43m of downtime. Each is summarised below — incident details, duration, and resolution information.
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 currently experiencing an issue with our email composer provider that is impacting the email editor. Since 10:01 CEST, initializing the email composer may fail or be significantly delayed. The issue has been escalated to our third-party provider, and we are awaiting a fix on their side.
A fix has been deployed by our email composer provider and the email editor is initializing normally again. We are monitoring the situation to ensure stability before resolving the incident.
This incident has been resolved. Between 10:01 CEST and 10:30 CEST, our email composer provider experienced degraded performance that prevented or delayed the initialization of the email editor. A fix was deployed on the provider side and service is back to normal.
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.
Since 06:24 CET, CEP Trigger automations have been running late. We identified the cause and deployed a fix. Deliveries may be delayed by up to 90 minutes while the backlog processes. We are monitoring recovery.
The backlog has been processed, the trigger automations are now live.
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.
At 10:50 CET we performed a routine rotation of our TLS certificates; this unexpectedly caused images to appear blank in Push and In-App messages for some users. Affected devices: - iPhones/iPads running on iOS 17.7 or older - A very small percentage of Android devices The issue was resolved at 17:40 CET
We are currently experiencing a delay in indexing messages from our SDKs. At the moment, message indexing is running approximately 1 hour behind. This delay impacts only the updating of Profile events and attributes. Specifically: • The profile view is not updated in real-time. • Some automations may be triggered later than expected.
We are continuing to investigate this issue.
As of 15:15 (GMT+2), the situation is under control. Indexing delays on CEP have been resolved, Profile updates and custom event processing are now back to real-time. We’re continuing to monitor the platform to ensure stability.
This incident has been resolved.
Oct 19, 08:00 UTC Completed - The scheduled maintenance has been completed. Oct 19, 07:00 UTC In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary. Oct 6, 08:28 UTC Scheduled - Our Email Composer partner will be performing an infrastructure update on October 19, 2025, from 09:00 to 10:00 CEST (UTC+2). During this window, the Email Composer may be unavailable. You won’t be able to: • Edit email messages in the composer • Edit your templates • Upload new images
Impact: In some cases, automation workflows that include Yes/No steps and/or Delay steps can stall. Affected profiles remain stuck and may miss subsequent communications. Estimated impact: ~1% of users. Scope: Limited to automations using both Yes/No and/or Delay steps. Other automations are not affected. Current status: We have identified the defect and are developing a fix. No workaround is available at this time. Next steps: The fix will be deployed after validation. We apologize for the disruption and appreciate your patience.
The fix is in testing and targeted for release early next week. Next update: Monday, August 25, by 18:00 CEST
A fix for this issue has been implemented, we are now monitoring the results.
The issue affecting automation workflows with Yes/No and/or Delay steps has been resolved. The fix has been successfully deployed and results have been monitored without further impact. All CEP Core Services (Email, Push, SMS delivery) are now operating normally. We apologize for the disruption and thank you for your patience.
Following a maintenance operation on our data‑storage system, CEP automation triggers have been processing more slowly than expected. Our engineering team is analysing the issue and working to restore normal performance. We will provide further updates as soon as we have more information.
We have rolled back the database maintenance operation, and all automation triggers have now processed their backlog. All CEP campaigns with Push, Email & SMS are now back online. We are actively monitoring the situation and will provide further updates as we progress.
This incident has been resolved.
Since May 15, around 16:00 CEST, we have been experiencing issues indexing “open push” events on the CEP platform, impacting all push types. This indexing issue led to partial data loss, causing incomplete or missing data in dashboards, APIs, exports, and affecting retargeting campaigns based on open events. Not all data was impacted, but some events remain unrecoverable. A fix has been deployed, and you may now observe an increase in open rates compared to previous days. We will keep you informed of any further updates on this page.
This incident has been resolved.
Starting July 30 at 00:13 CEST, we began experiencing intermittent delays affecting CEP Trigger Automations. During the night, the issue was limited to email channels and impacted approximately 2% of traffic. The problem escalated between 10:20 and 10:44 CEST on July 31, affecting all triggered sends across email, SMS, and push channels, with delays of approximately 15 minutes. The backlog has since been cleared. We are currently implementing a permanent fix and continuing to monitor the system closely. No further delays have been observed.
A fix has been deployed to production, and CEP Trigger Automations are now operating normally across all channels. Additional tests have been added to prevent this issue from recurring.
Since 24 July at 22:34 CEST, we are experiencing an indexing delay in part of our indexing pipeline. This issue affects: - The availability of new Profile attributes in the dashboard autocomplete - Profile analytics, which may display inaccurate data We are actively working to resolve the issue and will provide updates as soon as possible.