Is Branch Down?

This incident is resolved. mParticle event traffic is flowing normally, and the data dropped earlier today has been fully replayed. No data loss is expected. We apologize for the disruption and any delay in your data. If you notice any gaps in your mParticle event data, please contact Support. --- [2026-11-05T14:00:07.086-08:00] (monitoring) Service has recovered, and mParticle event traffic is flowing normally again. Events dropped earlier today (starting around 9:40 AM PT) are being replayed, we don't expect data loss. Replayed data may appear in your dashboards and downstream integrations with a delay while the replay completes. --- [2026-11-05T13:52:38.980-08:00] (monitoring) Starting around 9:40 AM PT, a failure in part of our event ingestion infrastructure caused event traffic sent from mParticle to Branch to be dropped. We've added capacity and service is recovering. Our engineers are monitoring to confirm it holds. Impact: Events sent to Branch via mParticle between roughly 9:40 AM PT and recovery were not received, We're still determining the exact volume of affected events.

We are now seeing successful completion of the previously delayed jobs and all current exports are processing without any delays. --- [2026-10-26T02:32:50.261-07:00] (identified) We are currently investigating an issue with the processing of Custom Exports API jobs generated between 05:14 UTC and 08:45 UTC. Please note that processing resumed at 08:45 UTC, and all affected export jobs are being reprocessed automatically but currently delayed due to the accumulated backlog. We are actively working through the backlog and to identify the root cause and will provide further updates as more information becomes available.

This has now been resolved. Earlier, an AWS service outage caused a service disruption to attribution processing, affecting V1/V2 event delivery. Impact: V1/V2 events sent between2:56 PM PT to 3:38 PM PT were not received. Service has been fully restored and events are once again processing normally. --- [2026-09-03T15:51:23.082-07:00] (monitoring) Services are beginning to recover, and events are once again being processed. We'll continue monitoring closely and share an update once full resolution is confirmed. --- [2026-09-03T15:33:15.787-07:00] (investigating) We're investigating a service disruption to attribution processing caused by an AWS service outage, resulting in a brief but significant drop in availability. Impact: Primarily impacting v1/v2 events, starting approximately 2:45–3:00 PM PT today. The issue was identified and responders are actively working it. We'll share an update as we learn more.