Batch experienced a minor incident on February 17, 2026, lasting 5h 19m. The incident has been resolved; the full update timeline is below.
Update timeline
- resolved Feb 17, 2026, 12:33 PM UTC
Feb 17, 12:33 UTC Resolved - Trigger automations on webpush SDK are live since 13:00 CET. The incident is now resolved. Feb 17, 11:38 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 17, 10:07 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 17, 09:06 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 17, 08:02 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 17, 07:14 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.