Branch Outage History

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

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

Latency has now returned to normal.

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.

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.

Our team has now pushed a fix to resolve the issue. We are assessing impact and will follow up with more details.

We are once again seeing successful requests

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

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.

As of 08:36 PM Pacific Time, we have restored the Journey services. You should now be able to create and clone Journeys successfully.

As of 1:04PM PST we have recovered 100% of the functionality and are reporting success rates and latency are back to normal.

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

Cohort Analytics service is now up and working

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.

We now see a full recovery of the Facebook API. We will continue to monitor but all systems have returned to normal.

Dashboard services have stabilized and returned to normal.

As of 9:00 am PST (16:00 UTC), we have confirmed the fix applied by Google has normalised the event attributions.

This incident has been resolved.

We’ve released a change to improve the end user experience by reducing the Deepview’s auto-fallback-redirect delay. As a result, if the link has a web URL set that is configured for App Links, the app will be opened by this mechanism very shortly after showing the Deepview. We will continue to investigate solutions to iterate and optimize the user experience.

We identified the issue with network configurations and Universal Email Services have now been restored.

This incident has been resolved.

Backfill has now been completed. The data displayed in the dashboard should now be complete and accurate, no data was lost. If any exports containing Unique Open data were performed earlier, we advise on exporting once again to ensure data accuracy.

Attribution pipeline has returned to normal and customers should no longer experience a delay