Last checked
Branch status
Deep linking for mobile apps.
Experiencing an issue?
Branch è down?
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.
Mappa dei disservizi di Branch
Approved reports from the last 24 hours, grouped by country. Markers show country-level locations, not precise locations or confirmed affected infrastructure.Mappa dei disservizi di Branch
Loading report locations…
Branch status history
Official status observations, not measured service uptime.
Last 60 daysDaily history
Loading history…
- Operativo
- Problemi
- Interruzione
- Manutenzione
- Nessun dato
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 |
|---|---|---|---|---|
| 438h 40mOngoing | 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 |
Discussione comunitaria
Condividi i tuoi pensieri su Branch
Nessun commento ancora
Sii il primo a commentare!
Informazioni sul monitoraggio di Branch su Uptimus
Uptimus monitora Branch tramite la fonte ufficiale e normalizza incidenti, manutenzioni e componenti in uno stato coerente.
Questa pagina include attualmente 7 componenti monitorati, 52 incidenti, 24 manutenzioni e 6 giorni di storico noto.
Uptimus è un servizio indipendente e non è affiliato a Branch. Uno stato regolare non garantisce che ogni utente, dispositivo o area sia esente da problemi.
Come Uptimus monitora Branch
Ricevi un avviso quando Branch o un componente monitorato segnala un'interruzione grave o critica. Gli avvisi possono essere inviati tramite i canali attivi nel workspace, inclusi email, push e integrazioni configurate. La cronologia disponibile contiene 52 incidenti indicizzati e offre un contesto oltre lo stato attuale. Un incidente recente indicizzato è stato «Duplicate Webhook Events».
Ricevi avvisi su prestazioni degradate, impatto parziale e incidenti che non rappresentano un'interruzione completa. Uptimus monitora attualmente 7 componenti di Branch: API, Dashboard, Link Redirection, Deep Linking. Gli avvisi possono essere inviati tramite i canali attivi nel workspace, inclusi email, push e integrazioni configurate.
