Home
/
Status
/
Service
Deep linking for mobile apps.
Source
auto
Category
Analytics
Adapter
STATUSPAGE IO
Verified
Pending review
Current state
Operational
Checked 6m ago
7
Components
0
Active incidents
1
Maintenance
50%
90d uptime
Services Degraded: X API Platform Impacting X (formerly Twitter) Attributions
Mar 26, 3:45 AM
Normalized official status-page data for incidents, maintenance, components, and history.
50%
Known uptime
2 known history days
7
Components tracked
0 outage, 0 degraded
50
Incidents indexed
0 active right now
23
Maintenance windows
1 active or scheduled
Components with the most recent status-page events.
API
Operational
Dashboard
Operational
Deep Linking
Operational
Export API
Operational
Journeys
Operational
Component changes, incidents, and maintenance windows grouped by day.
operational
degraded
outage
maintenance
unknown
1
operational days
0
degraded days
1
outage days
0
maintenance days
88
unknown days
Latest outages and degradations detected from the official status page.
We have confirmed that X’s API Service success rates have returned to normal. We will continue to monitor.
The identified issue has been resolved, and services are now restored. You should see the dashboard features available again.
Latency has now returned to normal.
Between 3:00 PM and 3:25 PM PST, we experienced a period of service instability that affected Deeplinking and App opens. During this window users may have encountered errors or slower response times. Our team identified this was the result of configuration error during a routine system update. We immediately reverted the change and all services returned to normal operation by 3:25 PM PST. We are currently monitoring our systems and verifying that all delayed data has been processed correctly.
We have identified the issue, deployed a fix, and restarted the affected jobs. We are now seeing successful completion of jobs and these will be processed in the next few hours.
Our team has now pushed a fix to resolve the issue. We are assessing impact and will follow up with more details.
We are once again seeing successful requests
Meta has resolved the issues affecting Facebook login, as confirmed on their status page (https://metastatus.com/facebook-login). Branch attempted to re-establish connections for all accounts, and most were successful. If your Facebook Ad Partner authentication token remains invalid, please manually re-authenticate your account within the Branch platform here: https://dashboard.branch.io/ads/partner-management/a_facebook?tab=settings
We have identified an issue impacting post install event SKAN attributions. As a result SKAN attributions may have been missed for conversion events starting July 31st. The root cause was addressed and resolved as of August 7th at 5:12 PM PDT. We will continue monitoring.
As of 08:36 PM Pacific Time, we have restored the Journey services. You should now be able to create and clone Journeys successfully.
Scheduled and completed maintenance windows are separated from incidents.
As part of our ongoing efforts to continually upgrade our infrastructure to provide the best experience, the servers used by Branch to pull data from websites will soon change. This is a service that scrapes a url to pull link data and social preview information when creating a Branch link. Please work with your Web Development team to ensure your allowlist is updated by June 30th to include the new additional IPs to avoid possible disruption. If the update is not completed before June 30, you may see warnings when creating links in the Branch Dashboard, and links generated via API may not automatically populate scraped link data fields. For additional details please refer to the help documentation: https://help.branch.io/developer-hub/docs/web-advanced-features#include-deep-link-data-in-html
The scheduled maintenance has been completed.
The scheduled maintenance has been completed.
The scheduled maintenance has been completed.
The scheduled maintenance has been completed.
The scheduled maintenance has been completed.
The scheduled maintenance has been completed.
The scheduled maintenance has been completed.
The scheduled maintenance has been completed.
The scheduled maintenance has been completed.
Uptimus tracks the official Branch status page, normalizes upstream events, and separates incidents from scheduled maintenance.
Official source
https://status.branch.io
Adapter
STATUSPAGE IO
Alert streams
Incidents, component changes, and maintenance windows.
Public SEO page
Indexable status history for users searching outage information.
Regional reports can be layered on top of official provider status when user signals are available.
Showing 1 to 7 of 7 tracked components.
| Component | Status | Type | Last changed |
|---|---|---|---|
API | Operational | Component | Not recorded |
Dashboard | Operational | Component | Not recorded |
Link Redirection | Operational | Component | Not recorded |
Deep Linking | Operational | Component | Not recorded |
Export API | Operational | Component | Not recorded |
Webhooks | Operational | Component | Not recorded |
Journeys | Operational | Component | Not recorded |
Follow outages, degraded components, and maintenance updates in your Uptimus workspace with email, push, and webhook alerts.
Official provider components
Incident and maintenance separation
Workspace alerts and webhooks
Related status pages based on category, adapter type, and operational history.
Branch is currently marked as Operational in Uptimus based on the latest official status page check.
Supported status page providers are checked continuously by our scraper scheduler. The public page is cached briefly for SEO and performance.
No. Uptimus stores incidents and maintenance windows separately when the upstream provider exposes enough detail.
Yes. Create an Uptimus workspace, follow this provider, and choose email, push, or webhook notifications.
