Is Validic V1 Down Right Now? Check if there is a current outage ongoing.

Google is currently experiencing issue with their authentication services. This can affect any service that uses Google authorization for users to log in, including Fitbit. This is not a Validic issue. Validic will monitor this issue and provide updates here as they are available. Google is tracking this issue here:
https://status.cloud.google.com/regional/americas

This incident has been resolved.

Fitbit has reported that this issue is resolved. Validic will continue to monitor as we do see data flow gradually returning to normal.

Fitbit has confirmed that they are reporting a service outage via their status page. Validic will continue to monitor. https://status.fitbit.com/

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.

This incident has been resolved.

iHealth data flow appears to be returning to more normal levels. The iHealth authorization page also has been loading as expected and users have been able to connect their iHealth accounts via the Validic Marketplace. We will continue to monitor for stability.

Validic is currently investigating an issue where users are seeing an error when trying to navigate to the iHealth authorization page via the Validic marketplace. We are also investigating possible delays in the delivery of data from iHealth. As a result, users will not be able to connect to iHealth and you may see delays in receiving data from connected iHealth users. We will update this post as new information is available.

Fitbit has communicated to us that they have resolved all open issues around their application and their API syncing. We are resolving this status page and appreciate everyone's patience with this. It has been challenging as there were things out of our control with changes to the Fitbit API and Fitbit issues that required their attention. If you encounter scenarios where you see a cloud-connected Fitbit user seeing different things in what is showing in the user's Fitbit application and what is in the Validic API, Validic technical support is here to assist. We do request that you do the following before writing in though. 1. Work through the steps on this page with the affected user: https://help.validic.com/space/VCS/3480453131/How+to+troubleshoot+Inform+issues 2. If working through those steps doesn't resolve the issue then open a ticket with our team and share the troubleshooting steps you have taken along with screenshots of the user's Fitbit application that shows a difference in what is in the Inform API. Don't forget to share the Validic ID and Org ID. Validic technical support will need that information to fully investigate the scenario for the user.

As of late August 2024, Fitbit has adjusted their algorithm for calculating metrics such as calories burned, distance, and times in heart rate zones. These changes may result in metric values that are much higher or lower than anticipated. Usually, these sorts of values can be explained by the personal information the user has stored in their Fitbit user profile. Why are calories burned, distance, and/or time in heart rate zones values different than I expect? Fitbit devices estimate your users’ calories burned by combining their basal metabolic rate (BMR) with their activity data. BMR is calculated using the Fitbit profile information, including height, weight, sex, and age. It's important to have users make sure that this information is entered accurately in their Fitbit account, as it significantly impacts the calorie calculations. If their device tracks heart rate, this data is also incorporated, especially when estimating calories burned during exercise. To ensure the most accurate calorie burn, distance, and time in heart rate zone estimations: 1. Have the user verify and update their Fitbit profile: Confirm that their height, weight, sex, and age are correct in their Fitbit account settings. See https://support.google.com/fitbit/answer/14236616?sjid=16936490723788951099-NA 2. Utilize the Exercise app: For activities like spinning or yoga where step count might not accurately reflect intensity, the user should consider using the Exercise app on their Fitbit device to track workouts and capture real-time heart rate data. 3. Consider GPS tracking: If the user frequently engages in activities where their arm movement is restricted, such as pushing a stroller or holding a dog leash, using GPS tracking can improve distance and calorie burn calculations. If users continue to have trouble tracking these metrics, please have them reach out to the Fitbit community for assistance: https://community.fitbit.com/t5/Community/ct-p/EN

This incident has been resolved.

Page loads are returning to the expected behavior in the Validic Support Portal. We will monitor for stability.

Validic is currently investigating a possible issue where pages in the Support Portal at https://help.validic.com may not be loading for some users. We will provide updates here as they are available.

This incident has been resolved.

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. At this time, the queue is catching up, but there still may be slight delays in the delivery of Fitbit data.

This incident has been resolved.

Validic is still investigating possible solutions to the Polar authorization issues. We will update this status as more information becomes available.

Validic is investigating a possible issue where users may experience errors when attempting to authorize Polar in the Validic marketplace. As a result, some users may not be able to successfully connect to Polar. We will provide updates here as they are available.

Fitbit data continues to flow as expected. This issue is resolved.

Fitbit data is again flowing as expected. We will continue to monitor for stability.

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.

Strava data and user connections have been consistent and as-expected since this change so we will close this status page. If you do happen to see any issues with Strava users or data please contact the Validic Support Team via https://help.validic.com

As part of the transition to this new developer program, Strava set the number of allowed athletes to a high number for all Validic developer accounts. We have discovered that some Validic orgs were not set to a high enough number to allow the addition of new Strava users. Validic is working directly with Strava to resolve this.

Recently, Strava announced that they would be launching a new Developer Program for all users of their API data. Their planned cutover to that new program is March 4, 2024. Validic has been aware of this change and has been working closely with Strava to update all Validic developer credentials in an effort to have a seamless transition. There is no action for you or your Strava users. No interruption of data delivery is expected. This status page is simply to inform you that this change will be happening behind the scenes. Should you see any issues with user connections or data flow with Strava after March 4, 2024, please contact the Validic Support Team via https://help.validic.com

This issue if fully resolved.

The Fitbit integration appears to be functioning as designed at this point. We're monitoring the situation to ensure it is completely resolved.

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.

Earlier today there was a delay in processing Validic API data for approximately 30 minutes. Data processing has since caught up and yo should not be missing any data.

Fitbit has resolved this issue.

Fitbit has reported that users who have connected their Fitbit accounts via Google may not be able to log in or see their Fitbit data when logged in. As a result, you may not see some Fitbit user data in the Validic API while Fitbit works to resolve this issue. Validic will continue to monitor this and provide updates here when they are available.

This incident has been resolved.

OneTouch data is starting to flow as expected. Validic will continue to monitor.

This issue appears to be related to a widespread AWS issue. We are continuing to monitor.

Validic is investigating possible issues with the delivery of data from OneTouch. As a result, you may see delays in receiving user data from OneTouch users and users may see issues when trying to sync to OneTouch. We will provide updates here when they are available.

This incident has been resolved.

MyFitnessPal data is starting to flow as expected. Validic will continue to monitor.

Validic is investigating possible issues with the delivery of data from MyFitnessPal. As a result, you may see delays in receiving user data from MyFitnessPal users and users may see issues when trying to sync to MyFitnessPal. We will provide updates here when they are available.

This incident has been resolved.

Fitbit data is starting to flow as expected. Validic will continue to monitor.

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.

Fitbit has reported that this issue is resolved. Details can be found here: https://www.fitbitstatus.com/incidents/5p02cq0yd4pf

Correction: Fitbit is still investigating this issue and Validic will continue to monitor.

Fitbit has implemented a fix to this issue. We will continue to monitor.

Fitbit has reported that users who have connected their Fitbit accounts via Google may not have their data available in the Fitbit public API. As a result, you may not see some Fitbit user data in the Validic API while Fitbit works to resolve this issue. Validic will continue to monitor this and provide updates here when they are available.

This incident has been resolved.

OneTouch data has been flowing as expected. Validic will continue to monitor for stability.

Validic is investigating possible issues with the delivery of data from OneTouch. As a result, you may see delays in receiving user data from OneTouch users and users may see issues when trying to sync to OneTouch. We will provide updates here when they are available.

This incident has been resolved.

Omron data appears to be flowing as expected. We will continue to monitor for stability.

Validic is investigating possible delays in the delivery of data from Omron. As a result, you may see delays in receiving user data from Omron users and users may see issues when trying to sync to Omron. We will provide updates here when they are available.

This incident has been resolved.

Validic is investigating possible issues with the delivery of data from Runkeeper. As a result, you may see delays in receiving user data from Runkeeper users and users may see issues when trying to sync to Runkeeper. We will provide updates here when they are available.

The backfill data completely cleared our queue and everything is back to normal with the data flow for Garmin. We're resolving this issue

Garmin has confirmed they have completed the data sync from 4/3 until we put the fix in. They completed it quicker than they thought initially. We are monitoring to verify all is well, but it appears we are close to resolved here.

Garmin has confirmed that all data from 4/3/23 forward have been sent and are now available in the Validic API. Validic will continue to monitor for a period of time to make sure all is as expected.

Garmin has started the process to push through the data that was missed due to this change. This process is expected to take several days to be completed. We will continue to monitor and provide updates here.

The Validic product team is in communication with Garmin to have them push the data from when Garmin made the change until we put the fix in. Exact ETA on when Garmin will run this request isn't available now. We'll update this status when we are given details from the Garmin team.

Data is flowing successfully from when the fix was put in until now. There is some missing data from when Garmin made the change and we made the adjustment on our side to account for that change. This status page will be updated when there is an update on the status of recovering that lost data

There was a change on the Garmin end that caused this data delay. Validic deployed a fix this morning and we are monitoring it. Initial tests show data is flowing. There will be a delay for data from 4/3 to the present to be available in our database.

Validic is investigating possible issues with the delivery of data from Garmin. As a result, you may see delays in receiving user data from Garmin users and users may see issues when trying to sync to Garmin. We will provide updates here when they are available.

The issue for these data sources has been fully resolved. There wasn't any data loss here. The sources were queuing successfully, but the process fell behind.

The Withings data has caught up. This will be monitored overnight and accessed in the morning. There will be an update then

A fix was implemented earlier in the day and we have been monitoring the data coming through our queues. At this time only Withings still has a backlog in the queue. The rest of the sources have caught up with data.

Additional investigation has added more affected sources. Investigation continues, but a path to resolution is being worked on. MyFitnessPal Garmin Misfit Withings Strava Polar Tomtom UA

Validic is investigating a potential issue that prevented our Legacy API (v1) from collecting data from certain data sources. It appears that Strava, My Fitness Pal, and Polar are affected. Updates will be made available as we learn more about this.

This incident has been resolved.

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.

Fitbit has resolved this issue and all is working as expected.

Fitbit is reporting that they are no longer seeing a spike in errors with the API. Validic will continue to monitor.

Fitbit is currently reporting a higher than expected rate of errors with their API at this time and are investigating the issue. 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.

iHealth has implemented a fix and this issue is resolved.

iHealth is actively working on a fix to this issue.

We've reached out to our iHealth contacts for assistance in resolving this. The issue appears intermittent. iHealth is investigating

Some users are currently reporting errors when trying to connect to iHealth via the Validic Marketplace. Validic is investigating this issue and will provide updates here as they become available.

Withings authorization endpoints are working as expected.

Withings has implemented a fix to the OAuth2 issue. Validic will continue to monitor.

Withings is currently reporting that some users are seeing errors with their OAuth2 authorization endpoints, which are used to grant access to user data via their API. As a result, some users may not be able to sync their Withings users to Validic. We will provide updates here when they are available.

This incident has been resolved.

We are still seeing periodic delays in the receipt of Under Armour data and are working with their team to try to identify the cause.

The issue appears to be resolved. We're monitoring this now to ensure stability of the data delivery.

Validic is investigating possible issues with the delivery of data from Under Armour. As a result, you may see delays in receiving user data from Under Armour users and users may see issues when trying to sync to Under Armour. We will provide updates here when they are available.

Fitbit is reporting that all services are operational.

Fitbit has implemented a fix to this issue. Validic will continue to monitor the status.

Fitbit is expecting the issue to be resolved in the next 3-4 hours.

Update: Fitbit is tracking this issue with updates found here: https://www.fitbitstatus.com/incidents/vzg84qtm6btl

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.

The data has caught up. This incident is resolved.

The system appears to be recovering well. We're monitoring

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.

This issue has been resolved

Garmin data delivery has returned to normal. Validic will continue to monitor.

Validic is investigating possible delays in the delivery of data from Garmin. As a result, you may see delays in receiving user data from Garmin users and users may see issues when trying to sync to Garmin. We will provide updates here when they are available.

MyFitnessPal reports that this issue is resolved.

MyFitnessPal reports that they have implemented a fix to the login issue. Validic will continue to monitor.

MyFitnessPal is reporting that some users are not able to log in via the web, mobile, or API products. As a result, new users may not be able to connect their MyFitnessPal user via the Validic Marketplace. We will provide updates here when they are available.

This incident has been resolved.

The issue appears to be resolved. We're monitoring this now to ensure stability of the data delivery.

Validic is investigating possible issues with the delivery of data from Withings. As a result, you may see delays in receiving user data from Withings users and users may see issues when trying to sync to Withings. We will provide updates here when they are available.

This incident has been resolved.

Syncing to Polar via the Validic Marketplace is working as expected. Validic will continue to monitor.

The Polar team has confirmed reports of this issue and are currently investigating.

Some users are currently reporting errors when trying to connect to Polar via the Validic Marketplace. Validic is investigating this issue and will provide updates here as they become available.

Things are back to normal. The issue is resolved

The issues appear to have been resolved on the Withings side. We're monitoring this.

Validic is investigating possible issues with the delivery of data from Withings. As a result, you may see delays in receiving user data from Withings users and users may see issues when trying to sync to Withings. We will provide updates here when they are available.

MyFitnessPal has resolved this issue.

MyFitnessPal is currently investigating elevated error rates on all of their services. As a result, you may see delays in receiving user data from MyFitnessPal users and users may see issues when trying to sync to MyFitnessPal. We will provide updates here when they are available.

iHealth user authorization is continuing to work as expected.

iHealth has implemented a fix and the authorization process for users is working as expected. Validic will continue to monitor.

The iHealth technical team is assisting with this investigation. Validic will continue to provide updates here as they are available.

Users are currently reporting unexpected slowness and timeout errors when trying to sync to iHealth via the Validic Marketplace. Validic is investigating this issue and will provide updates here as they become available.

Omron data has been flowing consistently.

Omron data appears to be flowing as expected again. We will continue to monitor.

Validic is investigating possible delays in the delivery of data from Omron. As a result, you may see delays in receiving user data from Omron users and users may see issues when trying to sync to Omron. We will provide updates here when they are available.

This incident has been resolved.

The data for Fitbit has caught up. This issue is resolved

We are continuing to monitor for any further issues.

Fitbit has identified the issue and are implementing a fix.

We are continuing to investigate this issue.

Fitbit has confirmed the issue and are reporting "Widespread outage of Fitbit services which interact with user data" which affects the Fitbit API. Validic will continue to monitor for updates from Fitbit.

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.

The incident is resolved

Validic is investigating possible issues with the delivery of data from Strava As a result, you may see delays in receiving user data from Strava users and users may see issues when trying to sync to Strava. We will provide updates here when they are available.

MyFitnessPal database maintenance is complete.

MyFitnessPal is currently running some database maintenance that could be affecting the ability of users to sync their data as well as the delivery of user data via their API. As a result, you may see delays in receiving user data from MyFitnessPal users and users may see issues when trying to sync to MyFitnessPal. We will provide updates here when they are available.

Omron data has been flowing consistently.

Omron data appears to be flowing as expected again. We will continue to monitor.

Validic is investigating possible issues with the delivery of data from Omron. As a result, you may see delays in receiving user data from Omron users and users may see issues when trying to sync to Omron. We will provide updates here when they are available.

Omron data has been flowing consistently.

Omron data appears to be flowing as expected again. We will continue to monitor.

New users can't be enrolled due to calls to Omron failing with a 504 message.

Validic is investigating possible issues with the delivery of data from Omron. As a result, you may see delays in receiving user data from Omron users and users may see issues when trying to sync to Omron. We will provide updates here when they are available.

Under Armour data continues to flow as expected.

Under Armour data has started to flow again. Validic will continue to monitor.

Validic is investigating possible issues with the delivery of data from Under Armour. As a result, you may see delays in receiving user data from Under Armour users and users may see issues when trying to sync to Under Armour. We will provide updates here when they are available.

Garmin data delivery has returned to expected levels.

The integration has stabilized and we are monitoring the situation.

Validic is investigating possible delays in the delivery of data from Garmin. As a result, you may see delays in receiving user data from Garmin users and users may see issues when trying to sync to Garmin. We will provide updates here when they are available.

Omron data delivery has returned to normal.

Validic is investigating possible delays in the delivery of data from Omron. As a result, you may see delays in receiving user data from Omron users and users may see issues when trying to sync to Omron. We will provide updates here when they are available.

This incident has been resolved.

Fitbit data delivery has improved and we are continuing to monitor.

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.

This incident has been resolved.

Omron data appears to be coming through closer to normal and expected rates. We will continue to monitor.

We are continuing to investigate this issue.

Validic is investigating possible delays in the delivery of data from Omron. As a result, you may see delays in receiving user data from Omron users and users may see issues when trying to sync to Omron. We will provide updates here when they are available.

This incident has been resolved.

The issue with Fitbit data has been resolved and data is catching up. As a result, you may see delays in receiving user data from Fitbit users. We will provide updates here when they are available.

This incident has been resolved.

Polar has announced that they are investigating data transfer issues between Polar Flow and several services, including the Polar API. As a result, you may see delays in receiving user data from Polar users and users may see issues when trying to sync to Polar. We will provide updates here when they are available.

This incident has been resolved.

We're experiencing an elevated level of API errors and are currently looking into the issue.

Omron has confirmed that regular delivery of data has been restored.

The delivery of data from Omron is starting to return to expected levels. We will continue to monitor and provide updates here.

Validic is investigating possible delays in the delivery of data from Omron. As a result, you may see delays in receiving user data from Omron users and users may see issues when trying to sync to Omron. We will provide updates here when they are available.

This incident has been resolved.

Users attempting to connect to YOO via the Validic marketplace may be experiencing errors. As a result, users may not be able to connect to YOO at this time. Validic is investigating this issue with YOO and will provide updates here.