55 Branch incidents · 2023年1月 — official updates, affected components, duration and resolution details.
我们目前正在调查一个问题,处理在协调世界时05:14至协调世界时08:45之间产生的海关出口API工作。 请注意,协调世界时08:45恢复处理,所有受影响的出口工作正在自动重新处理,但目前由于积压而推迟。 我们正在积极努力解决积压问题并找出根源,并将在获得更多信息后提供进一步的最新资料.
我们现在看到,以前拖延的工作正在顺利完成,所有目前的出口都在毫无拖延地进行加工.
自动翻译自官方事件更新。
我们正在调查由于AWS服务中断导致的归属处理中断,导致可用性短暂但显著下降. 影响:主要影响v1/v2事件,从今天大约2:45-3:00PM PT起. 问题已经确定,答复者正在积极开展工作。 等我们学到更多知识后再分享最新消息.
服务开始恢复,事件再次得到处理。 我们将继续密切监视 并分享最新消息 一旦完全解析出来.
现在这个问题已经得到解决。 早些时候,AWS服务中断导致服务中断归属处理,影响V1/V2事件交付. 影响:2:56 PM PT至3:38 PM PT之间的V1/V2事件没有收到. 服务已完全恢复,事件再次得到正常处理.
自动翻译自官方事件更新。
我们目前正在对我们的系统进行简短的维护。 在此期间,一些网络用户的发送可能会被暂时推迟。 影响: Webhook 通知被排队并被延迟. 没有丢失数据,所有事件都会自动处理. 估计分辨率:10至15分钟内。 我们对此不便表示歉意,并将在恢复正常处理后立即发布最新情况.
维护工作现已完成,所有webhook服务恢复正常. 我们正在处理已排队的 Webhooks 的积压,所有延迟通知将很快送达。 谢谢你的耐心.
自动翻译自官方事件更新。
在2026年8月19日,10:40 AM PST到2026年8月20日:4:55 PM PST之间,一场部署冲突导致重复的webhook事件被发送到Installs,Reinstalls,以及用户生命周期事件. Ad Partners的影响力最大; Data Partners和 Dashboard webhook 的订阅者也可能收到重复. 这个问题已经确定和解决。 影响:在事件发生时发生故障的合作伙伴没有受到影响。 不重复的合作伙伴可能在本窗口中收到了受影响事件类型重复的回信并可以重复给定事件 id. 没有客户数据丢失.
这一事件已经得到解决.
自动翻译自官方事件更新。
我们正在积极调查一个影响一些应用的问题, 使用分支 iOS SDK 3.14.1 , 应用可能在特定设备剪贴板条件下崩溃.
我们已经查明了基本问题,并发布了Branch iOS SDK v3.14.2,其中包括在特定设备剪贴板条件下对一些应用用v3.14.1撞击的相撞启动问题进行修复. 如果你使用分支iOS SDK 3.14.1, 我们建议更新到 3.14.2 以避免任何问题.
我们在iOS SDK版本的3.14.1中找到并解决了影响客户的问题。 会发生什么:在某些应用启动情景中,如果用户有出乎意料的数据被复制到他们的剪贴板上,NublicLink可能会误解它,可能导致应用崩溃. 受冲击者: 这个问题只影响到了使用由iOS SDK版本3.14.1所构建的IndigenalLink的应用程序. 如果你的应用程序没有使用 NaturalLink, 你没有受到这个问题的影响 。 如何修复:这已经在iOS SDK版本 3.14.2中完全解决. 如果您的应用程序使用"NublicLink",请让您的工程团队更新到这个最新版本以接收修复. 即时工作轮廓( 不需更新应用程序) : 如果您无法立即推动应用程序更新, 您可以在您的仪表板上解除本地链接功能, 从而立即阻止崩溃 .
自动翻译自官方事件更新。
我们发现在归属处理和网络搜索方面存在延误。 处理工作正在正确进行,但目前拖延了大约一个小时。 工程组正在调查原因.
从7点10分起,我们正在30分钟内处理网络攻击。 我们正在监测局势并继续从根源出发进行调查.
截止到7:10 PT,我们现在正在30分钟内处理webhooks,我们并不看到我们的归属处理出现延误. 我们正在监测局势并继续从根源出发进行调查.
我们目前正在调查一个大约从7: 30 PT开始的问题,这个问题正在影响我们的服务。 Webhook 处理目前超过了我们的30分钟 SLA. 此外,我国API内部的数据输出和数据可用性受到长达四个小时的拖延。 我们正在积极努力查明根源,并将在获得更多信息后提供进一步的最新资料.
此时我们认为,我们已经查明并解决了根源,所有系统都恢复正常。 Webhoks和数据可用性属于苏丹解放军和正常范围。 我们将一直留在监测 整个周末.
这一事件已经得到解决.
自动翻译自官方事件更新。
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.
