Fitbit incident
Some users querying web APIs for steps calculated by Pixel Watches may see incorrect values.
Fitbit experienced a minor incident on March 20, 2026 affecting Web API, lasting 95d 4h. The incident has been resolved; the full update timeline is below.
Affected components
Update timeline
- investigating Mar 20, 2026, 10:26 PM UTC
We are aware of the issue and working to fully resolve the issue.
- resolved Mar 23, 2026, 09:42 PM UTC
We’ve fixed the issue where some Pixel Watch users were seeing overcounted steps and calories. Please be aware that previously recorded data will remain unchanged, as this update applies to new activity only. If you’re still experiencing this issue, please restart your Pixel Watch. For more information, please visit https://support.google.com/googlepixelwatch/answer/13575675.
- resolved Mar 23, 2026, 09:43 PM UTC
Incident began at 2026-03-20 10:13 and ended at 2026-06-23 14:42 (all times are US/Pacific ). We’ve fixed the issue where some Pixel Watch users were seeing overcounted steps and calories. Please be aware that previously recorded data will remain unchanged, as this update applies to new activity only. If you’re still experiencing this issue, please restart your Pixel Watch. For more information, please visit https://support.google.com/googlepixelwatch/answer/13575675 . Affected products: Web API
- resolved Mar 23, 2026, 09:43 PM UTC
Incident began at 2026-03-20 10:13 and ended at 2026-06-23 14:42 (all times are US/Pacific ). We’ve fixed the issue where some Pixel Watch users were seeing overcounted steps and calories. Please be aware that previously recorded data will remain unchanged, as this update applies to new activity only. If you’re still experiencing this issue, please restart your Pixel Watch. For more information, please visit https://support.google.com/googlepixelwatch/answer/13575675 . Affected products: Web API