Last checked
Branch status
Deep linking for mobile apps.
Experiencing an issue?
¿Branch no funciona?
Degraded performance
The current official status of Branch cannot be verified. The latest stored provider observation indicated normal operation. 0 reports were recorded for Branch in the last 24 hours. Last official check: .
Source: official status pageHaving 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.
Mapa de Interrupciones
Approved reports from the last 24 hours, grouped by country. Markers show country-level locations, not precise locations or confirmed affected infrastructure.Mapa de Interrupciones
Loading report locations…
Branch status history
Official status observations, not measured service uptime.
Last 60 daysDaily history
Loading history…
- Operativo
- Problemas
- Interrupción
- Mantenimiento
- Sin datos
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 52mOngoing | 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 |
Discusión de la Comunidad
Comparte tus pensamientos sobre Branch
Aún no hay comentarios
¡Sé el primero en comentar!
Acerca de la supervisión de Branch en Uptimus
Uptimus supervisa Branch mediante su fuente oficial y normaliza incidencias, mantenimiento y componentes en un estado coherente.
Esta página incluye actualmente 7 componentes supervisados, 52 incidencias, 24 mantenimientos y 6 días de historial conocido.
Uptimus es un servicio independiente y no está afiliado con Branch. Un estado saludable no garantiza que todos los usuarios, dispositivos o regiones estén libres de problemas.
Cómo supervisa Uptimus Branch
Recibe alertas cuando Branch o uno de sus componentes supervisados informa de una interrupción grave o crítica. Las alertas pueden enviarse por los canales activados en el espacio de trabajo, incluidos correo, push e integraciones configuradas. El historial disponible contiene 52 incidencias indexadas y aporta contexto más allá del estado actual. Una incidencia reciente indexada fue «Duplicate Webhook Events».
Recibe alertas sobre rendimiento degradado, impacto parcial e incidencias que no representan una interrupción completa. Uptimus supervisa actualmente 7 componentes de Branch: API, Dashboard, Link Redirection, Deep Linking. Las alertas pueden enviarse por los canales activados en el espacio de trabajo, incluidos correo, push e integraciones configuradas.
