Batch Outage History

Between September 14 and October 5, push sent and push open events from CEP campaigns were missing from the daily MEP event exports for some projects. Push delivery was not affected, and no data was lost. The issue was caused by a database migration, after which these events were stored in a location that was no longer read by the export process. A fix was deployed on October 5 at 14:30 CEST, and exports generated since October 6 are complete.

This incident has been resolved. On October 2, between approximately 15:00 and 16:30 CEST, the Dashboard was intermittently slow or unavailable for some users, due to a network issue between our hosting provider and some Internet access providers. The Dashboard is operating normally again, and no errors have been observed for over 40 minutes.

On September 23, CEP event ingestion was delayed during two separate periods. Between 07:00 and 09:06 CEST, less than 1% of events sent through our mobile SDKs were processed with delay. Between 10:00 and 11:00 CEST, the delay affected all CEP event ingestion, both API and SDK. Processing has returned to normal and the backlog is fully processed.

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.

This incident has been resolved.

This incident has been resolved.

This incident has been 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.

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.

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.

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.

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.

This incident has been resolved. The exports have been back up since 09:45 CET, pending requests are still being processed.

The service has been restored and has been under monitoring for 48 hours with no regressions observed.

This incident has been resolved.

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.