Historial de interrupciones de Branch

1. 21 de agosto de 2026 a las 0:47 UTCmonitoring

   Entre el 19 de agosto de 2026, 10:40 AM PST y el 20 de agosto de 2026, 4:55 PM PST, un conflicto de implementación causó que se enviaran eventos duplicados de webhook para Installs, Reinstalls y Eventos de Lifecycle de Usuario. Ad Partners vio el mayor impacto; Data Partners y suscriptores de Dashboard webhook también pueden haber recibido duplicados. La cuestión ha sido identificada y resuelta. Impacto: Los socios que deduplican eventos en su extremo no se vieron afectados. Los socios que no deduplican pueden haber recibido postbacks duplicados para los tipos de eventos afectados durante esta ventana y pueden deduplicar dado event id. No se perdieron datos de clientes.

Traducido automáticamente desde la actualización oficial del incidente.

1. 9 de julio de 2026 a las 18:09 UTCinvestigating

   Estamos investigando activamente un problema que afecta a algunas aplicaciones usando Branch iOS SDK 3.14.1 donde la aplicación puede chocar en el lanzamiento bajo condiciones específicas de portapapeles de dispositivo.

2. 9 de julio de 2026 a las 22:26 UTCmonitoring

   Hemos identificado los problemas subyacentes y hemos lanzado Branch iOS SDK v3.14.2, lo que incluye una solución para el problema de bloqueo en el lanzamiento que impacta algunas aplicaciones usando v3.14.1 bajo condiciones específicas del portapapeles de dispositivos. Si usted está utilizando Branch iOS SDK 3.14.1, recomendamos actualizar a 3.14.2 para evitar cualquier problema.

3. 10 de julio de 2026 a las 0:14 UTCresolved

   Hemos identificado y resuelto el problema que afecta a los clientes usando NativeLink en nuestra versión iOS SDK 3.14.1 Lo que sucedió: En ciertos escenarios de lanzamiento de aplicaciones, si un usuario hubiera copiado datos inesperados a su portapapeles, NativeLink podría malinterpretarlo, lo que podría provocar que la aplicación se estrellara. Quién fue afectado: Este número sólo impactó aplicaciones usando NativeLink que fueron construidas en la versión 3.14.1 de iOS SDK. Si su aplicación no utiliza NativeLink, no fue impactado por este problema. Cómo arreglarlo: Esto se ha resuelto completamente en iOS SDK versión 3.14.2. Si su aplicación utiliza NativeLink, por favor tenga su equipo de ingeniería actualizado a esta última versión para recibir la solución. La solución de trabajo inmediata (No se requiere actualización de aplicaciones): Si no puede presionar una actualización de la aplicación inmediatamente, puede detener los fallos de inmediato desactivando NativeLink en su panel de control.

Traducido automáticamente desde la actualización oficial del incidente.

1. 2 de julio de 2026 a las 23:47 UTCinvestigating

   Hemos identificado un retraso en el procesamiento de la atribución y webhooks. El procesamiento funciona correctamente pero actualmente retrasado aproximadamente una hora. El equipo de Ingeniería está investigando la causa subyacente.

2. 3 de julio de 2026 a las 2:28 UTCmonitoring

   A partir de 7:10 PT ahora estamos procesando webhooks en 30 minutos. Estamos monitoreando la situación y continuamos investigando por una causa raíz.

3. 3 de julio de 2026 a las 10:59 UTCmonitoring

   A partir de 7:10 PT ahora estamos procesando webhooks en 30 minutos y no vemos demoras con nuestro procesamiento de atribución. Estamos monitoreando la situación y continuamos investigando por una causa raíz.

4. 3 de julio de 2026 a las 16:27 UTCinvestigating

   Actualmente estamos investigando una cuestión que comenzó a aproximadamente 7:30 PT, que está afectando nuestros servicios. El procesamiento de Webhook supera actualmente nuestro SLA de 30 minutos. Además, las exportaciones de datos y la disponibilidad de datos dentro de nuestras API están experimentando retrasos de hasta cuatro horas. Trabajamos activamente para identificar la causa raíz y proporcionaremos nuevas actualizaciones a medida que se disponga de más información.

5. 3 de julio de 2026 a las 23:56 UTCmonitoring

   En este momento creemos que hemos identificado y abordado la causa raíz y todos los sistemas vuelven a la normalidad. Webhooks y disponibilidad de datos están dentro de SLA y límites normales. Seguiremos en Monitoreo durante el fin de semana.

6. 8 de julio de 2026 a las 18:45 UTCresolved

   Este incidente ha sido resuelto.

Traducido automáticamente desde la actualización oficial del incidente.

1. 26 de marzo de 2026 a las 3: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 de marzo de 2026 a las 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 de marzo de 2026 a las 15:42 UTCresolved

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

1. 13 de marzo de 2026 a las 6: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 de marzo de 2026 a las 9:10 UTCresolved

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

1. 5 de marzo de 2026 a las 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 de marzo de 2026 a las 18:09 UTCmonitoring

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

3. 5 de marzo de 2026 a las 19:20 UTCresolved

   Latency has now returned to normal.

1. 20 de febrero de 2026 a las 1: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 de noviembre de 2025 a las 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 de noviembre de 2025 a las 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 de septiembre de 2025 a las 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 de septiembre de 2025 a las 1: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 de septiembre de 2025 a las 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 de septiembre de 2025 a las 23:28 UTCresolved

   We are once again seeing successful requests

1. 14 de agosto de 2025 a las 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 de agosto de 2025 a las 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 de agosto de 2025 a las 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 de agosto de 2025 a las 3: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 de agosto de 2025 a las 5: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 de abril de 2025 a las 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 de abril de 2025 a las 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 de abril de 2025 a las 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 de marzo de 2025 a las 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 de marzo de 2025 a las 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 de marzo de 2025 a las 3: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 de marzo de 2025 a las 16:50 UTCresolved

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

1. 18 de marzo de 2025 a las 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 de marzo de 2025 a las 16:05 UTCresolved

   Cohort Analytics service is now up and working

1. 15 de marzo de 2025 a las 6: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 de marzo de 2025 a las 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 de marzo de 2025 a las 3: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 de diciembre de 2024 a las 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 de diciembre de 2024 a las 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 de septiembre de 2024 a las 9: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 de septiembre de 2024 a las 10:43 UTCresolved

   Dashboard services have stabilized and returned to normal.

1. 27 de agosto de 2024 a las 3: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 de agosto de 2024 a las 4:50 UTCmonitoring

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

3. 29 de agosto de 2024 a las 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.