Cronologia delle interruzioni di Branch

1. 21 agosto 2026 alle ore 00:47 UTCmonitoring

   Tra il 19 agosto 2026, 10:40 PST e il 20 agosto 20, 2026, 4:55 PM PST, un conflitto di distribuzione ha causato duplicati eventi webhook da inviare per Installs, Reinstalls, and User Lifecycle Events. Ad Partners ha visto il più alto impatto; i partner di dati e gli abbonati webhook di Dashboard possono anche aver ricevuto duplicati. Il problema è stato identificato e risolto. Impatto: I partner che deduplicano gli eventi alla loro fine non sono stati colpiti. I partner che non deduplicano possono aver ricevuto postback duplicati per i tipi di eventi interessati durante questa finestra e possono deduplicare dato event id. Nessun dato del cliente è stato perso.

Tradotto automaticamente dall'aggiornamento ufficiale dell'incidente.

1. 9 luglio 2026 alle ore 18:09 UTCinvestigating

   Stiamo attivamente indagando su un problema che riguarda alcune applicazioni utilizzando Branch iOS SDK 3.14.1 in cui l'applicazione può crash sul lancio in determinate condizioni del dispositivo clipboard.

2. 9 luglio 2026 alle ore 22:26 UTCmonitoring

   Abbiamo identificato i problemi sottostanti e abbiamo rilasciato Branch iOS SDK v3.14.2, che include una correzione per il problema crash-on-launch che colpisce alcune applicazioni utilizzando v3.14.1 in specifiche condizioni del dispositivo clipboard. Se si utilizza Branch iOS SDK 3.14.1, si consiglia di aggiornare a 3.14.2 per evitare qualsiasi problema.

3. 10 luglio 2026 alle ore 00:14 UTCresolved

   Abbiamo identificato e risolto il problema che riguarda i clienti che utilizzano NativeLink nella nostra versione SDK iOS 3.14.1 Ciò che è successo: In alcuni scenari di avvio dell'app, se un utente aveva dati inaspettati copiati al proprio appunti, NativeLink potrebbe interpretarlo male, potenzialmente causando l'applicazione di crash. Chi è stato colpito: Questo problema ha colpito solo le applicazioni utilizzando NativeLink che sono stati costruiti su iOS SDK versione 3.14.1. Se l'applicazione non utilizza NativeLink, non è stato influenzato da questo problema. Come risolvere: Questo è stato completamente risolto in iOS SDK versione 3.14.2. Se l'applicazione utilizza NativeLink, si prega di avere l'aggiornamento del team di ingegneria a questa ultima versione per ricevere la correzione. Il Workaround immediato (Nessun aggiornamento App richiesto): Se non è possibile spingere immediatamente un aggiornamento app, è possibile arrestare i crash immediatamente disabilitando NativeLink nella dashboard.

Tradotto automaticamente dall'aggiornamento ufficiale dell'incidente.

1. 2 luglio 2026 alle ore 23:47 UTCinvestigating

   Abbiamo identificato un ritardo nell'elaborazione di attribuzione e webhooks. L'elaborazione funziona correttamente ma attualmente ritardata di circa un'ora. Il team di Ingegneria sta indagando sulla causa sottostante.

2. 3 luglio 2026 alle ore 02:28 UTCmonitoring

   A partire da 7:10 PT stiamo ora elaborando webhooks entro 30 minuti. Stiamo monitorando la situazione e continuiamo a indagare per una causa principale.

3. 3 luglio 2026 alle ore 10:59 UTCmonitoring

   A partire da 7:10 PT stiamo ora elaborando webhooks entro 30 minuti e non vediamo ritardi con il nostro trattamento di attribuzione. Stiamo monitorando la situazione e continuiamo a indagare per una causa principale.

4. 3 luglio 2026 alle ore 16:27 UTCinvestigating

   Stiamo attualmente indagando su un problema che ha cominciato a circa 7:30 PT, che sta influenzando i nostri servizi. La lavorazione di Webhook sta superando il nostro SLA di 30 minuti. Inoltre, le esportazioni di dati e la disponibilità di dati all'interno delle nostre API stanno vivendo ritardi fino a quattro ore. Stiamo lavorando attivamente per identificare la causa principale e fornirà ulteriori aggiornamenti come ulteriori informazioni diventano disponibili.

5. 3 luglio 2026 alle ore 23:56 UTCmonitoring

   In questo momento crediamo di aver identificato e affrontato la causa principale e tutti i sistemi sono tornati alla normalità. Webhooks e la disponibilità dei dati sono all'interno di SLA e limiti normali. Resteremo in Monitoraggio attraverso il fine settimana.

6. 8 luglio 2026 alle ore 18:45 UTCresolved

   Questo incidente è stato risolto.

Tradotto automaticamente dall'aggiornamento ufficiale dell'incidente.

1. 26 marzo 2026 alle ore 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 marzo 2026 alle ore 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 marzo 2026 alle ore 15:42 UTCresolved

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

1. 13 marzo 2026 alle ore 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 marzo 2026 alle ore 09:10 UTCresolved

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

1. 5 marzo 2026 alle ore 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 marzo 2026 alle ore 18:09 UTCmonitoring

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

3. 5 marzo 2026 alle ore 19:20 UTCresolved

   Latency has now returned to normal.

1. 20 febbraio 2026 alle ore 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 alle ore 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 alle ore 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 settembre 2025 alle ore 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 settembre 2025 alle ore 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 settembre 2025 alle ore 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 settembre 2025 alle ore 23:28 UTCresolved

   We are once again seeing successful requests

1. 14 agosto 2025 alle ore 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 agosto 2025 alle ore 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 agosto 2025 alle ore 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 agosto 2025 alle ore 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 agosto 2025 alle ore 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 aprile 2025 alle ore 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 aprile 2025 alle ore 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 aprile 2025 alle ore 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 marzo 2025 alle ore 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 marzo 2025 alle ore 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 marzo 2025 alle ore 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 marzo 2025 alle ore 16:50 UTCresolved

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

1. 18 marzo 2025 alle ore 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 marzo 2025 alle ore 16:05 UTCresolved

   Cohort Analytics service is now up and working

1. 15 marzo 2025 alle ore 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 marzo 2025 alle ore 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 marzo 2025 alle ore 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 dicembre 2024 alle ore 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 dicembre 2024 alle ore 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 settembre 2024 alle ore 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 settembre 2024 alle ore 10:43 UTCresolved

   Dashboard services have stabilized and returned to normal.

1. 27 agosto 2024 alle ore 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 agosto 2024 alle ore 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 agosto 2024 alle ore 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.