Branch driftsforstyrrelser

1. 21. august 2026 kl. 00.47 UTCmonitoring

   Mellem august 19, 2026, 10: 40 AM PST og 20 august 2026, 4: 55 PM PST, en implementering konflikt forårsaget duplikerede webhook begivenheder, der skal sendes til Installs, Reinstalls, og bruger livscyklusbegivenheder. Ad Partners så den højeste effekt; Data Partners og Dashboard webhook abonnenter kan også have modtaget duplikater. Spørgsmålet er blevet identificeret og rettet. Indvirkning: Partnere, der deduplikerer begivenheder på deres ende blev ikke påvirket. Partnere som ikke duplikerer kan have modtaget duplikerede postbacks for de berørte begivenhedstyper i dette vindue og kan duplikere given event _ id. Ingen kundedata blev tabt.

Automatisk oversat fra den officielle hændelsesopdatering.

1. 9. juli 2026 kl. 18.09 UTCinvestigating

   Vi undersøger aktivt et problem, der påvirker nogle apps ved hjælp af Branch iOS SDK 3.14.1, hvor appen kan gå ned ved lanceringen under specifikke enhedens udklipsholder betingelser.

2. 9. juli 2026 kl. 22.26 UTCmonitoring

   Vi har identificeret de underliggende problemer og har udgivet Branch iOS SDK v3.14.2, som indeholder en rettelse til crash-on- launch problem påvirker nogle apps ved hjælp af v3.14.1 under specifikke enhed udklipsholder betingelser. Hvis du bruger Branch iOS SDK 3.14.1, anbefaler vi opdatering til 3.14.2 for at undgå problemer.

3. 10. juli 2026 kl. 00.14 UTCresolved

   Vi har identificeret og løst problemet påvirker kunder, der bruger NativeLink i vores iOS SDK version 3.14.1 Hvad skete der: I visse app lancering scenarier, hvis en bruger havde uventede data kopieret til deres udklipsholder, kunne NativeLink misfortolke det, potentielt forårsager app til at gå ned. Som blev påvirket: Dette problem kun påvirket apps ved hjælp af NativeLink, der blev bygget på iOS SDK version 3.14.1. Hvis din app ikke bruger NativeLink, var du ikke påvirket af dette problem. Sådan Fix det: Dette er blevet fuldt løst i iOS SDK version 3.14.2. Hvis din app bruger NativeLink, skal du have din engineering team opdatering til denne nyeste version til at modtage fix. Den umiddelbare arbejdsgang (ingen App opdatering kræves): Hvis du ikke kan skubbe en app opdatering med det samme, kan du stoppe nedbrud med det samme ved at deaktivere NativeLink i dit instrumentbræt.

Automatisk oversat fra den officielle hændelsesopdatering.

1. 2. juli 2026 kl. 23.47 UTCinvestigating

   Vi har identificeret en forsinkelse i tildeling behandling og webkroge. Behandlingen fungerer korrekt, men er i øjeblikket forsinket med ca. en time. Teknikerne undersøger den underliggende årsag.

2. 3. juli 2026 kl. 02.28 UTCmonitoring

   Fra 7: 10 PT er vi nu ved at behandle netkroge inden for 30 minutter. Vi overvåger situationen og fortsætter med at undersøge sagen for en grundlæggende årsag.

3. 3. juli 2026 kl. 10.59 UTCmonitoring

   Fra 7: 10 PT behandler vi nu webkroge inden for 30 minutter, og vi kan ikke se forsinkelser med vores tildeling behandling. Vi overvåger situationen og fortsætter med at undersøge sagen for en grundlæggende årsag.

4. 3. juli 2026 kl. 16.27 UTCinvestigating

   Vi er i øjeblikket ved at undersøge et spørgsmål, der startede omkring 7: 30 PT, som påvirker vores tjenester. Webhook behandling er i øjeblikket overstiger vores 30-minutters SLA. Desuden oplever dataeksport og datatilgængelighed inden for vores API 'er forsinkelser på op til fire timer. Vi arbejder aktivt på at identificere den grundlæggende årsag og vil give yderligere opdateringer, efterhånden som flere oplysninger bliver tilgængelige.

5. 3. juli 2026 kl. 23.56 UTCmonitoring

   På nuværende tidspunkt mener vi, at vi har identificeret og behandlet den grundlæggende årsag, og alle systemer er tilbage til normal. Webkroge og datatilgængelighed ligger inden for SLA og normale grænser. Vi bliver ved med at overvåge i weekenden.

6. 8. juli 2026 kl. 18.45 UTCresolved

   Denne hændelse er blevet løst.

Automatisk oversat fra den officielle hændelsesopdatering.

1. 26. marts 2026 kl. 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. marts 2026 kl. 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. marts 2026 kl. 15.42 UTCresolved

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

1. 13. marts 2026 kl. 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. marts 2026 kl. 09.10 UTCresolved

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

1. 5. marts 2026 kl. 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. marts 2026 kl. 18.09 UTCmonitoring

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

3. 5. marts 2026 kl. 19.20 UTCresolved

   Latency has now returned to normal.

1. 20. februar 2026 kl. 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. november 2025 kl. 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. november 2025 kl. 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. september 2025 kl. 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. september 2025 kl. 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. september 2025 kl. 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. september 2025 kl. 23.28 UTCresolved

   We are once again seeing successful requests

1. 14. august 2025 kl. 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 kl. 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 kl. 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 kl. 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 kl. 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. april 2025 kl. 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. april 2025 kl. 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. april 2025 kl. 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. marts 2025 kl. 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. marts 2025 kl. 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. marts 2025 kl. 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. marts 2025 kl. 16.50 UTCresolved

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

1. 18. marts 2025 kl. 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. marts 2025 kl. 16.05 UTCresolved

   Cohort Analytics service is now up and working

1. 15. marts 2025 kl. 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. marts 2025 kl. 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. marts 2025 kl. 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. december 2024 kl. 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. december 2024 kl. 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. september 2024 kl. 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. september 2024 kl. 10.43 UTCresolved

   Dashboard services have stabilized and returned to normal.

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