52 Branch incidents · 2023年1月 — official updates, affected components, duration and resolution details.
2026年8月19日、午前10時40分、午後2026年8月20日、午後4時55分、展開コンフリクションにより、インストール、再インストール、およびユーザーライフサイクルイベントの送信が行われた。 アド・パートナーズは、最も影響力が高まっています。データ・パートナーズとダッシュボードのWebhookの加入者も重複を受け取りました。 問題は特定され、修正されました。 影響: 終端の出来事を解読するパートナーは影響を受けませんでした。 重複しないパートナーは、このウィンドウの間に影響を受けるイベントタイプに重複した投稿を受け取り、与えられた event id を複製することができます。 顧客データが失われない.
公式のインシデント更新を自動翻訳しています。
特定のデバイスクリップボード条件下でアプリが起動時にクラッシュする可能性があるブランチiOS SDK 3.14.1 を使用して、一部のアプリに影響を及ぼす問題を積極的に調査しています.
基本的な問題を特定し、ブランチiOS SDK v3.14.2をリリースしました。これは、特定のデバイスクリップボード条件下でv3.14.1を使用していくつかのアプリに影響を与えるクラッシュオンランチャ問題の修正を含みます。 ブランチiOS SDK 3.14.1 を利用している場合は、問題を回避するために 3.14.2 に更新することをお勧めします.
IOS SDK バージョン 3.14.1 で、NativeLink を使用して顧客に影響を与える問題を特定、解決しました。 What Happened: 特定のアプリの起動シナリオでは、ユーザーが自分のクリップボードにコピーした予期しないデータを持っていた場合、NativeLinkはそれを誤解させる可能性があります。 誰が影響を受けたのか: この問題は、iOS SDK バージョン 3.14.1 で構築された NativeLink を使用したアプリにのみ影響します。 お使いのアプリがNativeLinkを利用していない場合は、この問題に影響を受けていない。 修正方法:iOS SDKバージョン3.14.2で完全に解決しました。 お使いのアプリがNativeLinkを使用している場合は、この最新バージョンにエンジニアリングチームの更新を行ってください。 即時の回避策(アプリの更新は必要ありません): すぐにアプリの更新をプッシュできない場合は、ダッシュボードでNativeLinkを無効にすることで、すぐにクラッシュを停止することができます.
公式のインシデント更新を自動翻訳しています。
アトリビューション処理とWebhooksの遅延を特定しました。 処理は正しく機能しますが、現在約1時間遅れます。 エンジニアリングチームは、根本的な原因を調査しています.
7:10 PT では、30分以内に Webhook を処理しています。 状況を監視し、根本原因の調査を続けていきます.
7:10 PT では Webhook を 30 分以内に処理し、アトリビューション処理の遅延は見られません。 状況を監視し、根本原因の調査を続けていきます.
現在、弊社サービスに影響を及ぼす、約7:30のPTで始まった問題について調査中です。 Webhook処理は、現在30分を超える SLA を上回っています。 また、API内のデータエクスポートやデータ可用性は、最大4時間までの遅延が発生しています。 根本的な原因を特定し、より多くの情報が利用可能になるように、さらなるアップデートを提供できるよう積極的に取り組んでいます.
今回は、根本原因を特定し、根本原因に対処し、全てのシステムが正常に戻っていると確信しています。 Webhooks およびデータ可用性は SLA および通常のバインド内にあります。 週末を通したまま監視します.
この事件は解決しました.
公式のインシデント更新を自動翻訳しています。
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.
Starting around 9:55 AM PST we identified an increased failure response for callouts made to the Facebook API. We are seeing this API start to recover and will continue to monitor.
We now see a full recovery of the Facebook API. We will continue to monitor but all systems have returned to normal.
We are observing an issue with our Dashboard Service. Users might see latency with the Dashboard loading or encounter a blank page while trying to access the Branch Dashboard. Our Engineering Teams are actively Investigating.
Dashboard services have stabilized and returned to normal.
Starting August 26th at around 9:00 am PST (16:00 UTC), we have identified drop in attributions from Google for iOS. Our internal teams are investigating the issue.
We have collaborated with Google, who have identified the root cause and applied a fix. We are monitoring the situation.
As of 9:00 am PST (16:00 UTC), we have confirmed the fix applied by Google has normalised the event attributions.