Validic Outage History

Validic is up right now

Validic had 9 outages in the last 2 years totaling 1607h 42m of downtime — averaging 0.4 incidents per month.

There were 9 Validic outages since August 1, 2024 totaling 1607h 42m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: http://status.validic.com

Minor August 6, 2025

Fitbit Nutrition Data Sync Errors

Detected by Pingoru
Aug 06, 2025, 07:02 PM UTC
Resolved
Aug 07, 2025, 05:38 PM UTC
Duration
22h 35m
Affected: Fitbit
Timeline · 2 updates
  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 →

Minor August 6, 2025

Fitbit Data Delays

Detected by Pingoru
Aug 06, 2025, 03:24 AM UTC
Resolved
Aug 06, 2025, 05:51 PM UTC
Duration
14h 26m
Affected: Fitbit
Timeline · 3 updates
  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 →

Minor July 11, 2025

API data delays or errors

Detected by Pingoru
Jul 11, 2025, 03:04 PM UTC
Resolved
Jul 17, 2025, 11:55 AM UTC
Duration
5d 20h
Affected: API
Timeline · 4 updates
  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 →

Major June 12, 2025

Google Authentication Outage

Detected by Pingoru
Jun 12, 2025, 06:52 PM UTC
Resolved
Jun 13, 2025, 01:14 PM UTC
Duration
18h 21m
Affected: APIFitbit
Timeline · 5 updates
  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 →

Minor October 24, 2024

iHealth Authorization Page Errors & Data Delays

Detected by Pingoru
Oct 24, 2024, 07:20 PM UTC
Resolved
Oct 25, 2024, 04:24 PM UTC
Duration
21h 4m
Affected: iHealth
Timeline · 3 updates
  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 →

Minor October 16, 2024

Validic Support Portal Page Load Issues

Detected by Pingoru
Oct 16, 2024, 01:37 PM UTC
Resolved
Oct 16, 2024, 03:32 PM UTC
Duration
1h 55m
Affected: Support Portal
Timeline · 3 updates
  1. investigating Oct 16, 2024, 01:37 PM UTC

    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.

  2. monitoring Oct 16, 2024, 01:56 PM UTC

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

  3. resolved Oct 16, 2024, 03:32 PM UTC

    This incident has been resolved.

Read the full incident report →