Fitbit Outage History

Fitbit is up right now

Pingoru has recorded 7 incidents for Fitbit: 7 in the last 12 months and 1 in the last 90 days.

Source: status.healthapp.google.com

7incidents recorded
7last 12 months
1last 90 days
14 daystypical duration

Incidents, newest first

Minor September 1, 2026 Login is not working for all users. 2h 37m Mobile App

Started Sep 01, 2026, 07:00 PM UTC· resolved Sep 01, 2026, 09:37 PM UTC

  1. investigating Sep 01, 2026, 09:15 PM UTC

    We are working on investigating issues with logging into the application.

  2. monitoring Sep 01, 2026, 09:15 PM UTC

    Incident began at 2026-09-01 12:00 (all times are US/Pacific). We are working on investigating issues with logging into the application. Affected products: Mobile App

  3. resolved Sep 02, 2026, 02:09 PM UTC

    We had a brief issue that prevented logging into the app earlier. It has been resolved. Please try again.

  4. resolved Sep 02, 2026, 02:09 PM UTC

    Incident began at 2026-09-01 12:00 and ended at 2026-09-01 14:37 (all times are US/Pacific). We had a brief issue that prevented logging into the app earlier. It has been resolved. Please try again. Affected products: Mobile App

Read the full incident report →

Major July 15, 2026 Sync not working for all users. 6h 40m Device Sync / Pairing

Started Jul 15, 2026, 11:20 AM UTC· resolved Jul 15, 2026, 06:00 PM UTC

  1. investigating Jul 15, 2026, 12:41 PM UTC

    Currently there is an outage affecting the Sync functionality for all Google Health users.

  2. monitoring Jul 15, 2026, 12:41 PM UTC

    Incident began at 2026-07-15 04:20 (all times are US/Pacific). Currently there is an outage affecting the Sync functionality for all Google Health users. Affected products: Device Sync / Pairing

  3. resolved Jul 15, 2026, 02:50 PM UTC

    Health Coach functionality: Ask and Summaries are also impacted.

  4. monitoring Jul 15, 2026, 02:50 PM UTC

    Incident began at 2026-07-15 04:20 (all times are US/Pacific). Health Coach functionality: Ask and Summaries are also impacted. Affected products: Device Sync / Pairing

Read the full incident report →

Minor March 20, 2026 Some users querying web APIs for steps calculated by Pixel Watches may see incorrect values. 95d 4h Web API

Started Mar 20, 2026, 05:13 PM UTC· resolved Jun 23, 2026, 09:42 PM UTC

  1. investigating Mar 20, 2026, 10:26 PM UTC

    We are aware of the issue and working to fully resolve the issue.

  2. 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.

  3. 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

  4. 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

Read the full incident report →

Minor March 9, 2026 Issue affecting SpO2 and Skin Temperature data on some Wear OS devices. 1d 10h Device Sync / Pairing, Mobile App

Started Mar 09, 2026, 08:21 PM UTC· resolved Mar 11, 2026, 06:49 AM UTC

  1. investigating Mar 09, 2026, 10:31 PM UTC

    Some users with Fitbit on Wear OS devices may be unable to access SpO2 and Skin Temperature features due to a recent update. Workaround: Please try adjusting the app permissions on your Wear OS device: Swipe down > Settings ⚙️ > Apps & notifications > App permissions > Fitness and wellness. Ensure both 'Oxygen saturation (Fitbit)' 🩸 and 'Skin temperature (Fitbit)' 🌡️ are set to 'Allow' ✅. We are working to fully resolve the underlying issue and will provide updates here.

  2. resolved Mar 11, 2026, 06:50 AM UTC

    The recent issue with SpO2 and Skin temp data is now resolved. To continue viewing your SpO2 and skin temperature data, please update your app to version 3.55.1.1 or higher. This update ensures you're able to view your metrics moving forward.

Read the full incident report →

Minor December 4, 2025 Food logging is unavailable. 17h 13m Mobile App

Started Dec 04, 2025, 11:54 PM UTC· resolved Dec 05, 2025, 05:07 PM UTC

  1. investigating Dec 05, 2025, 12:09 AM UTC

    We are currently experiencing issues with food logging feature. Our team is investigating the issue and will give an update as soon as possible.

  2. resolved Dec 05, 2025, 05:46 PM UTC

    The issue has been resolved, and the food logging feature is now available.

Read the full incident report →

Minor November 19, 2025 Fitbit most recent data not available in the Fitbit app 1h 40m Device Sync / Pairing

Started Nov 19, 2025, 11:30 AM UTC· resolved Nov 19, 2025, 01:10 PM UTC

  1. resolved Nov 19, 2025, 12:35 PM UTC

    Fitbit newest data is not available in the mobile app. New account creation fails

Read the full incident report →

Minor November 7, 2025 Food search is unavailable. 2h 21m Mobile App

Started Nov 07, 2025, 09:06 PM UTC· resolved Nov 07, 2025, 11:27 PM UTC

  1. investigating Nov 07, 2025, 09:07 PM UTC

    We are currently experiencing issues with the food search feature. Our team is working on a fix. As a workaround, please try logging via your "recent foods" history.

  2. resolved Nov 08, 2025, 12:38 AM UTC

    This incident was mitigated, Food Search is now operating normally.

Read the full incident report →