Störungsverlauf von Branch

1. 21. August 2026 um 00:47 UTCmonitoring

   Zwischen dem 19. August 2026, 10:40 Uhr PST und dem 20. August 2026, 16:55 Uhr PST führte ein Bereitstellungskonflikt dazu, dass doppelte Webhook-Ereignisse für Installationen, Neuinstallationen und Benutzerlebenszyklus-Ereignisse gesendet wurden. Werbepartner sahen die größten Auswirkungen; Datenpartner und Dashboard-Webhook-Abonnenten haben möglicherweise auch Duplikate erhalten. Das Problem wurde identifiziert und behoben. Auswirkungen: Partner, die Ereignisse an ihrem Ende deduplizieren, waren nicht betroffen. Partner, die nicht deduplizieren, haben möglicherweise doppelte Postbacks für die betroffenen Ereignistypen in diesem Fenster erhalten und können die gegebene event id deduplizieren. Es gingen keine Kundendaten verloren.

Automatisch aus der offiziellen Störungsmeldung übersetzt.

1. 9. Juli 2026 um 18:09 UTCinvestigating

   Wir untersuchen aktiv ein Problem, das einige Apps mit Branch iOS SDK 3.14.1 betrifft, bei denen die App beim Start unter bestimmten Zwischenablagebedingungen abstürzen kann.

2. 9. Juli 2026 um 22:26 UTCmonitoring

   Wir haben die zugrunde liegenden Probleme identifiziert und Branch iOS SDK v3.14.2 veröffentlicht, das eine Korrektur für das Crash-on-Launch-Problem enthält, das einige Apps mit v3.14.1 unter bestimmten Geräte-Zwischenablagebedingungen betrifft. Wenn Sie Branch iOS SDK 3.14.1 verwenden, empfehlen wir, auf 3.14.2 zu aktualisieren, um Probleme zu vermeiden.

3. 10. Juli 2026 um 00:14 UTCresolved

   Wir haben das Problem identifiziert und behoben, das Kunden betrifft, die NativeLink in unserer iOS SDK Version 3.14.1 verwenden. Was ist passiert: Wenn ein Benutzer in bestimmten App-Startszenarien unerwartete Daten in seine Zwischenablage kopiert hat, könnte NativeLink diese falsch interpretieren und möglicherweise zum Absturz der App führen. Wer war betroffen: Dieses Problem betraf nur Apps mit NativeLink, die auf iOS SDK Version 3.14.1 gebaut wurden. Wenn Ihre App NativeLink nicht verwendet, sind Sie von diesem Problem nicht betroffen. So beheben Sie es: Dies wurde in iOS SDK Version 3.14.2 vollständig behoben. Wenn Ihre App NativeLink verwendet, lassen Sie Ihr Engineering-Team bitte auf diese neueste Version aktualisieren, um den Fix zu erhalten. Der sofortige Workaround (kein App-Update erforderlich): Wenn Sie ein App-Update nicht sofort drücken können, können Sie die Abstürze sofort stoppen, indem Sie NativeLink in Ihrem Dashboard deaktivieren.

Automatisch aus der offiziellen Störungsmeldung übersetzt.

1. 2. Juli 2026 um 23:47 UTCinvestigating

   Wir haben eine Verzögerung bei der Attributionsverarbeitung und Webhooks festgestellt. Die Verarbeitung funktioniert korrekt, verzögert sich jedoch derzeit um etwa eine Stunde. Das Engineering-Team untersucht die zugrunde liegende Ursache.

2. 3. Juli 2026 um 02:28 UTCmonitoring

   Ab 7:10 PT verarbeiten wir Webhooks nun innerhalb von 30 Minuten. Wir beobachten die Situation und untersuchen weiterhin nach einer Ursache.

3. 3. Juli 2026 um 10:59 UTCmonitoring

   Ab 7:10 PT verarbeiten wir jetzt Webhooks innerhalb von 30 Minuten und wir sehen keine Verzögerungen bei unserer Attributionsverarbeitung. Wir beobachten die Situation und untersuchen weiterhin nach einer Ursache.

4. 3. Juli 2026 um 16:27 UTCinvestigating

   Wir untersuchen derzeit ein Problem, das um ca. 7:30 PT begann, was sich auf unsere Dienste auswirkt. Die Webhook-Verarbeitung übersteigt derzeit unsere 30-minütige SLA. Darüber hinaus erleben Datenexporte und Datenverfügbarkeit innerhalb unserer APIs Verzögerungen von bis zu vier Stunden. Wir arbeiten aktiv daran, die Ursache zu identifizieren und werden weitere Updates bereitstellen, sobald mehr Informationen verfügbar werden.

5. 3. Juli 2026 um 23:56 UTCmonitoring

   Zu diesem Zeitpunkt glauben wir, dass wir die Ursache identifiziert und angegangen haben und alle Systeme wieder normal sind. Webhooks und Datenverfügbarkeit liegen innerhalb von SLA und normalen Grenzen. Wir werden bis zum Wochenende im Monitoring bleiben.

6. 8. Juli 2026 um 18:45 UTCresolved

   Dieser Vorfall wurde behoben.

Automatisch aus der offiziellen Störungsmeldung übersetzt.

1. 26. März 2026 um 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. März 2026 um 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. März 2026 um 15:42 UTCresolved

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

1. 13. März 2026 um 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. März 2026 um 09:10 UTCresolved

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

1. 5. März 2026 um 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. März 2026 um 18:09 UTCmonitoring

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

3. 5. März 2026 um 19:20 UTCresolved

   Latency has now returned to normal.

1. 20. Februar 2026 um 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 um 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 um 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 um 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 um 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 um 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 um 23:28 UTCresolved

   We are once again seeing successful requests

1. 14. August 2025 um 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 um 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 um 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 um 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 um 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 um 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 um 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 um 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. März 2025 um 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. März 2025 um 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. März 2025 um 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. März 2025 um 16:50 UTCresolved

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

1. 18. März 2025 um 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. März 2025 um 16:05 UTCresolved

   Cohort Analytics service is now up and working

1. 15. März 2025 um 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. März 2025 um 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. März 2025 um 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. Dezember 2024 um 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. Dezember 2024 um 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 um 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 um 10:43 UTCresolved

   Dashboard services have stabilized and returned to normal.

1. 27. August 2024 um 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 um 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 um 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.