Aug <var data-var='date'>15</var>, <var data-var='time'>10:42</var> UTC Resolved - This incident has been resolved. Aug <var data-var='date'>15</var>, <var data-var='time'>10:32</var> UTC Monitoring - 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. Aug <var data-var='date'>15</var>, <var data-var='time'>09:34</var> UTC Investigating - 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.

CEP Push Delivery Issue (FCM)

Jul <var data-var='date'>28</var>, <var data-var='time'>14:13</var> UTC Resolved - This incident has been resolved. Jul <var data-var='date'>28</var>, <var data-var='time'>13:51</var> UTC Monitoring - A fix has been implemented and we are monitoring the results. Jul <var data-var='date'>28</var>, <var data-var='time'>13:39</var> UTC Investigating - 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.

Email Composer – Service Unavailable

Jul <var data-var='date'>23</var>, <var data-var='time'>11:08</var> UTC Resolved - This incident has been resolved. Jul <var data-var='date'>23</var>, <var data-var='time'>10:40</var> UTC Update - We are continuing to monitor for any further issues. Jul <var data-var='date'>23</var>, <var data-var='time'>10:35</var> UTC Monitoring - 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. Jul <var data-var='date'>23</var>, <var data-var='time'>10:17</var> UTC Identified - 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. Jul <var data-var='date'>23</var>, <var data-var='time'>10:11</var> UTC Investigating - 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.

Android push (FCM) delivery outage on CEP

Jul <var data-var='date'>17</var>, <var data-var='time'>14:25</var> UTC Resolved - Between July 17 at 15:30 CEST and 16:05 CEST, FCM push notifications were not delivered on the CEP platform. Notifications scheduled during this window were not sent and will not be retried. Analytics will show zero delivery for the affected notifications. If impacted, consider resending your campaign. The issue has been resolved and delivery is back to normal.

Jul <var data-var='date'>17</var>, <var data-var='time'>11:24</var> UTC Resolved - Processing has returned to normal for CEP Exports and Cloud Sync synchronizations. The backlog has been fully processed and no data has been lost. Jul <var data-var='date'>17</var>, <var data-var='time'>10:23</var> UTC Update - We are continuing to investigate this issue. Jul <var data-var='date'>17</var>, <var data-var='time'>10:21</var> UTC Investigating - 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.

Processing delays on CEP Exports & Cloud Sync

Jul <var data-var='date'> 7</var>, <var data-var='time'>22:09</var> UTC Resolved - This incident is now resolved. Profile updates are being processed in real time again, and the data used for one-time and recurring campaign targeting, and attribute-change automations has fully caught up, with no profile data lost. Separately, the earlier disruption to transactional message sending and in-app display on July 7 between 19:45 and 20:15 CEST was resolved the same evening. All services are operating normally. Jul <var data-var='date'> 7</var>, <var data-var='time'>21:34</var> UTC Update - Profile updates are now being processed in real time again at the source, and profile analytics have caught up. A downstream indexing backlog remains, however: the profile data used for campaign targeting, including targeting based on attribute changes, is currently delayed by under an hour and is steadily catching up. No profile data has been lost, and all updates will be reflected once the backlog fully clears. We continue to monitor closely and will share a further update tomorrow morning. Jul <var data-var='date'> 7</var>, <var data-var='time'>19:58</var> UTC Update - Between 19:45 and 20:15 CEST, a disruption affected our MEP Transactional API, during which some transactional messages may not have been sent, and some in-app messages on CEP may not have been displayed. Both are now fully resolved and operating normally again, and transactional requests from this window can be safely retried. Separately, our CEP profile processing pipeline saw a renewed delay this evening and is still catching up to real time, with no profile data lost. We will continue to monitor closely and share a further update within the next hour. Jul <var data-var='date'> 7</var>, <var data-var='time'>16:32</var> UTC Update - Recovery is nearly complete on our CEP profile processing pipeline, with real-time processing restored for the large majority of profile updates. We expect the remaining delay to fully clear during this evening. As a precaution, we have put in place reinforced monitoring and on-call coverage overnight to quickly detect and address any recurrence. We will share a further update tomorrow morning. Jul <var data-var='date'> 7</var>, <var data-var='time'>15:21</var> UTC Update - Recovery is underway on our CEP profile processing pipeline. Real-time processing has been restored for approximately 99% of profile updates, and the remaining share is still catching up. During this time, a small portion of attribute updates may still be delayed in one-time & recurring campaign targeting, automations triggered by attribute changes, and profile analytics. No data has been lost, and all delayed updates will be processed as the backlog clears. Jul <var data-var='date'> 7</var>, <var data-var='time'>10:05</var> UTC Monitoring - We are seeing recovery on our CEP profile processing pipeline. Real-time processing has already been restored for the majority of profile updates, while a subset is still catching up, so some attribute updates may remain delayed a bit longer in one-time & recurring campaign targeting, automations triggered by attribute changes, and profile analytics. No data has been lost, and all delayed updates will be processed as the backlog clears. We are continuing to monitor closely until processing is fully back to real time. Jul <var data-var='date'> 7</var>, <var data-var='time'>08:35</var> UTC Investigating - Since approximately 04:40 CEST, our CEP profile processing pipeline has been delayed, with profile updates currently around 5 hours behind real time. As a result, some profile attribute updates may not yet be reflected in one-time & recurring campaign targeting, automations triggered by attribute changes, and profile analytics. Campaign audience selection and most event-based automations are not affected. We are actively investigating the issue; no data has been lost, and delayed updates will be processed as the backlog clears.

Profile update processing delays on CEP

Jul <var data-var='date'> 1</var>, <var data-var='time'>07:56</var> UTC Resolved - This incident is now resolved. Jul <var data-var='date'> 1</var>, <var data-var='time'>07:34</var> UTC Monitoring - The issue has been resolved and the backlog has been fully processed. Jul <var data-var='date'> 1</var>, <var data-var='time'>07:31</var> UTC Identified - 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.

Delays in CEP trigger automations

Jun <var data-var='date'>23</var>, <var data-var='time'>10:30</var> UTC 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.

In-App message serving delays (≥ SDK 3.1)

Jun <var data-var='date'>19</var>, <var data-var='time'>12:05</var> UTC Resolved - 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. Jun <var data-var='date'>19</var>, <var data-var='time'>11:18</var> UTC Update - 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. Jun <var data-var='date'>19</var>, <var data-var='time'>10:26</var> UTC Identified - 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. Jun <var data-var='date'>19</var>, <var data-var='time'>09:51</var> UTC Investigating - 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 updates and orchestration impact on CEP

May <var data-var='date'>18</var>, <var data-var='time'>23:00</var> UTC Resolved - 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.

Missed executions for CEP recurring automations

May <var data-var='date'>13</var>, <var data-var='time'>18:16</var> UTC Resolved - 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. May <var data-var='date'>13</var>, <var data-var='time'>17:03</var> UTC Monitoring - 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. May <var data-var='date'>13</var>, <var data-var='time'>16:40</var> UTC Identified - 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. May <var data-var='date'>13</var>, <var data-var='time'>16:08</var> UTC Investigating - 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.

Transactional API push delivery issues

May <var data-var='date'> 8</var>, <var data-var='time'>03:00</var> UTC Resolved - Between May 8 at 05:00 CEST and 11:15 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 11:30 CEST.

May <var data-var='date'> 7</var>, <var data-var='time'>12:45</var> UTC Resolved - 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. May <var data-var='date'> 7</var>, <var data-var='time'>10:37</var> UTC Monitoring - Our profile data indexation pipeline experienced instability starting at May 7, 02:00 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.

Delays in CEP profile data indexation

May <var data-var='date'> 3</var>, <var data-var='time'>22:30</var> UTC Resolved - 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.

Web SDK Degraded Serving

Apr <var data-var='date'>22</var>, <var data-var='time'>08:46</var> UTC Resolved - 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. Apr <var data-var='date'>22</var>, <var data-var='time'>08:36</var> UTC Monitoring - 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. Apr <var data-var='date'>22</var>, <var data-var='time'>08:16</var> UTC Identified - 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.

Apr <var data-var='date'>21</var>, <var data-var='time'>14:04</var> UTC Resolved - This incident has been resolved. Between 15:28 CEST and 15:57 CEST, our email composer provider experienced degraded performance on their infrastructure, which impacted plugin initialization in the email editor. A fix was deployed on the provider side and service is back to normal. Apr <var data-var='date'>21</var>, <var data-var='time'>13:35</var> UTC Identified - Since April 21 at 15:28 CEST, the Email Composer is unavailable due to an incident on our third-party provider's side (Stripo). Users are unable to access or edit email messages in the composer at this time. The issue has been escalated to Stripo, and we are actively monitoring their progress toward a fix. We will share further updates as soon as more information becomes available.

Mar <var data-var='date'>23</var>, <var data-var='time'>10:29</var> UTC Resolved - This incident has been resolved. The exports have been back up since 09:45 CET, pending requests are still being processed. Mar <var data-var='date'>23</var>, <var data-var='time'>00:15</var> UTC Monitoring - 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. Mar <var data-var='date'>22</var>, <var data-var='time'>23:42</var> UTC Identified - 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. Mar <var data-var='date'>22</var>, <var data-var='time'>22:31</var> UTC Investigating - 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.

MEP Campaign Sending Delays

Mar <var data-var='date'> 4</var>, <var data-var='time'>07:35</var> UTC Resolved - The service has been restored and has been under monitoring for 48 hours with no regressions observed. Feb <var data-var='date'>28</var>, <var data-var='time'>15:31</var> UTC Monitoring - 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. Feb <var data-var='date'>28</var>, <var data-var='time'>15:02</var> UTC Identified - 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.

Delays in CEP campaign processing

Feb <var data-var='date'>21</var>, <var data-var='time'>23:17</var> UTC Resolved - This incident has been resolved. Feb <var data-var='date'>21</var>, <var data-var='time'>21:19</var> UTC Monitoring - 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. Feb <var data-var='date'>21</var>, <var data-var='time'>20:16</var> UTC Identified - 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. Feb <var data-var='date'>21</var>, <var data-var='time'>19:43</var> UTC Investigating - 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.

Processing Delays for Mobile Profile Updates

Feb <var data-var='date'>19</var>, <var data-var='time'>09:51</var> UTC Resolved - This incident has been resolved. Feb <var data-var='date'>19</var>, <var data-var='time'>09:38</var> UTC Monitoring - A fix has been implemented and we are monitoring the results. Feb <var data-var='date'>19</var>, <var data-var='time'>09:30</var> UTC Investigating - 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.

Email Composer - Image Upload Issue

Feb <var data-var='date'>17</var>, <var data-var='time'>12:33</var> UTC Resolved - Trigger automations on webpush SDK are live since 13:00 CET. The incident is now resolved. Feb <var data-var='date'>17</var>, <var data-var='time'>11:38</var> UTC Update - Trigger automations based on mobile SDK events are now live. The ones based on webpush SDK events are currently delayed by 1:30h. We're continuing to monitor the situation and expect a full resolution by 14:00 CET Feb <var data-var='date'>17</var>, <var data-var='time'>10:07</var> UTC Monitoring - CEP campaigns (one-shot and recurring automations) are back to normal. The backlog was fully processed at 11:00 CET, and campaigns sent as of now work as expected. Trigger automations based on mobile & web SDK events are processing but remain delayed by ~2 hours. No data has been lost, messages will be sent to the expected users as the backlog clears. Feb <var data-var='date'>17</var>, <var data-var='time'>09:06</var> UTC Update - We are still investigating the problem. CEP campaigns are still slowly being sent and approximately 2 hours behind schedule. Some trigger automations coming from SDK (mobile & web) events are delayed by 1:30 hours. No data has been lost, messages will be sent to the expected users as the backlog clears. We will provide a status update at 11:00 CET. Feb <var data-var='date'>17</var>, <var data-var='time'>08:02</var> UTC Update - We are still investigating the problem. CEP campaigns are slowly being sent but still approximately 3 hours behind schedule. Some trigger automations are delayed by 30 minutes. No data has been lost, messages will be sent to the expected users as the backlog clears. We will provide a status update at 10:00 CET. Feb <var data-var='date'>17</var>, <var data-var='time'>07:14</var> UTC Investigating - We are investigating delays affecting CEP campaigns (one shot & recurring). As of writing, processing is approximately 3 hours behind schedule. In-app messages and automations are not affected. Campaigns will be sent to the expected users as the backlog clears.

Feb <var data-var='date'>11</var>, <var data-var='time'>07:40</var> UTC Resolved - The backlog has been processed, the trigger automations are now live. Feb <var data-var='date'>11</var>, <var data-var='time'>07:00</var> UTC Monitoring - 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.

Jan <var data-var='date'>15</var>, <var data-var='time'>17:00</var> UTC 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.

CEP Trigger automation delays

Jan <var data-var='date'>14</var>, <var data-var='time'>20:30</var> UTC Resolved - Summary: Between 14 January at 21:30 CET and 15 January at 09:15 CET, a small subset of CEP trigger automations was delayed for up to 11 hours. This subset accounted for less than 2% of all CEP trigger automations. Impact for the affected trigger automations: * Event processing was delayed by up to 11 hours. * As a consequence, the delivery of emails, SMS, and push notifications was delayed by up to 11 hours. Root Cause: one instance of our event processing pipeline was unable to process certain events due to an edge case in their data, which slowed down the processing speed for that specific instance. Resolution: a mitigation was applied on 15 January at 08:36 CET, which restored normal processing performance. By 09:10 CET, the backlog was cleared and processing returned to real-time.

Jan <var data-var='date'> 7</var>, <var data-var='time'>07:54</var> UTC Resolved - Trigger automations ran late between 07:00 and 08:40 CET. All messages were delivered; none were lost.

Is Batch down?

Batch status is UP

Lastest published events

CEP Push Delivery Issue (FCM)

Email Composer – Service Unavailable

Android push (FCM) delivery outage on CEP

Batch Services, Components and Regions

Recent Batch events

CEP Push Delivery Issue (FCM)

Email Composer – Service Unavailable

Android push (FCM) delivery outage on CEP

CEP Push Delivery Issue (FCM)

Processing delays on CEP Exports & Cloud Sync

Profile update processing delays on CEP