Is Branch down?

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.

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.

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.

We are currently carrying out brief maintenance on our system. During this time, delivery for some webhooks may be temporarily delayed. Impact: Webhook notifications are queued and delayed. No data will be lost, and all events will process automatically. Estimated Resolution: Within the next 10–15 minutes. We apologize for the inconvenience and will post an update as soon as normal processing resumes.

Maintenance is now complete, and all webhook services are back to normal. We are currently processing the backlog of queued webhooks, and all delayed notifications will be delivered shortly. Thank you for your patience.

Between August 19, 2026, 10:40 AM PST and August 20, 2026, 4:55 PM PST, a deployment conflict caused duplicate webhook events to be sent for Installs, Reinstalls, and User Lifecycle Events. Ad Partners saw the highest impact; Data Partners and Dashboard webhook subscribers may also have received duplicates. The issue has been identified and fixed. Impact: Partners who deduplicate events on their end were not affected. Partners who do not deduplicate may have received duplicate postbacks for the affected event types during this window and can deduplicate given event_id. No customer data was lost.

This incident has been resolved.

We are actively investigating an issue affecting some apps using Branch iOS SDK 3.14.1 where the app may crash on launch under specific device clipboard conditions.

We've identified the underlying issues and have released Branch iOS SDK v3.14.2, which includes a fix for the crash-on-launch issue impacting some apps using v3.14.1 under specific device clipboard conditions.If you are using Branch iOS SDK 3.14.1, we recommend updating to 3.1.4.2 to avoid any issues.

We have identified and resolved the issue affecting customers using NativeLink in our iOS SDK version 3.14.1 What Happened: In certain app launch scenarios, if a user had unexpected data copied to their clipboard, NativeLink could misinterpret it, potentially causing the app to crash. Who Was Impacted: This issue only impacted apps using NativeLink that were built on iOS SDK version 3.14.1. If your app does not use NativeLink, you were not impacted by this issue. How to Fix It: This has been fully resolved in iOS SDK version 3.14.2. If your app uses NativeLink, please have your engineering team update to this latest version to receive the fix. The Immediate Workaround (No App Update Required): If you cannot push an app update immediately, you can stop the crashes right away by disabling NativeLink in your dashboard.

We have identified a delay in attribution processing and webhooks. Processing is functioning correctly but currently delayed by approximately one hour. The Engineering team is investigating the underlying cause.

As of 7:10 PT we are now processing webhooks within 30 minutes. We are monitoring the situation and continue to investigate for a root cause.

As of 7:10 PT we are now processing webhooks within 30 minutes and we do not see delays with our attribution processing. We are monitoring the situation and continue to investigate for a root cause.

We are currently investigating an issue that began at approximately 7:30 PT, which is impacting our services. Webhook processing is currently exceeding our 30-minute SLA. Furthermore, data exports and data availability within our APIs are experiencing delays of up to four hours. We are actively working to identify the root cause and will provide further updates as more information becomes available.

At this time we believe that we have identified and addressed the root cause and all systems are back to normal. Webhooks and data availability are within SLA and normal bounds. We will remain in Monitoring through the weekend.

This incident has been resolved.