Historique des pannes de Branch

1. 21 août 2026 à 00:47 UTCmonitoring

   Entre le 19 août, 2026, 10:40 PST et le 20 août, 2026, 16:55 PST, un conflit de déploiement a causé l'envoi d'événements webhook dupliqués pour les Installations, les Réinstallations et les Événements du cycle de vie de l'utilisateur. Les partenaires publicitaires ont eu le plus d'impact; Data Partners et les abonnés de Dashboard Webhook peuvent également avoir reçu des duplicatas. Le problème a été identifié et corrigé. Impact: Les partenaires qui déduisent les événements à leur fin n'ont pas été touchés. Les partenaires qui ne dédoublent pas peuvent avoir reçu des postbacks en double pour les types d'événements touchés pendant cette fenêtre et peuvent dédoubler en fonction de event id. Aucune donnée client n'a été perdue.

Traduit automatiquement depuis la mise à jour officielle de l'incident.

1. 9 juillet 2026 à 18:09 UTCinvestigating

   Nous enquêtons activement sur un problème touchant certaines applications en utilisant Branch iOS SDK 3.14.1 où l'application peut s'écraser au lancement dans des conditions de presse-papiers spécifiques.

2. 9 juillet 2026 à 22:26 UTCmonitoring

   Nous avons identifié les problèmes sous-jacents et avons publié Branch iOS SDK v3.14.2, qui inclut une correction pour le problème de crash-on-launch impactant certaines applications utilisant v3.14.1 dans des conditions de presse-papiers spécifiques. Si vous utilisez Branch iOS SDK 3.14.1, nous vous recommandons de mettre à jour le 3.14.2 pour éviter tout problème.

3. 10 juillet 2026 à 00:14 UTCresolved

   Nous avons identifié et résolu le problème touchant les clients utilisant NativeLink dans notre version 3.14.1 de SDK iOS Ce qui s'est passé : Dans certains scénarios de lancement d'applications, si un utilisateur avait des données inattendues copiées dans son presse-papiers, NativeLink pourrait l'interpréter mal, ce qui pourrait provoquer l'écrasement de l'application. Qui a été touché : Ce problème n'a touché que les applications utilisant NativeLink qui ont été construites sur iOS SDK version 3.14.1. Si votre application n'utilise pas NativeLink, vous n'avez pas été touché par ce problème. Comment le corriger: Ceci a été entièrement résolu dans iOS SDK version 3.14.2. Si votre application utilise NativeLink, veuillez demander à votre équipe d'ingénierie de mettre à jour cette dernière version pour recevoir la correction. La solution immédiate (pas de mise à jour de l'application requise) : Si vous ne pouvez pas pousser une mise à jour d'application immédiatement, vous pouvez arrêter les crashs tout de suite en désactivant NativeLink dans votre tableau de bord.

Traduit automatiquement depuis la mise à jour officielle de l'incident.

1. 2 juillet 2026 à 23:47 UTCinvestigating

   Nous avons identifié un retard dans le traitement de l'attribution et les webhooks. Le traitement fonctionne correctement mais est actuellement retardé d'environ une heure. L'équipe du génie enquête sur la cause sous-jacente.

2. 3 juillet 2026 à 02:28 UTCmonitoring

   A partir de 7:10 PT, nous traitons maintenant les webhooks dans les 30 minutes. Nous suivons la situation et continuons d'enquêter sur une cause fondamentale.

3. 3 juillet 2026 à 10:59 UTCmonitoring

   À partir de 7:10 PT, nous traitons maintenant les webhooks dans les 30 minutes et nous ne voyons pas de retards avec notre traitement d'attribution. Nous suivons la situation et continuons d'enquêter sur une cause fondamentale.

4. 3 juillet 2026 à 16:27 UTCinvestigating

   Nous enquêtons actuellement sur un problème qui a commencé à environ 7 h 30, ce qui a une incidence sur nos services. Webhook traitement dépasse actuellement notre 30 minutes SLA. De plus, les exportations de données et la disponibilité des données dans nos API connaissent des retards allant jusqu'à quatre heures. Nous travaillons activement à identifier la cause fondamentale et fournirons d'autres mises à jour à mesure que de plus amples renseignements seront disponibles.

5. 3 juillet 2026 à 23:56 UTCmonitoring

   À l'heure actuelle, nous croyons avoir identifié et abordé la cause fondamentale et tous les systèmes sont de retour à la normale. Webhooks et la disponibilité des données sont dans SLA et limites normales. Nous resterons en surveillance tout au long du week-end.

6. 8 juillet 2026 à 18:45 UTCresolved

   Cet incident a été résolu.

Traduit automatiquement depuis la mise à jour officielle de l'incident.

1. 26 mars 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 mars 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 mars 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 mars 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 mars 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 mars 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 mars 2026 à 18:09 UTCmonitoring

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

3. 5 mars 2026 à 19:20 UTCresolved

   Latency has now returned to normal.

1. 20 février 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 novembre 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 novembre 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 septembre 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 septembre 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 septembre 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 septembre 2025 à 23:28 UTCresolved

   We are once again seeing successful requests

1. 14 août 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 août 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 août 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 août 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 août 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 avril 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 avril 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 avril 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 mars 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 mars 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 mars 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 mars 2025 à 16:50 UTCresolved

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

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

   Cohort Analytics service is now up and working

1. 15 mars 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 mars 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 mars 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 décembre 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 décembre 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 septembre 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 septembre 2024 à 10:43 UTCresolved

   Dashboard services have stabilized and returned to normal.

1. 27 août 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 août 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 août 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.