Branch outage history

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.

We are now seeing successful completion of the previously delayed jobs and all current exports are processing without any delays.

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.14.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.

We have identified a disruption in X's API Service Status (https://docs.x.com/status) causing delays to X attributions. Once X's services are restored, attribution and webhooks will be funnelled and properly processed. Our team is monitoring the situation.

We are continuing to monitor the situation. Branch's API and Webhook services were not impacted and they continue to be fully operational

We have confirmed that X’s API Service success rates have returned to normal. We will continue to monitor.

Our Engineering team is currently working to resolve an issue where some customers are reporting missing features from their dashboard. We appreciate your patience as we work to restore full functionality as quickly as possible.

The identified issue has been resolved, and services are now restored. You should see the dashboard features available again.

We are currently observing severe latency with the Meta Graph API. This is resulting in a temporary loss of real-time reporting data. We have alerted Meta and are monitoring the situation closely and will provide updates as they become available.

We are seeing a decrease in the latency and will continue to monitor.

Latency has now returned to normal.

Between 3:00 PM and 3:25 PM PST, we experienced a period of service instability that affected Deeplinking and App opens. During this window users may have encountered errors or slower response times. Our team identified this was the result of configuration error during a routine system update. We immediately reverted the change and all services returned to normal operation by 3:25 PM PST. We are currently monitoring our systems and verifying that all delayed data has been processed correctly.

We have identified an issue with Daily Exports API service failing. Customers may encounter delay or even errors while trying to pull the data. Out team is actively working to resolve the issue.

We have identified the issue, deployed a fix, and restarted the affected jobs. We are now seeing successful completion of jobs and these will be processed in the next few hours.

We have identified an issue with Google Ads iOS attribution pipeline impacting partial attribution data beginning July 23rd. We are working to resolve the issue and assess impact.

Our team has now pushed a fix to resolve the issue. We are assessing impact and will follow up with more details.

We have identified an increase in error responses for Universal Email Campaign links for clients integrated Sendgrid services, this potentially includes those using Sendgrid, Braze + Sendgrid, Klayvio and other ESPs utilizing sendgrid API. End users should be resolving to the fallback URL in cases where we receive an error from Sendgrid endpoints. We have reported this issue to Sendgrid and will continue to work with them to a resolution.

We are once again seeing successful requests

We are aware of global issues with Facebook Ad Partner authentication tokens. Branch is monitoring Meta's status page (https://metastatus.com/facebook-login), currently reporting issues with their Facebook login. Once Meta's services are restored, Branch will try to automatically reconnect . If your authentication token remains invalid, manually re-authenticate your account within the Branch platform here: https://branch.dashboard.branch.io/ads/partner-management

Meta has resolved the issues affecting Facebook login, as confirmed on their status page (https://metastatus.com/facebook-login). Branch attempted to re-establish connections for all accounts, and most were successful. If your Facebook Ad Partner authentication token remains invalid, please manually re-authenticate your account within the Branch platform here: https://dashboard.branch.io/ads/partner-management/a_facebook?tab=settings

We have identified an issue impacting post install event SKAN attributions. As a result SKAN attributions may have been missed for conversion events starting July 31st. The root cause was addressed and resolved as of August 7th at 5:12 PM PDT. We will continue monitoring.

At 8:20 PM Pacific Time, we identified an issue with not being able to create or clone Journeys. Our Engineering teams are investigating the issue.

As of 08:36 PM Pacific Time, we have restored the Journey services. You should now be able to create and clone Journeys successfully.

We're encountering service degradation with a few our services impacting link performance. API may return an error, however link redirects will continue to work and open the app or web as expected. Our Engineering team is actively working to resolve the issue and restore full functionality. We’ll provide updates as we have more information.

Root cause has been identified and we are currently applying the fixes. In the meantime API Success Rate and latency are back to normal levels and direct deep linking functionality has been restored. We are continually working to restore other impacted functionalities including deferred deep linking.

As of 1:04PM PST we have recovered 100% of the functionality and are reporting success rates and latency are back to normal.

Our engineering team has identified a significant increase in error responses from the Google Ads API. As a result we are seeing a delay in populating the cost, click and impression data within the dashboard. We are actively working with Google's team to resolve. No data loss is expected.

We are continuing to troubleshoot the issue with google, we expect a temporary delay in cost, click and impression data for Google ads until api issues are fully resolved. Once again, no data loss is expected.

Errors have subsided and the backlog has been cleared. We will continue to monitor the API services. In the meantime data is up-to-date.

The issue has been resolved. All data has been backfilled.

We are currently investigating an issue with Cohort Analytics being unavailable. You will see a message "No analytics found". Our teams are currently investigating.

Cohort Analytics service is now up and working

Our engineering team has identified a high latency in responses from Facebook SAN API resulting in a delay to the attribution pipeline. We have reached out to Facebook and are currently investigating.

Our engineering team has identified high latency response times from the Facebook SAN API, which is impacting attribution accuracy and reporting within our platform. The increased response time is leading to lower-than-expected attributions to Facebook and potential misattributions to other channels due to delayed postbacks from FB. Due to high latency, we have also disabled SAN Deferred Deep Linking, which will impact deep linking and attribution for events relying on SAN calls.

Meta has resolved disruptions to their attribution claim pipelines as of Saturday March 15th 04:10 PM Pacific Time. These disruptions caused delays in claims received from Meta, resulting in attribution loss and potential misattributions. We have resumed our attribution pipelines back to normal. Latency previously observed has subsided, however we will continue to monitor our services.