Branch logo

Is Branch Down?

SaaSLive status, outages, and incident history

No. Branch is up right now.

Every monitored Branch system is operational as of September 26, 2026. PulsAPI did not find an outage in its latest check of the official status feed.

OperationalChecked 14m agoLive · 60s while moving

Know the moment Branch breaks

Branch is healthy right now. We keep checking (every 60 seconds once it starts moving) and email you the moment that changes.

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

How we know: the official Branch status page, PulsAPI's own check (every 60 seconds while one is moving, every 5 to 20 minutes while it is stable), and outage reports from engineers. How PulsAPI monitoring works

Branch Component Status

The main Branch systems on this page. All 7 are operational right now.

7operational
API
Operational
Dashboard
Operational
Deep Linking
Operational

4 more components tracked

Their status is in the bar above. Free accounts see every component by name.

Also tracking Export API, Journeys, Link Redirection, Webhooks.

See all of them free

Component statuses may change independently during partial outages.

Recent Branch Outages & Incidents

Incident history from the official Branch status page, including resolution updates.

Service Performance IssueResolved Sep 3, 2026 · 1h 56mResolved

This 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 received. Service has been fully restored and events are once again processing normally. --- [2026-09-03T15:51:23.082-07:00] (monitoring) Services are beginning to recover, and events are once again being processed. We'll continue monitoring closely and share an update once full resolution is confirmed. --- [2026-09-03T15:33:15.787-07:00] (investigating) We're investigating a service disruption to attribution processing caused by an AWS service outage, resulting in a brief but significant drop in availability. Impact: Primarily impacting v1/v2 events, starting approximately 2:45–3:00 PM PT today. The issue was identified and responders are actively working it. We'll share an update as we learn more.

Delayed Webhook DeliveryResolved Aug 24, 2026 · 23 minResolved

Maintenance 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. --- [2026-08-24T12:55:22.498-07:00] (identified) We are currently carrying out brief maintenance on our system. During this time, delivery for some webhooks may be temporarily delayed. Impact: Webhook notifications are queued and delayed. No data will be lost, and all events will process automatically. Estimated Resolution: Within the next 10–15 minutes. We apologize for the inconvenience and will post an update as soon as normal processing resumes.

Duplicate Webhook EventsResolved Aug 21, 2026 · 253h 57mResolved

This incident has been resolved. --- [2026-08-20T17:47:44.315-07:00] (monitoring) Between August 19, 2026, 10:40 AM PST and August 20, 2026, 4:55 PM PST, a deployment conflict caused duplicate webhook events to be sent for Installs, Reinstalls, and User Lifecycle Events. Ad Partners saw the highest impact; Data Partners and Dashboard webhook subscribers may also have received duplicates. The issue has been identified and fixed. Impact: Partners who deduplicate events on their end were not affected. Partners who do not deduplicate may have received duplicate postbacks for the affected event types during this window and can deduplicate given event_id. No customer data was lost.

Branch Uptime History

Daily uptime recorded by PulsAPI over the last 90 days, with the days that carried a Branch incident marked. Each day is measured from our own checks, so the record continues even when the vendor publishes nothing.

Uptime history50 days observed
Aug 8100.00% averageSep 26

Live Branch Outage Reports

Problems reported by engineers using Branch. Reports often appear 10 to 20 minutes before the official status page moves, and stay on this page for 90 days.

Reports, last 24 hours0 total
24h agoNothing reportednow

No Branch problems reported yet.

Something wrong with Branch on your end?

Reports are anonymous, take about ten seconds, and help the next engineer who checks.

About Branch

Is Branch down? Branch reports live availability for 7 components at status.branch.io, among them API, Dashboard and Link Redirection. Track Branch outages, degradations and past incidents here, with uptime history and alerts across your SaaS stack.

Over the past 30 days, PulsAPI has measured Branch uptime at 100.00%. Response times, incident history, and SLA tracking for Branch are available on the PulsAPI dashboard.

Branch Status FAQ

Is Branch down right now?

The verdict at the top of this page comes from the latest poll of the official Branch status feed and refreshes automatically, so you are not looking at a stale cached answer. PulsAPI re-checks a vendor every 60 seconds whenever it is not fully operational, or has changed status in the last 30 minutes, so an incident is always on the fastest cadence. Vendors that are stable and rarely watched are re-checked every 5 to 20 minutes instead.

What should I do if Branch is not working?

Check the component list on this page first to see if your failure matches a known outage. If it does, you can report the issue for other engineers, follow the incident timeline for vendor updates, and run any fallback your app supports until Branch recovers.

How do I check Branch uptime history?

PulsAPI tracks Branch uptime over 30, 60, and 90-day rolling windows. The current 30-day uptime is 100.00%. The 90-day uptime strip on this page is public: no account needed. A free account adds alerts whenever Branch changes state, plus 15 days of incident detail; Pro extends that to 90 days and Business to 13 months.

How fast does PulsAPI detect Branch outages?

PulsAPI reads the official Branch status page. PulsAPI re-checks a vendor every 60 seconds whenever it is not fully operational, or has changed status in the last 30 minutes, so an incident is always on the fastest cadence. Vendors that are stable and rarely watched are re-checked every 5 to 20 minutes instead. Alerts reach Slack, Discord, Microsoft Teams, PagerDuty, or email within seconds of detection.

Does PulsAPI track individual Branch components?

Yes. PulsAPI monitors 7 individual Branch components, so you can see which service or region is affected instead of a generic "service degraded" banner.

Can I get alerts when Branch goes down?

Yes. Create a free account and subscribe to Branch: the free plan covers three services with unlimited email alerts and no monthly notification cap. Paid plans lift the monitor limit entirely (Pro and above do not meter how many vendors you watch) and route the same alerts into Slack, Discord, Microsoft Teams, PagerDuty and webhooks.

How do I report an issue with Branch to the community?

Click "Report an issue" at the top of this page, pick the issue type and severity, and optionally add your region and a short note. Reports are anonymous and help other engineers spot Branch problems early. Official status pages often lag real incidents by 10 to 20 minutes.

Is there a free way to monitor Branch?

Yes. The free plan covers 3 monitored services with unlimited email alerts, permanently, so Branch plus two more costs nothing. Every new account also opens with a 30-day Business trial (unlimited monitors, Slack alerts, SLA reporting) with no credit card.

Track Branch with the rest of your stack

2463+ vendors in one dashboard, and an email the moment any of them changes state. Three free, and no monitor limit at all from $29/mo, unlike the alternatives, which keep charging by the monitor.

Start free, 3 services