Live  /  Branch  /  Incident

Branch: mParticle Event Delivery Disruption

Branch · branch.ioResolved2026-11-06 00:19 UTC
Public — what happened

Summary

Branch reported a disruption in which events sent from mParticle to Branch were not received, beginning around 9:40 AM PT on November 5. Branch said a failure in part of its event ingestion infrastructure caused the problem, and that it added capacity, after which traffic was flowing normally again by 22:00 UTC. The company said the dropped events are being replayed and it does not expect data loss, though replayed data may show up late in dashboards and connected integrations. The incident was marked resolved at 00:19 UTC on November 6, and Branch said it was still working out how many events were affected.

Timeline

Source of record: provider status page. Summary written by SquidGrid from the provider’s published updates; times in UTC.

Independent path health

The status page is the symptom. SquidGrid measures the paths that reach Branch against their own baselines — whether the routes carrying your traffic degraded, at which handoff, and who owns that stretch.

🔒 Sign in to see
Customers get the live Provider Assessment Report for Branch: its full incident track record, what tends to break, and recent public reports of problems.

Included with any paid plan.

Open the Branch report →

More from Branch

Covered in The Squid’s Ink, Week 46, 2026, our weekly internet health report.

The full archive is on the Branch status & history page.

Related: Branch status & history. SquidGrid is not affiliated with Branch.