Batch had 44 outages in the last 2 years totaling 585h 49m of downtime — averaging 1.8 incidents per month.
There were 44 Batch outages since March 24, 2025 totaling 585h 49m of downtime. Each is summarised below — incident details, duration, and resolution information.
On July 22 from 15:34 to 16:04 CEST, the Dashboard and some APIs experienced temporary disruptions due to unexpected effects during a planned network maintenance. Impacted components included the Dashboard, Data ingestion, Trigger Events API, Transactionnal API, Profile API, and Custom Audience API. The issue has been resolved and all systems are now operating normally.
Between 18:05 and 19:08 GMT+2, our Trigger Automations component experienced an issue that prevented new trigger events from being processed in real-time. This resulted in delayed communications, including emails, push notifications, and SMS, for up to one hour. Our engineering team identified and resolved the underlying issue, restoring normal operations by 19:06 GMT+2. A backlog of delayed events was fully processed by 19:08 GMT+2. All systems are now operating normally. We sincerely apologize for any disruption this may have caused.
We are currently investigating this issue.
We are continuing to investigate this issue.
We are currently investigating a network issue that is affecting access to the main dashboard. Our engineering team is actively working to identify the root cause and restore normal service as quickly as possible.
We are continuing to investigate this issue.
Dashboard is back online, we are still investigating.
This incident has been resolved.
We have identified an issue affecting Date attributes on Profiles when updated via our SDKs (v2.x and v3.x). Between July 2nd, 15:36 CET and July 3rd, 15:25 CET, any Date attribute set using the SDK was assigned an incorrect value far in the future. Impact As a result of this issue: * Targeting based on these attributes will not behave as expected. * Profiles will not appear correctly in the Dashboard’s Profile View. * Data exports will reflect incorrect dates for affected attributes. What is Not Affected * Attributes updated outside the impacted time window have the correct value. * Attributes updated via the Profile API or Custom Data API are not impacted. * The MEP (Mobile Engagement Platform) remains unaffected. Current status Our engineering team is actively working on restoring the correct values for all impacted Profiles. As it is a lengthy process, we expect this work to be completed in the next 24h.
The data has been restored: * Targetings using those attributes will now work as expected * The attributes now show up in the Profile View * Future exports will show the correct data We will not replay automations & campaigns to profiles that should have been targeted but were not. Future occurrences will work as expected.
We're currently experiencing intermittent errors with our image loading system. The impact is two fold: * some campaigns cannot be created correctly due to image loading failures, affecting both the main dashboard and the editorial dashboards. * some transactional push notifications containing images cannot be sent correctly due to image loading failures. This issue started on June 20th at 17:00 CET. Our team is actively investigating the issue and working to restore full functionality as quickly as possible. We apologize for any inconvenience this may cause.
We're still observing intermittent image loading errors, though at a significantly reduced rate compared to the last 24 hours. The last reported error occurred at 15:00 CET. Our team continues to actively work on implementing a permanent fix.
A fix has been implemented. We haven't observed any new issues for the past two hours and will continue to monitor the situation closely.
This incident has been resolved.
Between June 9th and 13th, we encountered issues with SMS delivery, which resulted in a significant discrepancy between the estimated reach and the actual number of delivered SMS in the analytics. Please note that these SMS were not billed, and the issue has since been resolved. We have reached out to the affected clients regarding this issue.
Between June 9th 16:30 GMT+2 and June 10th 12:50 GMT+2, a database issue caused partial service disruptions affecting specific API endpoints and our analytics data processing pipeline. Impact: - Transactional API: Intermittent 500 internal server errors were returned by get stats endpoint. - Export API: Exports requests took multiple hours to be processed. - Dashboard: Analytics data production was delayed, causing outdated information to be displayed on the dashboard. The engineering team identified the root cause of the instability and deployed a correction. Service functionality was restored and confirmed stable at 12:50 GMT+2, queued exports finished processing around 15:50 GMT+2
Between June 10th 17h (French Time) and June 11th 17h, intermittent 500 errors occurred on create and update API calls that included attributes, affecting approximately 1% of total API traffic during this period.
This morning, we identified an issue affecting imported push tokens in Push v2, which may have led to duplicate notifications being sent. As a precaution, we have temporarily disabled creating campaigns with imported tokens while we investigate the root cause and work on a fix. Push v1 remains fully operational and is not impacted by this issue.
We have resolved the issue. We fixed the incorrect data and have now reactivated the imported token based campaigns
We are currently experiencing slowness on our dashboard. Our teams are investigating the cause of this issue. We will keep you updated on the situation.
The performance issues previously affecting the dashboard have been resolved. A fix has been applied, resulting in a much faster experience for all users. We will continue to monitor the situation to ensure everything remains stable.
Situation is back to normal
Between April 24th, 2025 at 20:30 UTC and May 2nd, 2025 at 08:00 UTC, some users experienced network instabilities across our services. The issue was traced to a faulty load balancer in our infrastructure, which caused intermittent disruptions and impacted service stability during that period. The defective component has since been replaced, and systems have returned to normal operation. All services are now stable and functioning as expected. As a result of this incident, anomaly detection tools have been enhanced to better detect network-related issues at the edge of our infrastructure. These improvements are designed to enable more proactive identification and resolution of potential problems, further reinforcing the reliability of our services.
Since Friday, April 18th, we have been experiencing delays in loading native attributes for targeting our MEP campaigns. The incident has been identified, and initial fixes are being applied. We will provide further updates as soon as possible.
A fix has been implemented and we are monitoring the results.
The issue has been identified and a fix is being implemented.
Despite initial fixes being applied, we are still experiencing issues, and the situation remains under investigation. We will continue to keep you informed and provide further updates as soon as possible.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
Our Customer Engagement Platform is experiencing delays for some Push, SMS & Email automations. About 1.5% of the messages are delayed for at most 10 hours. We have identified the cause and are working on a fix. No messages have been lost: once the fix is deployed, the delayed messages will be sent.
The fix has been deployed and the system is catching up. The delayed messages should all be sent around 10:00 GMT+2.
This incident has been resolved.
Our Mobile Engagement Platform experienced processing delays for some triggered push notifications between April 10th, 10:40 PM and April 11th, 10:05 AM. All messages were successfully processed, and none were lost.
Our Customer Engagement Platform experienced processing delays for some triggered push notifications between April 5th, 3:30 PM and April 6th, 8:30 PM. All messages were successfully processed, and none were lost.
We experienced an issue affecting our GDPR API, resulting in the later being unavailable for a while. A fix was implemented at 5:00 A.M. UTC (6:00 A.M. CET) and we didn't notice any new occurrence of this issue since then.
We’re currently experiencing connectivity issues affecting the Dashboard. Our team is investigating and working to restore full access as soon as possible.
The issue has been identified and a fix is being implemented.
We are continuing to work on a fix for this issue.
A mitigation has been implemented and is functioning as expected. We are continuing to closely monitor the system and address any remaining issues.
There are no changes at this time. The mitigation remains effective, the impacted components are stable, and we are continuing to monitor the situation closely.
A permanent fix has been implemented, and the affected components remain stable. The incident will remain open as we continue to closely monitor the situation for the next 24 hours.
Monitoring has confirmed that the issue is fully resolved and all systems are operating normally. This incident is now closed.
We’re currently experiencing an issue affecting our Audience API. Our engineering team is actively investigating and working to resolve it as quickly as possible.
A fix has been implemented and we are monitoring the results.
The issue has been fully resolved — a permanent fix was implemented at 21:00 UTC, and we've continued monitoring throughout the night to ensure stability.