A Google Health incident disrupted Device Sync / Pairing for all users on July 15, affecting Fitbit and Pixel Watch owners who opened the app to missing statistics, errors or a stalled sync. Google’s status dashboard now marks the incident as resolved, but the useful lesson survives the outage: when a health app stops syncing, do not begin by unpairing the watch or wiping its data. First establish whether the broken link is your phone, your wearable or the service in the middle.
The official incident began at 04:20 Pacific time and was marked resolved at 11:00 Pacific time. Google said that Sync functionality was unavailable for all Google Health users; it later added that Health Coach Ask and Summaries were affected too. 9to5Google reported the outage as it unfolded. That distinction matters: a widespread service incident calls for patience and evidence, not destructive troubleshooting dressed up as enthusiasm.
First, separate an outage from a watch problem
If a normally reliable Fitbit or Pixel Watch suddenly refuses to update, check the provider’s status page before changing any settings. A dashboard entry that names Device Sync / Pairing is strong evidence that the failure is upstream. Wait for the incident to be resolved, then give the app a little time to reconnect before assuming that a local repair is necessary.
Do not treat blank charts as proof that the measurements have vanished. Wearables usually retain a limited amount of recent activity locally, but the exact amount depends on the device, battery state and the data type. The safe posture is conservative: keep the watch charged, keep it paired, and let a restored service attempt the normal catch-up sync.
Quick checks after a sync failure
- Check the Google Health status dashboard. Look specifically for Device Sync / Pairing and note whether the incident is active or resolved. Take a screenshot of any error and its time if your data is important.
- Keep the phone and watch connected. Turn Bluetooth on, keep both devices nearby and make sure neither is in a battery-saving state that blocks background work.
- Open the Fitbit app and allow a normal sync attempt. On Android, use the official Fitbit app on Google Play; avoid third-party “sync fixer” apps that ask for health permissions without solving the underlying outage.
- Update only what is clearly outdated. An app update can be reasonable after the service recovers, but do not use an outage as a reason to install unrelated beta software or factory-reset a working phone.
- Retry once the dashboard is green. Give the service time to process the backlog. Repeatedly force-closing the app is more theatre than repair when the server is still catching up.
Why unpairing is the last resort
Unpairing and resetting a wearable can solve a genuine Bluetooth or account problem, but it also adds a second moving part while the original incident may still be resolving. It can remove locally stored data that has not uploaded yet, force a fresh setup and make it harder to tell what actually fixed the problem. Use that route only after the status page is normal, the app has had time to sync, and the failure persists for your device alone.
If the dashboard is clear but your data still does not appear, check the basics in this order: phone internet connection, Bluetooth pairing, the correct Google account, the Fitbit app’s permissions and available storage on the phone. For broader setup and sensor-permission checks, see AndroidLab’s Pixel Watch health permissions guide.
What changes in practice
The practical change is not a new setting; it is a better troubleshooting order. Health data feels personal enough that a broken chart invites panic, and that is precisely when people reach for a reset. During a confirmed cloud outage, the highest-value action is to preserve the device’s current state, document the error and wait for the service to recover. A reset is a tool for a local fault, not a universal ritual for a server-side one.
In brief
- Google logged a July 15 outage affecting Google Health Device Sync / Pairing for all users, and later marked it resolved.
- Check the official status dashboard before changing pairing, accounts or stored health data.
- Keep the Fitbit or Pixel Watch charged and paired so it can upload retained data after recovery.
- Only consider unpairing or a reset after the service is normal and the fault remains local to your device.
- 9to5Google — Google Health outage breaks device sync for all Fitbit and Pixel Watch users (July 15, 2026, 14:25 UTC)
- Google Health Status Dashboard — Sync not working for all users (incident July 15, 2026; resolved 11:00 Pacific time)