Last checked
Branch status
Deep linking for mobile apps.
Experiencing an issue?
Branch宕机了吗？
Degraded performance
Source: official status page
Having issues with Branch?
Share your experience to help others stay informed.
Branch service health graph
Service status and report activity over the last 24 hours, in 15-minute intervals. Early warnings and official incidents are shown separately.
Branch activity
Loading reports… · Last 24 hours
Download
- No problems detected
- Possible problems
- Problems detected
- Early warning
- Official incident
Tap a bar to keep its details open. With the chart focused, use Left and Right to move between intervals, Home or End to jump, and Escape to close. Full data is available in the table below.
View chart data
| Start | End | Reports | Status |
|---|
Latest activity
Last 24 hoursOfficial status checked
Branch is experiencing issues
Official provider statusOfficial incident active
Duplicate Webhook Events — 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.
Official provider status
Branch outage reports
0 outage reports in the last 24 hours.
Branch 中断地图
Approved reports from the last 24 hours, grouped by country. Markers show country-level locations, not precise locations or confirmed affected infrastructure.Branch 中断地图
Loading report locations…
Branch status history
Official status observations, not measured service uptime.
Last 60 daysDaily history
Loading history…
- 正常
- 问题
- 中断
- 维护
- 无数据
Branch components
Branch incident history
Official incidents, early warnings and community reports are identified separately. Early warning history covers only the last 24 hours. Dates use your time zone.
| Incident name | Duration | StartedUTC | Acknowledged | Severity |
|---|---|---|---|---|
| 435h 58mOngoing | Yes | Unknown | ||
| 6h 4m | Yes | Unknown | ||
| 138h 58m | Yes | Minor | ||
| 11h 57m | Yes | Minor | ||
| 2h 11m | Yes | Unknown | ||
| 2h 46m | Yes | Unknown | ||
| 0m | Yes | Unknown | ||
| 48m | Yes | Minor |
社区讨论
分享您对 Branch 的看法
还没有评论
成为第一个评论的人！
关于 Uptimus 对 Branch 的监控
Uptimus 通过官方状态源监控 Branch，并将事件、维护和组件健康状况统一为一致的服务状态。
此页面目前包含 7 个受监控组件、52 个事件、24 个维护窗口和 6 天已知历史。
Uptimus 是独立监控服务，与 Branch 无关联。健康状态并不保证每位用户、设备或地区都未受影响。
Uptimus 如何监控 Branch
当 Branch 或受监控组件报告重大或关键中断时接收通知。 提醒可通过工作区启用的渠道发送，包括电子邮件、推送和已配置的集成。 可用历史包含 52 个事件，为提醒提供当前状态之外的背景。 最近收录的事件是“Duplicate Webhook Events”。
接收有关性能下降、部分影响和非完全中断的小型事件通知。 Uptimus 当前跟踪 Branch 的 7 个组件: API, Dashboard, Link Redirection, Deep Linking。 提醒可通过工作区启用的渠道发送，包括电子邮件、推送和已配置的集成。
维护通知
当 Branch 发布计划、预定或正在进行的维护时接收通知。 Uptimus 已从 Branch 的可用历史中收录 24 个维护窗口。 提醒可通过工作区启用的渠道发送，包括电子邮件、推送和已配置的集成。
