Branch kesinti geçmişi

1. 21 Ağustos 2026 00:47 UTCmonitoring

   19 Ağustos 2026, 10:40 AM PST ve 20 Ağustos 20, 2026, 4:55 PM PST, yüklemeler, Yeniden yüklemeler ve Kullanıcı Yaşam döngüsü Etkinlikleri için gönderilen bir dağıtım çatışmasına neden oldu. Ad Partners en yüksek etkiyi gördü; Data Partners ve Dashboard webhook aboneleri de tekrarlar almış olabilir. Sorun tespit edildi ve düzeltildi. Etkisi: Sonunda olayları zorlayan kişiler etkilenmedi. Bu pencere sırasında etkilenen olay türleri için tekrarlanan geri dönüşler almış olabilir ve bu olay id'i deşifre edebilir. Hiçbir müşteri verileri kaybedilmedi.

Resmî olay güncellemesinden otomatik olarak çevrilmiştir.

1. 9 Temmuz 2026 18:09 UTCinvestigating

   Uygulamanın belirli cihaz klipleri altında başlatabileceği bazı uygulamaları etkileyen bir sorunu aktif olarak araştırıyoruz.

2. 9 Temmuz 2026 22:26 UTCmonitoring

   Altta yatan sorunları tespit ettik ve iOS SDK v3.14.2'yi yayınladık, bu da kaza-on-kullanıcının belirli cihaz klibi altında v3.14.1 kullanarak bazı uygulamaları etkilemesini sağladı. iOS SDK 3.14.1 kullanıyorsanız, herhangi bir sorundan kaçınmak için 3.14.2'ye güncellemeyi öneriyoruz.

3. 10 Temmuz 2026 00:14 UTCresolved

   Müşterilerimizi iOS SDK versiyonumuzda kullanarak etkileyen sorunu tespit ettik ve çözdük 3.14.14.1 Ne oldu: Belirli bir uygulama başlatılmış senaryolarda, bir kullanıcının kliplerine kopyalanmış beklenmedik bir veri olsaydı, YerliLink bunu yanlış yorumlayabilirdi, potansiyel olarak uygulamanın kazaya neden oldu. Kim Etkilendi: Bu konu sadece iOS SDK versiyonu üzerinde inşa edilen YerliLink kullanan uygulamaları etkiler 3.14.14.1. Uygulamanız YerliLink kullanmıyorsa, bu konu tarafından etkilenmediniz. Nasıl düzeltilir: Bu iOS SDK sürüm 3.14.2'de tamamen çözülmüştür. Uygulamanız YerliLink kullanıyorsa, düzeltmeyi almak için bu son sürüme mühendislik ekibiniz güncellemeniz gerekir. Immediate Work around (No App Update Required): Hemen bir uygulama güncellemesini zorlayamazsanız, tavanınızda Yerli Linkleri bozmak için hemen çöküntüleri durdurabilirsiniz.

Resmî olay güncellemesinden otomatik olarak çevrilmiştir.

1. 2 Temmuz 2026 23:47 UTCinvestigating

   Adım işleme ve webhooksda bir gecikme tespit ettik. İşleme doğru çalışır, ancak şu anda yaklaşık bir saat gecikir. Mühendislik ekibi alt yatan nedeni araştırıyor.

2. 3 Temmuz 2026 02:28 UTCmonitoring

   7:10 PT olarak artık 30 dakika içinde webhooks işlemeyiz. Durumu takip ediyoruz ve bir kök nedeni için araştırmaya devam ediyoruz.

3. 3 Temmuz 2026 10:59 UTCmonitoring

   7:10 PT olarak artık 30 dakika içinde webhooks işlemekteyiz ve ayırıcı işleme ile gecikmeleri görmüyoruz. Durumu takip ediyoruz ve bir kök nedeni için araştırmaya devam ediyoruz.

4. 3 Temmuz 2026 16:27 UTCinvestigating

   Şu anda hizmetlerimizi etkileyen yaklaşık 7:30 PT'de başlayan bir sorunu araştırıyoruz. Webhook işleme şu anda 30 dakikalık SLA'mızı aşıyor. Ayrıca, API'lerimiz içindeki veri ihracat ve veri kullanılabilirliği dört saate kadar gecikmektedir. Kök nedenini tanımlamak için aktif olarak çalışıyoruz ve daha fazla bilgi mevcut olacak şekilde daha fazla güncelleme sağlayacaktır.

5. 3 Temmuz 2026 23:56 UTCmonitoring

   Bu zamanda kök nedenini tespit ettiğimize ve ele aldığımıza inanıyoruz ve tüm sistemler normale geri döndü. Webhooks ve veri kullanılabilirliği SLA ve normal sınırlar içindedir. Hafta sonu boyunca İzlemede kalacağız.

6. 8 Temmuz 2026 18:45 UTCresolved

   Bu olay çözüldü.

Resmî olay güncellemesinden otomatik olarak çevrilmiştir.

1. 26 Mart 2026 03:45 UTCmonitoring

   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.

2. 26 Mart 2026 15:19 UTCmonitoring

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

3. 26 Mart 2026 15:42 UTCresolved

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

1. 13 Mart 2026 06:59 UTCinvestigating

   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.

2. 13 Mart 2026 09:10 UTCresolved

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

1. 5 Mart 2026 16:34 UTCmonitoring

   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.

2. 5 Mart 2026 18:09 UTCmonitoring

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

3. 5 Mart 2026 19:20 UTCresolved

   Latency has now returned to normal.

1. 20 Şubat 2026 01:22 UTCresolved

   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.

1. 27 Kasım 2025 16:56 UTCinvestigating

   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.

2. 27 Kasım 2025 17:44 UTCresolved

   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.

1. 8 Eylül 2025 23:04 UTCidentified

   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.

2. 9 Eylül 2025 01:14 UTCresolved

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

1. 3 Eylül 2025 22:44 UTCinvestigating

   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.

2. 4 Eylül 2025 23:28 UTCresolved

   We are once again seeing successful requests

1. 14 Ağustos 2025 17:37 UTCmonitoring

   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

2. 14 Ağustos 2025 19:13 UTCresolved

   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

1. 8 Ağustos 2025 22:38 UTCresolved

   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.

1. 7 Ağustos 2025 03:44 UTCinvestigating

   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.

2. 7 Ağustos 2025 05:21 UTCresolved

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

1. 24 Nisan 2025 16:41 UTCinvestigating

   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.

2. 24 Nisan 2025 17:36 UTCidentified

   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.

3. 24 Nisan 2025 22:29 UTCresolved

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

1. 21 Mart 2025 19:16 UTCinvestigating

   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.

2. 21 Mart 2025 21:54 UTCidentified

   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.

3. 22 Mart 2025 03:27 UTCmonitoring

   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.

4. 24 Mart 2025 16:50 UTCresolved

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

1. 18 Mart 2025 10:37 UTCinvestigating

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

2. 18 Mart 2025 16:05 UTCresolved

   Cohort Analytics service is now up and working

1. 15 Mart 2025 06:08 UTCinvestigating

   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.

2. 15 Mart 2025 14:38 UTCidentified

   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.

3. 16 Mart 2025 03:30 UTCresolved

   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.

1. 11 Aralık 2024 18:45 UTCmonitoring

   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.

2. 11 Aralık 2024 20:45 UTCresolved

   We now see a full recovery of the Facebook API. We will continue to monitor but all systems have returned to normal.

1. 20 Eylül 2024 09:56 UTCinvestigating

   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.

2. 20 Eylül 2024 10:43 UTCresolved

   Dashboard services have stabilized and returned to normal.

1. 27 Ağustos 2024 03:33 UTCinvestigating

   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.

2. 29 Ağustos 2024 04:50 UTCmonitoring

   We have collaborated with Google, who have identified the root cause and applied a fix. We are monitoring the situation.

3. 29 Ağustos 2024 16:57 UTCresolved

   As of 9:00 am PST (16:00 UTC), we have confirmed the fix applied by Google has normalised the event attributions.