An AWS service outage caused a disruption to Branch's attribution processing, resulting in V1/V2 events sent between 2:56 PM and 3:38 PM PT on September 3, 2026 not being received. The incident lasted approximately 2 hours before services were fully restored and event processing returned to normal.
Trusted by 1,000+ teams
Stop finding out about outages from your users. Monitor 6,320+ cloud services and get alerted the second something breaks.
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.
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.
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.
With IsDown, you can monitor all your critical services' official status pages from one centralized dashboard and receive instant alerts the moment an outage is detected. Say goodbye to constantly checking multiple sites for updates and stay ahead of outages with IsDown.
Start free trialNo credit card required · Cancel anytime · 6320 services available
Integrations with