Is Branch down?
Last checked 2m agoNo incidents right now.
Branch is operational right now. Last checked 2m ago; the most recent incident resolved 1d ago.
Real-time Branch status, recent outages, and incident history: pulled directly from Branch's official status page at status.branch.io every 5 minutes. Pingoru tracks 7 Branch services and has captured 4 incidents in the last 90 days (99.84% uptime). Get email, Slack, Discord, or webhook alerts the moment Branch reports a new incident, free for 3 monitors, no credit card.
Recent outages & incidents
Past 90 days- Export API
Timeline · 2 updates
- identified · Oct 26, 2026, 09:32 AM UTC
We are currently investigating an issue with the processing of Custom Exports API jobs generated between 05:14 UTC and 08:45 UTC. Please note that processing resumed at 08:45 UTC, and all affected export jobs are being reprocessed automatically but currently delayed due to the accumulated backlog. We are actively working through the backlog and to identify the root cause and will provide further updates as more information becomes available.
- resolved · Oct 26, 2026, 11:09 AM UTC
We are now seeing successful completion of the previously delayed jobs and all current exports are processing without any delays.
Latest: We are now seeing successful completion of the previously delayed jobs and all current exports are processing without any delays.
-
-
Timeline · 3 updates
- investigating · Sep 03, 2026, 10:33 PM UTC
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.
- monitoring · Sep 03, 2026, 10:51 PM UTC
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.
- resolved · Sep 04, 2026, 12:30 AM UTC
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.
Latest: 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…
-
-
Timeline · 2 updates
- identified · Aug 24, 2026, 07:55 PM UTC
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.
- resolved · Aug 24, 2026, 08:18 PM UTC
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.
Latest: 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 delivere…
-
-
Timeline · 2 updates
- monitoring · Aug 21, 2026, 12:47 AM UTC
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.
- resolved · Aug 31, 2026, 02:44 PM UTC
This incident has been resolved.
Latest: This incident has been resolved.
-
Incident record
Since April 2026 · Statuspage by Atlassian · 7 components checked every 5 minutesThe longest incident in the last year, Duplicate Webhook Events on August 21, 2026, ran for 11 days. 3 maintenance windows announced in the same period.
Most affected components, last 12 months
- Export API3
- Webhooks2
- API1
- Dashboard1
Latest incidents
- Custom Exports API – Processing Delay
We are currently investigating an issue with the processing of Custom Exports API jobs generated between 05:14 UTC and 08:45 UTC. Please note that processing…
- Service Performance Issue
We're investigating a service disruption to attribution processing caused by an AWS service outage, resulting in a brief but significant drop in availability.…
- Delayed Webhook Delivery
We are currently carrying out brief maintenance on our system. During this time, delivery for some webhooks may be temporarily delayed. Impact: Webhook…
- Started Oct 26, 2026, 09:32 AM UTC · Resolved Oct 26, 2026, 11:09 AM UTC · 1h 37m
- Service Performance Issue ResolvedStarted Sep 03, 2026, 10:33 PM UTC · Resolved Sep 04, 2026, 12:30 AM UTC · 1h 56m
- Delayed Webhook Delivery ResolvedStarted Aug 24, 2026, 07:55 PM UTC · Resolved Aug 24, 2026, 08:18 PM UTC · 23m
- Duplicate Webhook Events ResolvedStarted Aug 21, 2026, 12:47 AM UTC · Resolved Aug 31, 2026, 02:44 PM UTC · 10d 13h