Istoricul incidentelor Branch

1. 21 august 2026 la 00:47 UTCmonitoring

   Între 19 august 2026, 10:40 AM PST și 20 august, 2026, 4:55 PM PST, un conflict de desfășurare a cauzat duplicate evenimente webhook care urmează să fie trimise pentru Instalări, Reinstalls, și User Lifecycle Events. Ad Partners a văzut cel mai mare impact; Partenerii de date şi abonaţii de la Dashboard au primit şi duplicate. Problema a fost identificată şi rezolvată. Impact: Partenerii care deduplică evenimentele la sfârșitul lor nu au fost afectați. Partenerii care nu se deduplică pot fi primit postback-uri duplicate pentru tipurile de evenimente afectate în timpul acestei ferestre și pot deduplica dat eveniment id. Nu s-au pierdut date despre clienţi.

Traducere automată din actualizarea oficială a incidentului.

1. 9 iulie 2026 la 18:09 UTCinvestigating

   Investigăm în mod activ o problemă care afectează unele aplicații folosind Branch iOS SDK 3.14.1 în care aplicația se poate prăbuși la lansare în condiții specifice clipboard dispozitiv.

2. 9 iulie 2026 la 22:26 UTCmonitoring

   Am identificat problemele care stau la baza și am lansat Branch iOS SDK v3.14.2, care include un fix pentru problema crash-on-lanch impact unele aplicații folosind v3.14.1 în condiții specifice clipboard dispozitiv. Dacă utilizați Sucursala iOS SDK 3.14.1, vă recomandăm actualizarea la 3.14.2 pentru a evita orice probleme.

3. 10 iulie 2026 la 00:14 UTCresolved

   Am identificat și rezolvat problema care afectează clienții folosind NativeLink în versiunea noastră iOS SDK 3.14.1 Ce s-a întâmplat: În anumite scenarii de lansare a aplicației, dacă un utilizator ar avea date neașteptate copiate în clipboard-ul lor, NativeLink ar putea interpreta greșit, ceea ce ar putea cauza prăbușirea aplicației. Cine a fost influenţat: Această problemă a afectat doar aplicațiile care au fost construite pe versiunea iOS SDK 3.14.1. Dacă aplicația dumneavoastră nu utilizează NativeLink, nu ați fost afectat de această problemă. Cum să-l reparați: Acest lucru a fost complet rezolvat în versiunea iOS SDK 3.14.2. Daca aplicatia dumneavoastra foloseste NativeLink, va rugam sa updatati echipa de inginerie la aceasta ultima versiune pentru a primi fix. Lucrul imediat (nu este necesară actualizarea aplicației): Dacă nu puteți împinge imediat o actualizare a aplicației, puteți opri imediat accidentele dezactivând NativeLink din tabloul de bord.

Traducere automată din actualizarea oficială a incidentului.

1. 2 iulie 2026 la 23:47 UTCinvestigating

   Am identificat o întârziere în procesarea de atribuire și a site-uri web. Prelucrarea funcționează corect, dar în prezent întârzie cu aproximativ o oră. Echipa de ingineri investighează cauza principală.

2. 3 iulie 2026 la 02:28 UTCmonitoring

   De la 7:10 PT, acum procesăm site-uri web în 30 de minute. Monitorizăm situaţia şi continuăm să investigăm cauza principală.

3. 3 iulie 2026 la 10:59 UTCmonitoring

   Începând cu ora 7:10 PT, acum procesăm site-uri web în 30 de minute și nu vedem întârzieri în procesul de atribuire. Monitorizăm situaţia şi continuăm să investigăm cauza principală.

4. 3 iulie 2026 la 16:27 UTCinvestigating

   Investigăm în prezent o problemă care a început la aproximativ 7:30 PT, care afectează serviciile noastre. Procesarea webhook depăşeşte în prezent SLA-ul nostru de 30 de minute. În plus, exporturile de date și disponibilitatea datelor în cadrul API-urilor noastre se confruntă cu întârzieri de până la patru ore. Lucrăm în mod activ la identificarea cauzei profunde și vom oferi actualizări suplimentare pe măsură ce vor fi disponibile mai multe informații.

5. 3 iulie 2026 la 23:56 UTCmonitoring

   În acest moment credem că am identificat şi abordat cauza fundamentală şi că toate sistemele au revenit la normal. Webhooks și disponibilitatea datelor sunt în cadrul SLA și limite normale. Vom rămâne în monitorizare în weekend.

6. 8 iulie 2026 la 18:45 UTCresolved

   Acest incident a fost rezolvat.

Traducere automată din actualizarea oficială a incidentului.

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

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

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

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

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

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

3. 5 martie 2026 la 19:20 UTCresolved

   Latency has now returned to normal.

1. 20 februarie 2026 la 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 noiembrie 2025 la 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 noiembrie 2025 la 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 septembrie 2025 la 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 septembrie 2025 la 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 septembrie 2025 la 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 septembrie 2025 la 23:28 UTCresolved

   We are once again seeing successful requests

1. 14 august 2025 la 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 august 2025 la 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 august 2025 la 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 august 2025 la 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 august 2025 la 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 aprilie 2025 la 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 aprilie 2025 la 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 aprilie 2025 la 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 martie 2025 la 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 martie 2025 la 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 martie 2025 la 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 martie 2025 la 16:50 UTCresolved

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

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

   Cohort Analytics service is now up and working

1. 15 martie 2025 la 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 martie 2025 la 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 martie 2025 la 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 decembrie 2024 la 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 decembrie 2024 la 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 septembrie 2024 la 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 septembrie 2024 la 10:43 UTCresolved

   Dashboard services have stabilized and returned to normal.

1. 27 august 2024 la 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 august 2024 la 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 august 2024 la 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.