Histórico de interrupções do Branch

1. 21 Eost 2026 da 00:47 UTCmonitoring

   Entre 19 de agosto de 2026, 10:40 PST e 20 de agosto de 2026, 4:55 PST, um conflito de implantação causou eventos webhook duplicados a serem enviados para Installas, Reinstalações e Eventos de Ciclo de Vida do Usuário. Parceiros de anúncios tiveram o maior impacto; Parceiros de dados e assinantes do Dashboard webhook também podem ter recebido duplicatas. A questão foi identificada e corrigida. Impacto: Os parceiros que deduplicam os eventos não foram afetados. Parceiros que não deduplicam podem ter recebido postbacks duplicados para os tipos de eventos afetados durante esta janela e podem desduplicar dado event id. Nenhum dado do cliente foi perdido.

Traduzido automaticamente da atualização oficial do incidente.

1. 9 Gouere 2026 da 18:09 UTCinvestigating

   Estamos ativamente investigando um problema que afeta alguns aplicativos usando o Branch iOS SDK 3.14.1, onde o aplicativo pode falhar no lançamento em condições específicas de área de transferência do dispositivo.

2. 9 Gouere 2026 da 22:26 UTCmonitoring

   Identificamos os problemas subjacentes e lançamos o Branch iOS SDK v3.14.2, que inclui uma correção para o problema de crash-on-launch impactando alguns aplicativos usando o v3.14.1 em condições específicas de área de transferência do dispositivo. Se você estiver usando Branch iOS SDK 3.14.1, recomendamos atualizar para 3.14.2 para evitar problemas.

3. 10 Gouere 2026 da 00:14 UTCresolved

   Identificamos e resolvemos o problema que afeta os clientes usando o NativeLink na nossa versão iOS SDK 3.14.1 O que aconteceu: Em certos cenários de lançamento de aplicativos, se um usuário tivesse dados inesperados copiados para sua área de transferência, NativeLink poderia interpretá-lo de forma errada, causando potencialmente a falha do aplicativo. Quem foi impactado: Este problema apenas impactou aplicativos usando NativeLink que foram construídos no iOS SDK versão 3.14.1. Se o seu aplicativo não usa NativeLink, você não foi impactado por este problema. Como corrigi-lo: Isto foi totalmente resolvido no iOS SDK versão 3.14.2. Se seu aplicativo usa NativeLink, por favor, tenha sua equipe de engenharia atualizada para esta versão mais recente para receber a correção. A Solução Imediata (sem atualização da aplicação necessária): Se você não pode empurrar uma atualização de aplicativo imediatamente, você pode parar os quebras imediatamente, desabilitando NativeLink em seu painel.

Traduzido automaticamente da atualização oficial do incidente.

1. 2 Gouere 2026 da 23:47 UTCinvestigating

   Identificou-se um atraso no processamento de atribuição e webhooks. O processamento está funcionando corretamente, mas atualmente está atrasado em aproximadamente uma hora. A equipa de engenharia está a investigar a causa subjacente.

2. 3 Gouere 2026 da 02:28 UTCmonitoring

   A partir de 7:10 PT estamos agora processando webhooks dentro de 30 minutos. Estamos monitorando a situação e continuamos investigando por uma causa básica.

3. 3 Gouere 2026 da 10:59 UTCmonitoring

   A partir das 7:10 PT estamos agora processando webhooks dentro de 30 minutos e não vemos atrasos no nosso processamento de atribuição. Estamos monitorando a situação e continuamos investigando por uma causa básica.

4. 3 Gouere 2026 da 16:27 UTCinvestigating

   Atualmente estamos investigando uma questão que começou às 7:30 da PT, que está impactando nossos serviços. O processamento do Webhook está a exceder os nossos 30 minutos de SLA. Além disso, as exportações de dados e a disponibilidade de dados dentro de nossas APIs estão passando por atrasos de até quatro horas. Estamos trabalhando ativamente para identificar a causa raiz e forneceremos atualizações adicionais à medida que mais informações ficam disponíveis.

5. 3 Gouere 2026 da 23:56 UTCmonitoring

   Neste momento acreditamos que temos identificado e abordado a causa raiz e todos os sistemas estão de volta ao normal. Webhooks e disponibilidade de dados estão dentro SLA e limites normais. Permaneceremos em monitoramento durante o fim de semana.

6. 8 Gouere 2026 da 18:45 UTCresolved

   Este incidente foi resolvido.

Traduzido automaticamente da atualização oficial do incidente.

1. 26 Meurzh 2026 da 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 Meurzh 2026 da 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 Meurzh 2026 da 15:42 UTCresolved

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

1. 13 Meurzh 2026 da 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 Meurzh 2026 da 09:10 UTCresolved

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

1. 5 Meurzh 2026 da 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 Meurzh 2026 da 18:09 UTCmonitoring

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

3. 5 Meurzh 2026 da 19:20 UTCresolved

   Latency has now returned to normal.

1. 20 Cʼhwevrer 2026 da 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 Du 2025 da 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 Du 2025 da 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 Gwengolo 2025 da 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 Gwengolo 2025 da 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 Gwengolo 2025 da 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 Gwengolo 2025 da 23:28 UTCresolved

   We are once again seeing successful requests

1. 14 Eost 2025 da 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 Eost 2025 da 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 Eost 2025 da 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 Eost 2025 da 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 Eost 2025 da 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 Ebrel 2025 da 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 Ebrel 2025 da 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 Ebrel 2025 da 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 Meurzh 2025 da 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 Meurzh 2025 da 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 Meurzh 2025 da 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 Meurzh 2025 da 16:50 UTCresolved

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

1. 18 Meurzh 2025 da 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 Meurzh 2025 da 16:05 UTCresolved

   Cohort Analytics service is now up and working

1. 15 Meurzh 2025 da 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 Meurzh 2025 da 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 Meurzh 2025 da 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 Kerzu 2024 da 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 Kerzu 2024 da 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 Gwengolo 2024 da 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 Gwengolo 2024 da 10:43 UTCresolved

   Dashboard services have stabilized and returned to normal.

1. 27 Eost 2024 da 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 Eost 2024 da 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 Eost 2024 da 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.