Validic Outage History

Started Oct 17, 2025, 05:07 PM UTC· resolved Nov 03, 2025, 02:49 PM UTC

1. identified Oct 17, 2025, 05:07 PM UTC

   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 [email protected]

2. resolved Nov 03, 2025, 02:49 PM UTC

   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 [email protected] https://help.validic.com/space/VCS/4957044737/Apple+Health+Summary+Record+Volume+Improvements

Read the full incident report →

Started Sep 11, 2025, 12:53 PM UTC· resolved Sep 29, 2025, 04:38 PM UTC

1. identified Sep 11, 2025, 12:53 PM UTC

   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 [email protected]

2. monitoring Sep 15, 2025, 02:06 PM UTC

   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 [email protected]

3. monitoring Sep 22, 2025, 02:05 PM UTC

   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.

4. resolved Sep 29, 2025, 04:38 PM UTC

   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

Read the full incident report →

Started Aug 06, 2025, 07:02 PM UTC· resolved Aug 07, 2025, 05:38 PM UTC

1. identified Aug 06, 2025, 07:02 PM UTC

   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.

2. resolved Aug 07, 2025, 05:38 PM UTC

   Fitbit made an adjustment on their side and the issue is fully resolved

Read the full incident report →

Started Aug 06, 2025, 03:24 AM UTC· resolved Aug 06, 2025, 05:51 PM UTC

1. investigating Aug 06, 2025, 03:24 AM UTC

   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.

2. monitoring Aug 06, 2025, 11:49 AM UTC

   Data is flowing successfully after a period where it wasn't. We're monitoring as the data catches back up.

3. resolved Aug 06, 2025, 05:51 PM UTC

   Data continues to flow as expected. This issue is resolved.

Read the full incident report →

Started Jul 11, 2025, 03:04 PM UTC· resolved Jul 17, 2025, 11:55 AM UTC

1. investigating Jul 11, 2025, 03:04 PM UTC

   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.

2. identified Jul 11, 2025, 03:49 PM UTC

   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.

3. monitoring Jul 11, 2025, 06:30 PM UTC

   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.

4. resolved Jul 17, 2025, 11:55 AM UTC

   This incident has been resolved.

Read the full incident report →

Started Jun 12, 2025, 06:52 PM UTC· resolved Jun 13, 2025, 01:14 PM UTC

1. investigating Jun 12, 2025, 06:52 PM UTC

   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

2. investigating Jun 12, 2025, 06:58 PM UTC

   We are also seeing possible delays in the delivery of Fitbit user data as a result of this outage.

3. investigating Jun 12, 2025, 08:03 PM UTC

   We are continuing to investigate this issue.

4. investigating Jun 12, 2025, 08:05 PM UTC

   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.

5. resolved Jun 13, 2025, 01:14 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Oct 24, 2024, 07:20 PM UTC· resolved Oct 25, 2024, 04:24 PM UTC

1. investigating Oct 24, 2024, 07:20 PM UTC

   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.

2. monitoring Oct 25, 2024, 12:21 AM UTC

   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.

3. resolved Oct 25, 2024, 04:24 PM UTC

   This incident has been resolved.

Read the full incident report →