Update - There has been a delay in updating this status page due to there being not a lot of movement to report.
Fitbit is still reporting issues with their WebAPI on their status page https://status.fitbit.com/
We have open communication with Fitbit and are awaiting updates on the issues mentioned on 9/5 on this status page as well as data latency issues which are causing slowness on our end. We can only deliver the data to our clients when the data is received from the vendor API.
We've been told they are working on both the changes in the data sent in their API (9/5 post) as well as the latency issues from the Fitbit API we are experiencing.
This page will be updated when there is additional information to share on the path to resolution.
Sep 13, 2024 - 15:26 EDT
Fitbit is still reporting issues with their WebAPI on their status page https://status.fitbit.com/
We have open communication with Fitbit and are awaiting updates on the issues mentioned on 9/5 on this status page as well as data latency issues which are causing slowness on our end. We can only deliver the data to our clients when the data is received from the vendor API.
We've been told they are working on both the changes in the data sent in their API (9/5 post) as well as the latency issues from the Fitbit API we are experiencing.
This page will be updated when there is additional information to share on the path to resolution.
Sep 13, 2024 - 15:26 EDT
Update - Fitbit is still reporting issues with its web API https://status.fitbit.com/
Sep 09, 2024 - 21:55 EDT
Sep 09, 2024 - 21:55 EDT
Update - We are currently waiting for Fitbit to respond with input from their side regarding the fix we put in and any additional fixes we may need to implement to account for the change in data delivery through their API. We will update when additional information is made available from Fitbit.
Sep 09, 2024 - 10:00 EDT
Sep 09, 2024 - 10:00 EDT
Update - Summary
We are continuing to investigate data inconsistencies originating at Fitbit impacting the data payloads delivered to us through their API for summary and workout endpoints. These changes were first observed late last week and immediately brought to Fitbit’s attention.
Issues Identified
Negative Calorie Values: Some records from Fitbit contain negative calorie values.
Action taken: We are ignoring these negative values.
Impact: Some Validic clients may not receive calorie data in affected records.
Data Type Inconsistencies: Certain metrics are occasionally received as strings instead of numbers.
This issue often correlates with the presence of negative metrics.
Action taken: We are dropping records with unexpected data types.
Additional Data Format Change
A separate issue was identified and addressed regarding a change in Fitbit's data format.
We are actively monitoring this change and are prepared to adjust if Fitbit reverts to the previous format.
Affected Metrics
The following metrics have been observed to be intermittently affected by the above issues:
heart_rate_zone_very_low
heart_rate_zone_low
heart_rate_zone_medium
heart_rate_zone_high
energy_burned
basal_energy_burned
active_energy_burned
Note: Not all records for these metrics are affected. We are only dropping metric values with negative values or unexpected data types. You will receive all normal and expected metric values.
Current Actions
We have escalated both the negative metric values and data type inconsistencies to Fitbit for investigation.
Our team is continuously monitoring the situation and will provide updates as more information becomes available.
Next Steps
We will continue to work closely with Fitbit while they resolve these issues and minimize the impact on our clients. Further updates will be provided as the situation develops.
Sep 05, 2024 - 12:59 EDT
We are continuing to investigate data inconsistencies originating at Fitbit impacting the data payloads delivered to us through their API for summary and workout endpoints. These changes were first observed late last week and immediately brought to Fitbit’s attention.
Issues Identified
Negative Calorie Values: Some records from Fitbit contain negative calorie values.
Action taken: We are ignoring these negative values.
Impact: Some Validic clients may not receive calorie data in affected records.
Data Type Inconsistencies: Certain metrics are occasionally received as strings instead of numbers.
This issue often correlates with the presence of negative metrics.
Action taken: We are dropping records with unexpected data types.
Additional Data Format Change
A separate issue was identified and addressed regarding a change in Fitbit's data format.
We are actively monitoring this change and are prepared to adjust if Fitbit reverts to the previous format.
Affected Metrics
The following metrics have been observed to be intermittently affected by the above issues:
heart_rate_zone_very_low
heart_rate_zone_low
heart_rate_zone_medium
heart_rate_zone_high
energy_burned
basal_energy_burned
active_energy_burned
Note: Not all records for these metrics are affected. We are only dropping metric values with negative values or unexpected data types. You will receive all normal and expected metric values.
Current Actions
We have escalated both the negative metric values and data type inconsistencies to Fitbit for investigation.
Our team is continuously monitoring the situation and will provide updates as more information becomes available.
Next Steps
We will continue to work closely with Fitbit while they resolve these issues and minimize the impact on our clients. Further updates will be provided as the situation develops.
Sep 05, 2024 - 12:59 EDT
Monitoring - A fix has been deployed to account for changes made by Fitbit. Data is flowing successfully. We are monitoring to ensure the fix resolves the issues encountered with the integration.
Sep 04, 2024 - 23:12 EDT
Sep 04, 2024 - 23:12 EDT
Update - We are continuing to work on a fix for this issue.
Sep 04, 2024 - 14:16 EDT
Sep 04, 2024 - 14:16 EDT
Identified - We have identified the issue and a fix is being groomed. I'll update this page when that solution is released to account for the change from the Fitbit end.
Sep 04, 2024 - 08:40 EDT
Sep 04, 2024 - 08:40 EDT
Investigating - Validic is investigating possible issues with the delivery of data from Fitbit.
As a result, you may see delays in receiving user data from Fitbit users and users may see issues when trying to sync to Fitbit.
We will provide updates here when they are available.
Sep 04, 2024 - 00:12 EDT
As a result, you may see delays in receiving user data from Fitbit users and users may see issues when trying to sync to Fitbit.
We will provide updates here when they are available.
Sep 04, 2024 - 00:12 EDT
Update - The Validic team is still waiting for updates from the Bewell team on this issue.
Jul 02, 2024 - 09:21 EDT
Jul 02, 2024 - 09:21 EDT
Investigating - Validic is currently investigating an issue where users are seeing errors when trying to authorize Bewell Connect via the Validic marketplace.
We will provide updates here when they are available.
Jun 24, 2024 - 13:10 EDT
We will provide updates here when they are available.
Jun 24, 2024 - 13:10 EDT
About This Site
We continuously monitor the status of the Validic Inform APIs and all its related services. If there are any interruptions in service, a note will be posted here. If you are experiencing problems connecting to Validic and do not see a notice posted here, please visit support.validic.com to review our knowledge base articles for quick troubleshooting support. If your issue is not addressed there, please email support@validic.com with your company name, organization ID and user ID for the user experiencing issues, if necessary, and any other supporting information that may help expedite the resolution of your support request.
For Validic V1 API status, visit http://status.validic.com
REST API
Operational
Streaming API
Operational
Marketplace
Operational
Fitbit
Degraded Performance
Foracare
Operational
Garmin Connect
Operational
Higi
Operational
iHealth
Operational
Lose It!
Operational
Withings
Operational
Omron
Operational
Polar
Operational
Runkeeper
Operational
Strava
Operational
Suunto
Operational
Under Armour
Operational
Validic Mobile
Operational
Support Portal
Operational
MyFitnessPal
Operational
Sisense Reporting
Operational
LifeScan/OneTouch
Operational
YOO
Operational
Emfit
Operational
Daily Burn
Operational
Omron Japan
Operational
Dexcom
Operational
Qardio
Operational
Google Fit Mobile SDK
Operational
Quicksite
?
Operational
API Documentation
Operational
Bewell Connect
Degraded Performance
Operational
Degraded Performance
Partial Outage
Major Outage
Maintenance