Branch Outage History

14 incidents recorded over the last 365 days, 11 of them resolved. Durations are measured from when PulsAPI first saw the problem to when it cleared, which is usually longer than the vendor's own figure.

Live Branch status100.00% uptime history

Every Recorded Branch Incident

Branch incidents, newest first, with date, duration and status.
DateIncidentDurationStatus
Oct 26, 2026Custom Exports API – Processing DelayWe are now seeing successful completion of the previously delayed jobs and all current exports are processing without any delays.1h 37mResolved
Sep 3, 2026Service Performance IssueThis has now been resolved. Earlier, an AWS service outage caused a service disruption to attribution processing, affecting V1/V2 event delivery. Impact: V1/V2 events sent between2:56 PM PT to 3:38 PM PT were not…1h 56mResolved
Aug 24, 2026Delayed Webhook DeliveryMaintenance is now complete, and all webhook services are back to normal. We are currently processing the backlog of queued webhooks, and all delayed notifications will be delivered shortly. Thank you for your patience.23 minResolved
Aug 21, 2026Duplicate Webhook EventsThis incident has been resolved.253h 57mResolved
Jul 9, 2026iOS SDK 3.14.1 App Crash Related to Pasteboard URI ParsingWe have identified and resolved the issue affecting customers using NativeLink in our iOS SDK version 3.14.1 What Happened: In certain app launch scenarios, if a user had unexpected data copied to their clipboard…6h 4mResolved
Jul 2, 2026Delay in attributions and webhooksThis incident has been resolved.138h 58mResolved
Jun 30, 2026Branch Scraper IP Allowlist UpdateThe scheduled maintenance has been completed.1 minScheduled
Mar 26, 2026Services Degraded: X API Platform Impacting X (formerly Twitter) AttributionsWe have confirmed that X’s API Service success rates have returned to normal. We will continue to monitor.11h 57mResolved
Mar 13, 2026Services Degraded: Missing Dashboard FeaturesThe identified issue has been resolved, and services are now restored. You should see the dashboard features available again.2h 11mResolved
Mar 5, 2026Meta API LatencyLatency has now returned to normal.2h 46mResolved
Feb 24, 2026Planned System UpgradeThe scheduled maintenance has been completed.2h 0mScheduled
Feb 19, 2026Service Performance IssueBetween 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…0 minResolved
Dec 9, 2025Planned System UpgradeThe scheduled maintenance has been completed.3h 0mScheduled
Nov 27, 2025Daily Exports API Service ImpactWe 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.47 minResolved

Hear about the next one while it is open

Everything above is a record written after the fact. We can email you when the next Branch incident opens instead, at the point where knowing still changes what you do.

Free, no password, no card. Unsubscribe in one click.

How to Read This Branch Incident Log

Each row is an incident PulsAPI observed, not a summary written afterwards. The duration is wall-clock time between the first failing check and the first clean one, so it includes the window before Branch acknowledged anything. Vendor post-mortems typically measure from acknowledgement, which is why their numbers are usually shorter.

Incidents still open have no duration yet and are listed as ongoing rather than being given a running total. The archive covers the last 365 days; anything older has aged out of the window rather than never having happened.

The longest single Branch outage in this window ran 10d 13h, against a mean recovery of 1d 6h. If you depend on Branch in a customer-facing path, the longest figure is the one to design around. The mean is what happens on a normal bad day; the maximum is what happens on the worst one.