THIS IS A SCHEDULED EVENT Sep <var data-var='date'>1</var>, <var data-var='time'>00:00</var> - <var data-var='time'>01:00</var> EDT May <var data-var='date'>20</var>, <var data-var='time'>16:25</var> EDT Update - We're close to letting clients test Google Health integration in their sandboxes in the Inform API. Updates will be coming soon on that. Reach out to Validic support to migrate to Inform so you have access to this new feature. Google is rebranding Fitbit as Google Health, and that will require a new integration to continue receiving Fitbit data. That new integration won't be added to our v1 API. Clients will have to migrate to the Inform API to have access to this new integration. We're hosting a free webinar on May 27 at 2 PM ET specifically to walk your team through what this migration from the current Fitbit integration to the Google Health integration entails. It's more involved than a simple config change; it touches your data pipeline, your marketplace reconnection flow, and potentially parts of your data model. The sooner your engineers have a clear picture of the scope, the better. Register here: https://validic.zoom.us/webinar/register/3417792240109/WN_b9x0TULDS3KaO7e9jBXqhw May <var data-var='date'>11</var>, <var data-var='time'>16:26</var> EDT Scheduled - As you may have heard, Google is sunsetting the Fitbit Web API currently used for Validic's Fitbit integration. Google Health API is the replacement for the Fitbit Web API, and this new source will only be supported on Validic’s Inform API and not on the v1 API. Validic clients using the v1 API will have to migrate to the Inform API in order to continue ingesting data from end users’ Fitbit/Google Health apps. Google announced today that the Fitbit app will become Google Health on May 19th: https://support.google.com/fitbit/answer/17068213?hl=en&ref_topic=14236398&sjid=8074733428172977564-NA They have also set a Sept 2026 sunset date for the Fitbit Web API, so that means that Validic will be sunsetting the Fitbit integration for both Inform and v1 API at that time. Google hasn't announced a firm date in Sept at this time, so this maintenance thread will be updated as Google finalizes the date they are sunsetting the Fitbit Web API We are planning on having the Google Health API integration available for testing in Inform API in late May 2026. See more about the timeline on the Inform API for this coming integration: https://help.validic.com/space/VCS/5535203416/Fitbit+to+Google+Health+API:+Developer+Migration+Timeline Information on the migration from the v1 API to the Inform API can be found here. Reach out to Validic support through our support by sending an email to support@validic.com so we can guide you through your migration: https://help.validic.com/space/VCS/3462955048/Migrating+from+Legacy+API+to+Inform+API

Fitbit is becoming Google Health - Fitbit integration sunset in Sept 2026

May <var data-var='date'>20</var>, <var data-var='time'>16:24</var> EDT Completed - The scheduled maintenance has been completed. May <var data-var='date'>18</var>, <var data-var='time'>16:07</var> EDT Update - This is a reminder that tomorrow, May 19 2026, the Fitbit app will become Google Health. This coincides with the timeline to have to use Google auth instead of the Fitbit login to access the application: https://support.google.com/fitbit/answer/17068213?hl=en&ref_topic=14236398&sjid=8074733428172977564-NA Users that do not follow Google's instructions and do the required updates may not continue to transmit data after tomorrow, May 19. May <var data-var='date'>11</var>, <var data-var='time'>16:09</var> EDT Update - Google has announced that on May 19 2026, the Fitbit app will become Google Health. This coincides with the timeline to have to use Google auth instead of the Fitbit login to access the application: https://support.google.com/fitbit/answer/17068213?hl=en&ref_topic=14236398&sjid=8074733428172977564-NA They also shared Google Health app requirements: https://support.google.com/product-documentation/answer/14226283 Jan <var data-var='date'>30</var>, <var data-var='time'>15:45</var> EST Update - Google Fitbit has extended the deadline to move all Fitbit Accounts to Google Accounts to May 19, 2026. They have posted the full details of this process here: https://support.google.com/fitbit/answer/14237024 All of the previous information that Validic has shared about this is still accurate. Only the date has changed. Jan <var data-var='date'>14</var>, <var data-var='time'>09:06</var> EST Update - Google is finalizing the transition away from legacy Fitbit accounts. Beginning February 2, 2026, users must move their Fitbit account to a Google Account if they want to continue syncing data. If the migration hasn’t been completed by that date, the user’s Fitbit login will stop working, historical health data will no longer be accessible, and they will need to reauthorize in Inform once they complete the move. What your end users must do: -Open the Fitbit app on their smartphone (iOS or Android). -Tap their profile or settings icon. -Look for Move Account and follow the on-screen prompts to transfer their Fitbit account to a Google Account. -If they don’t see the prompt, it may appear after updating the Fitbit app to the latest version. -If they don’t already have a Google Account, they’ll be prompted to create one during the process. Important notes to share with your users: -The process generally takes just a few minutes and preserves their Fitbit history and device connections. -A personal Google Account is required (Google Workspace accounts typically won’t work). -Failure to migrate by Feb. 2, 2026, will result in Fitbit data no longer syncing, and they’ll need to re-authenticate after moving their accounts. Helpful Support Articles: Fitbit’s step-by-step guide from Google Help: https://support.google.com/fitbit/answer/14237024?hl=en Validic support article (guidance for migrating Fitbit users): https://help.validic.com/space/VCS/3755213034/Moving+a+Fitbit+user+to+a+Google+Account Please consider circulating this notice to your users as soon as possible. If you need a templated communication for your user base or have questions on how this impacts your Inform integration, let us know by emailing support@validic.com Additionally, note the following: For Fitbit Developer Accounts: * Do you have your own Fitbit developer account on dev.fitbit.com? * You *must* migrate this account to a Google Account. * If you don't switch, you will: - Lose API access - Can't log into your developer account - Lose all app and integration data Is Validic managing your developer credentials? - Validic does manage a large number of developer credentials for our clients. That being the case... - You likely don't need to do anything. - We'll handle the transition. Jul <var data-var='date'>21</var>, <var data-var='time'>16:04</var> EDT Scheduled - Google is moving all Fitbit accounts to Google Accounts. This change affects every Fitbit user and developer. You'll need to take steps to keep using Fitbit services and APIs. Key Dates You Should Know: * Now: Fitbit users can start moving to Google Accounts. * February 2, 2026: All Fitbit users *must* switch to a Google Account. - After this date, your old Fitbit login will stop working. - You'll lose access to your Fitbit account and data if you don't switch. What You Need to Do: 1. For Fitbit Users: * All Validic users with Fitbit accounts must move to a Google Account. * The switch is optional now, but required by February 2026. * Tell your users to prepare for this change. 2. For Fitbit Developer Accounts: * Do you have your own Fitbit developer account on dev.fitbit.com? * You *must* migrate this account to a Google Account. * If you don't switch, you will: - Lose API access - Can't log into your developer account - Lose all app and integration data Is Validic managing your developer credentials? - Validic does manage a large number of developer credentials for our clients. That being the case... - You likely don't need to do anything. - We'll handle the transition. - Still unsure? Contact support: https://help.validic.com/portal/2 Our team is working hard to make this transition smooth. We'll keep you updated as Google provides more details. Need help? Reach out to our support team: https://help.validic.com/portal/2 We also have an FAQ you can review: https://help.validic.com/space/VCS/3755213034/Moving+a+Fitbit+user+to+a+Google+Account See Google’s instructions: https://support.google.com/fitbit/answer/14237024

Important: Fitbit Account Changes - Action Needed by May 2026

Jan <var data-var='date'>27</var>, <var data-var='time'>12:00</var> EST Completed - The scheduled maintenance has been completed. Jan <var data-var='date'>27</var>, <var data-var='time'>10:00</var> EST In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary. Jan <var data-var='date'>16</var>, <var data-var='time'>09:02</var> EST Scheduled - We received this notice from Withings about the planned maintenance of their cloud service. Their status page is here: https://status.withings.io/#scheduled-33 "Scheduled Network Maintenance [Upcoming] Tuesday 27th January 2026 10:00:00 > We will be performing brief network maintenance on January 27th between 10:00 AM and 12:00 PM. While this window is two hours long, we anticipate a maximum service interruption of 5 minutes. We apologize for any inconvenience this may cause and appreciate your patience as we improve our infrastructure."

Withings maintenance

Jan <var data-var='date'> 8</var>, <var data-var='time'>02:00</var> EST Completed - The scheduled maintenance has been completed. Jan <var data-var='date'> 7</var>, <var data-var='time'>14:00</var> EST In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary. Dec <var data-var='date'> 8</var>, <var data-var='time'>08:57</var> EST Scheduled - Polar made us aware of the maintenance they have planned. Their notification is below: "Hereby we'd like to let you know that on Wednesday January 7th, 2026 at 07:00 UTC there will be a scheduled maintenance break in AccessLink API. We're expecting a downtime of up to 12 hours, and we will do our best to have the required database update ready as soon as possible. Queued data will be automatically transferred when the break is over. To track the progress of the maintenance break, head over to https://status.polar.com/. As always, if you have any questions, our Customer Care is happy to help you at b2bhelpdesk@polar.com. Thank you for your patience and understanding!"

Polar Maintenance

Nov <var data-var='date'> 3</var>, <var data-var='time'>09:49</var> EST Resolved - We are going to close this status page as it was more of an FYI for our clients than reporting an internal issue. If there are any questions about the below KBA, then reach out to the technical support team at support@validic.com https://help.validic.com/space/VCS/4957044737/Apple+Health+Summary+Record+Volume+Improvements Oct <var data-var='date'>17</var>, <var data-var='time'>13:07</var> EDT Identified - This is less of reporting an issue and more for noting a fix for something Validic noticed about Apple iOS 26 and summary records. Apple has always surfaced old summary records as new records in their HealthKit api as part of their housekeeping. In iOS 26, it appears this can happen much more frequently. Apple has acknowledged this is a bug in iOS 26. In versions older than Legacy iOS Native 1.18.0, in certain situations, the SDK would process that old record and then query every summary record since then. This creates a large volume of redundant summary records and slows the speed at which new data is ingested for users. More information about this is on this KBA: https://help.validic.com/space/VCS/4957044737/Apple+Health+Summary+Record+Volume+Improvements Clients using the Apple Health/HealthKit module in the Validic SDK are encouraged to update to Legacy iOS Native 1.18.0 to mitigate this and have the best performance they can with our integration with the HealthKit API If you or your team has any questions about the information above or in the linked KBA, open a ticket with Validic technical support by emailing support@validic.com

Newest Legacy iOS Native SDK versions for Apple Health summary query optimization

Oct <var data-var='date'>29</var>, <var data-var='time'>05:00</var> EDT Completed - The scheduled maintenance has been completed. Oct <var data-var='date'>29</var>, <var data-var='time'>02:00</var> EDT In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary. Sep <var data-var='date'>29</var>, <var data-var='time'>09:48</var> EDT Scheduled - Polar has made us aware that they will have a 3-hour maintenance period on 10/29/25. Below is the language they shared with us. "We'd like to let you know that on Wednesday 29th of October 2025 at 06:00 UTC we will have a scheduled maintenance break in all Polar services. We're expecting a downtime of up to 3 hours in AccessLink for "under-the-hood" improvements, after which it will take a few hours for all the services to be up and running at full speed. To track the progress of the maintenance break, head over to https://status.polar.com/. "

Sep <var data-var='date'>29</var>, <var data-var='time'>12:38</var> EDT Resolved - We have seen the number of errors continue to trend down, but we are still seeing errors for users who haven't taken the action of accepting the new Polar terms and conditions in the Polar application. We've created the following KBA regarding this. We urge our clients who depend on Polar data to be in communication with their end users to ensure you still receive Polar data from them. Since there is no action Validic can take to resolve this for the end user, we will be closing this status page. https://help.validic.com/space/VCS/4940169227/Polar+Terms+&+Conditions+Update+Required+for+Data+Syncs Sep <var data-var='date'>22</var>, <var data-var='time'>10:05</var> EDT Update - We are seeing the rate of errors for Polar trending down, but end users should still be encouraged to take the following action, as that will be the only path to resolution for the user's data being made available in the Polar cloud. It appears there are still a lot of users who haven't taken that action yet. Polar had an update to its system due to new EU regulations. Due to this, end users will need to open the Polar app on their phone and accept the new terms to allow for data sharing with third-party applications like the Validic ecosystem. Until an end user takes that action, data will not be shared with third-party applications, including Validic. Clients using Polar need to message end users to let them know to take this action to ensure continued data syncs from the Polar API to the Validic servers. Sep <var data-var='date'>15</var>, <var data-var='time'>10:06</var> EDT Monitoring - We appreciate the clients who have reached out to your users to request that they take this action in the Polar application to allow data to flow. We have not seen a great drop in the number of errors related to the need for the end users to take this action. Validic will be unable to pull data from the Polar API until users accept the new terms, including the update for the new EU regulations. Polar status page: https://status.polar.com/incidents/wn2cgh4q79pr Information on the EU regulations that went live: https://iapp.org/news/a/eu-data-act-all-your-threshold-questions-answered If a client using Polar has questions about this, send in a ticket to Validic technical support by emailing support@validic.com Sep <var data-var='date'>11</var>, <var data-var='time'>08:53</var> EDT Identified - Overnight, Polar had an update to its system due to new EU regulations. Due to this, end users will need to open the Polar app on their phone and accept the new terms to allow for data sharing with third-party applications like the Validic ecosystem. Until an end user takes that action, data will not be shared with third-party applications, including Validic. Clients using Polar need to message end users to let them know to take this action to ensure continued data syncs from the Polar API to the Validic servers. Information on the EU regulations that went live: https://iapp.org/news/a/eu-data-act-all-your-threshold-questions-answered Polar Status page on this: https://status.polar.com/ If a client using Polar has questions about this, send in a ticket to Validic technical support by emailing support@validic.com

Polar requiring end user accept new terms for data syncs

Sep <var data-var='date'>17</var>, <var data-var='time'>12:40</var> EDT Completed - The scheduled maintenance has been completed. Sep <var data-var='date'>16</var>, <var data-var='time'>12:52</var> EDT Scheduled - Withings has sent notification that they will be doing maintenance today at 20:00. They did not, however, note what timezone that 20:00 is for so we wanted to let everyone know about this so that you can expect that there might be Withings data delays or users unable to connect to Withings at some point later today. Here is the Withings notice: "Emergency network maintenance was scheduled for Tuesday 16th September 2025 20:00:00 A network equipment reboot will be performed with up to 5 minutes downtime during a 1h maintenance window Thanks, Withings Status"

Withings Scheduled Maintenance - Sept. 16

Aug <var data-var='date'> 7</var>, <var data-var='time'>13:38</var> EDT Resolved - Fitbit made an adjustment on their side and the issue is fully resolved Aug <var data-var='date'> 6</var>, <var data-var='time'>15:02</var> EDT Identified - We've identified an issue causing increased errors when syncing nutrition data from Fitbit, resulting in "500 Internal Server Error" entries appearing in client logs. The issue is due to recent unexpected changes in Fitbit's nutrition data format. Our engineering team is actively working on an update to handle these changes. We've reached out to Fitbit for clarification and are monitoring the situation closely. We will provide further updates as new information becomes available. Thank you for your patience.

Fitbit Nutrition Data Sync Errors

Aug <var data-var='date'> 6</var>, <var data-var='time'>13:51</var> EDT Resolved - Data continues to flow as expected. This issue is resolved. Aug <var data-var='date'> 6</var>, <var data-var='time'>07:49</var> EDT Monitoring - Data is flowing successfully after a period where it wasn't. We're monitoring as the data catches back up. Aug <var data-var='date'> 5</var>, <var data-var='time'>23:24</var> 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.

Fitbit Data Delays

Jul <var data-var='date'>17</var>, <var data-var='time'>14:18</var> EDT Resolved - Fitbit performance has been stable at the expected levels. Jul <var data-var='date'>17</var>, <var data-var='time'>11:04</var> EDT Monitoring - Fitbit has updated their status page noting that the issue is resolved. Validic is seeing data delivery start to return to expected levels. There may still be some delays while we receive any data that was not received during the outage. We will continue to monitor and provide updates here as they are available. Jul <var data-var='date'>17</var>, <var data-var='time'>08:04</var> EDT Update - Fitbit has reported that they are experiencing an outage at this time. The Validic team will continue to monitor. Fitbit is tracking this issue here: https://status.fitbit.com/ Jul <var data-var='date'>17</var>, <var data-var='time'>07:55</var> 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.

Jul <var data-var='date'>17</var>, <var data-var='time'>07:55</var> EDT Resolved - This incident has been resolved. Jul <var data-var='date'>11</var>, <var data-var='time'>14:30</var> EDT Monitoring - The Validic team has address the issue and all systems are caught up. We will continue to monitor to ensure that no new issues come up. Jul <var data-var='date'>11</var>, <var data-var='time'>11:49</var> EDT Identified - We have identified the issue and are working on a fix and monitoring all systems. More updates will be posted here as they are available. Jul <var data-var='date'>11</var>, <var data-var='time'>11:04</var> EDT Investigating - Validic is currently investigating possible issues with the Validic API. As a result, you may see delays or errors when attempting to make calls to the API to access data or manage users. We will post updates here as they are available.

API data delays or errors

Jun <var data-var='date'>23</var>, <var data-var='time'>09:00</var> EDT Completed - The scheduled maintenance has been completed. Jun <var data-var='date'>18</var>, <var data-var='time'>14:03</var> EDT Scheduled - On Monday June 23, 2025, Fitbit is planning to update their Web API infrastructure. This change is not expected to affect our systems or your experience. We will be monitoring during the update to ensure everything is running smoothly. No action is required on your part.

Fitbit API Update - June 23, 2025

Jun <var data-var='date'>13</var>, <var data-var='time'>09:14</var> EDT Resolved - This incident has been resolved. Jun <var data-var='date'>12</var>, <var data-var='time'>16:05</var> EDT Update - As an update here, Validic is finding that this outage is potentially affecting the delivery of data from more sources than just Fitbit. You may see delays receiving user data from potentially any data source at this time. Validic is continuing to closely monitor this. Jun <var data-var='date'>12</var>, <var data-var='time'>16:03</var> EDT Update - We are continuing to investigate this issue. Jun <var data-var='date'>12</var>, <var data-var='time'>14:58</var> EDT Update - We are also seeing possible delays in the delivery of Fitbit user data as a result of this outage. Jun <var data-var='date'>12</var>, <var data-var='time'>14:52</var> EDT Investigating - 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

Google Authentication Outage

Feb <var data-var='date'>27</var>, <var data-var='time'>14:48</var> EST Completed - The scheduled maintenance has been completed. Feb <var data-var='date'>24</var>, <var data-var='time'>15:03</var> EST Scheduled - Validic will be sunsetting the following cloud sources on 2/27/25. 1. Bewell Connect 2. Qardio 3. Daily Burn If you have any questions regarding this action reach out to support@validic.com for assistance

Sunset of Bewell Connect, Qardio, and Daily Burn

Jan <var data-var='date'>22</var>, <var data-var='time'>11:53</var> EST Completed - This task has been completed. Dec <var data-var='date'>18</var>, <var data-var='time'>08:33</var> EST Scheduled - FatSecret has informed Validic that they are planning to sunset their existing authentication workflow for users on January 24, 2025. A new authentication workflow has been created and the changes required to the Legacy API, combined with the very low user volume, are such that we have decided to sunset support for FatSecret in the legacy Validic API. If you are a legacy (v1) API customer and you would like to continue to use the FatSecret integration, please reach out to your Validic Client Success Executive or the Validic Customer Support team to discuss your options, which will include a migration to the Inform platform. Validic is working to remove FatSecret from all legacy Validic marketplaces on January 21, 2025. After this date: * Connected FatSecret users be automatically disconnected from FatSecret * Users will no longer see FatSecret as a source in the marketplace * FatSecret data records will no longer sync to the legacy API

Sunset of FatSecret

Dec <var data-var='date'>10</var>, <var data-var='time'>12:31</var> EST Resolved - This incident has been resolved. Dec <var data-var='date'> 3</var>, <var data-var='time'>13:38</var> EST Monitoring - Fitbit has reported that this issue is resolved. Validic will continue to monitor as we do see data flow gradually returning to normal. Dec <var data-var='date'> 3</var>, <var data-var='time'>09:22</var> EST Update - Fitbit has confirmed that they are reporting a service outage via their status page. Validic will continue to monitor. https://status.fitbit.com/ Dec <var data-var='date'> 3</var>, <var data-var='time'>06:25</var> EST 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.

Oct <var data-var='date'>25</var>, <var data-var='time'>12:24</var> EDT Resolved - This incident has been resolved. Oct <var data-var='date'>24</var>, <var data-var='time'>20:21</var> EDT Monitoring - 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. Oct <var data-var='date'>24</var>, <var data-var='time'>15:20</var> EDT Investigating - 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.

iHealth Authorization Page Errors & Data Delays

Oct <var data-var='date'>23</var>, <var data-var='time'>11:18</var> EDT Resolved - 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. Sep <var data-var='date'>30</var>, <var data-var='time'>16:16</var> EDT Investigating - 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

Fitbit update

Oct <var data-var='date'>16</var>, <var data-var='time'>11:32</var> EDT Resolved - This incident has been resolved. Oct <var data-var='date'>16</var>, <var data-var='time'>09:56</var> EDT Monitoring - Page loads are returning to the expected behavior in the Validic Support Portal. We will monitor for stability. Oct <var data-var='date'>16</var>, <var data-var='time'>09:37</var> EDT Investigating - 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.

Validic Support Portal Page Load Issues

Aug <var data-var='date'> 2</var>, <var data-var='time'>11:08</var> EDT Resolved - This incident has been resolved. Aug <var data-var='date'> 1</var>, <var data-var='time'>12:55</var> EDT 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. At this time, the queue is catching up, but there still may be slight delays in the delivery of Fitbit data.

Jul <var data-var='date'>16</var>, <var data-var='time'>10:14</var> EDT Resolved - This incident has been resolved. Aug <var data-var='date'>23</var>, <var data-var='time'>13:32</var> EDT Update - Validic is still investigating possible solutions to the Polar authorization issues. We will update this status as more information becomes available. Jul <var data-var='date'>12</var>, <var data-var='time'>13:36</var> EDT Investigating - 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.

Polar Authorization Errors

Apr <var data-var='date'>19</var>, <var data-var='time'>12:05</var> EDT Resolved - Fitbit data continues to flow as expected. This issue is resolved. Apr <var data-var='date'>19</var>, <var data-var='time'>11:15</var> EDT Monitoring - Fitbit data is again flowing as expected. We will continue to monitor for stability. Apr <var data-var='date'>19</var>, <var data-var='time'>09:47</var> 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.

Mar <var data-var='date'>19</var>, <var data-var='time'>16:22</var> EDT Resolved - 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 Mar <var data-var='date'> 7</var>, <var data-var='time'>13:21</var> EST Update - 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. Feb <var data-var='date'>28</var>, <var data-var='time'>14:40</var> EST Monitoring - 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

Strava Updating to New Developer Program

Dec <var data-var='date'>11</var>, <var data-var='time'>08:18</var> EST Resolved - This issue if fully resolved. Dec <var data-var='date'> 9</var>, <var data-var='time'>11:04</var> EST Monitoring - The Fitbit integration appears to be functioning as designed at this point. We're monitoring the situation to ensure it is completely resolved. Dec <var data-var='date'> 9</var>, <var data-var='time'>08:49</var> EST 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.

Is Validic V1 down?

Validic V1 status is UP

Lastest published events

Fitbit is becoming Google Health - Fitbit integration sunset in Sept 2026

Important: Fitbit Account Changes - Action Needed by May 2026

Withings maintenance

Validic V1 Services, Components and Regions

Recent Validic V1 events

Fitbit is becoming Google Health - Fitbit integration sunset in Sept 2026

Important: Fitbit Account Changes - Action Needed by May 2026

Withings maintenance

Polar Maintenance

Newest Legacy iOS Native SDK versions for Apple Health summary query optimization

Polar Maintenance

Get your FREE account now,
5 monitors included!

Is Validic V1 down?

Validic V1 status is UP

Lastest published events

Fitbit is becoming Google Health - Fitbit integration sunset in Sept 2026

Important: Fitbit Account Changes - Action Needed by May 2026

Withings maintenance

Validic V1 Services, Components and Regions

Recent Validic V1 events

Fitbit is becoming Google Health - Fitbit integration sunset in Sept 2026

Important: Fitbit Account Changes - Action Needed by May 2026

Withings maintenance

Polar Maintenance

Newest Legacy iOS Native SDK versions for Apple Health summary query optimization

Polar Maintenance

Get your FREE account now,5 monitors included!

Get your FREE account now,
5 monitors included!