tag:status.validic.com,2005:/historyValidic V1 Status - Incident History2024-03-28T20:06:41-04:00Validic V1tag:status.validic.com,2005:Incident/201002302024-03-19T16:22:03-04:002024-03-19T16:22:03-04:00Strava Updating to New Developer Program<p><small>Mar <var data-var='date'>19</var>, <var data-var='time'>16:22</var> EDT</small><br><strong>Resolved</strong> - 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</p><p><small>Mar <var data-var='date'> 7</var>, <var data-var='time'>13:21</var> EST</small><br><strong>Update</strong> - 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.</p><p><small>Feb <var data-var='date'>28</var>, <var data-var='time'>14:40</var> EST</small><br><strong>Monitoring</strong> - 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.<br /><br />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.<br /><br />There is no action for you or your Strava users. No interruption of data delivery is expected.<br /><br />This status page is simply to inform you that this change will be happening behind the scenes.<br /><br />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</p>tag:status.validic.com,2005:Incident/193858542023-12-11T08:18:53-05:002023-12-11T08:18:53-05:00Fitbit Data Delays<p><small>Dec <var data-var='date'>11</var>, <var data-var='time'>08:18</var> EST</small><br><strong>Resolved</strong> - This issue if fully resolved.</p><p><small>Dec <var data-var='date'> 9</var>, <var data-var='time'>11:04</var> EST</small><br><strong>Monitoring</strong> - The Fitbit integration appears to be functioning as designed at this point. We're monitoring the situation to ensure it is completely resolved.</p><p><small>Dec <var data-var='date'> 9</var>, <var data-var='time'>08:49</var> EST</small><br><strong>Investigating</strong> - Validic is investigating possible issues with the delivery of data from Fitbit.<br /><br />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.<br /><br />We will provide updates here when they are available.</p>tag:status.validic.com,2005:Incident/185352322023-09-28T10:44:01-04:002023-09-28T10:44:01-04:00TomTom is sunsetting it's API on Sept. 30 2023<p><small>Sep <var data-var='date'>28</var>, <var data-var='time'>10:44</var> EDT</small><br><strong>Completed</strong> - The scheduled maintenance has been completed.</p><p><small>Sep <var data-var='date'>28</var>, <var data-var='time'>09:44</var> EDT</small><br><strong>In progress</strong> - Scheduled maintenance is currently in progress. We will provide updates as necessary.</p><p><small>Sep <var data-var='date'>18</var>, <var data-var='time'>09:49</var> EDT</small><br><strong>Scheduled</strong> - We've been made aware that TomTom is sunsetting it's API on Sept 30 2023. Due to this we are planning to sunset TomTom as a source shortly before that date. When that occurs TomTom will be removed as a source in the marketplace for any orgs that are connected to this source. Users will no longer sync data with that source as of 9/30/23. <br /><br />For clarity on what actions will be taken on TomTom's end. Below is what was communicated to us from TomTom:<br /><br />The TomTom Sports mobile app, MySports Website, MySports Connect desktop application and all Sports Cloud APIs will be discontinued and permanently removed.<br /> <br />Users of our sports products may be able to still use them to see activity statistics on their device itself, but they will no longer get updates or will not be able to sync activities to the TomTom Sports platforms and applications.<br /> <br />Users that would like to keep their activity history, can download it from the TomTom MySports web application until the 30th September 2023.</p>tag:status.validic.com,2005:Incident/181866642023-08-18T13:18:26-04:002023-08-18T13:18:26-04:0030 Minute Data Processing delay<p><small>Aug <var data-var='date'>18</var>, <var data-var='time'>13:18</var> EDT</small><br><strong>Resolved</strong> - 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.</p>tag:status.validic.com,2005:Incident/178363192023-08-23T13:32:31-04:002023-08-23T13:32:31-04:00Polar Authorization Errors<p><small>Aug <var data-var='date'>23</var>, <var data-var='time'>13:32</var> EDT</small><br><strong>Update</strong> - Validic is still investigating possible solutions to the Polar authorization issues. We will update this status as more information becomes available.</p><p><small>Jul <var data-var='date'>12</var>, <var data-var='time'>13:36</var> EDT</small><br><strong>Investigating</strong> - Validic is investigating a possible issue where users may experience errors when attempting to authorize Polar in the Validic marketplace.<br /><br />As a result, some users may not be able to successfully connect to Polar.<br /><br />We will provide updates here as they are available.</p>tag:status.validic.com,2005:Incident/169845112023-07-07T09:58:37-04:002023-07-07T09:58:37-04:00Upcoming Omron API Changes<p><small>Jul <var data-var='date'> 7</var>, <var data-var='time'>09:58</var> EDT</small><br><strong>Completed</strong> - This update is complete and Omron has been removed from the Validic Legacy API.</p><p><small>May <var data-var='date'>23</var>, <var data-var='time'>13:15</var> EDT</small><br><strong>Update</strong> - Omron has informed Validic that they are planning to sunset their existing Partner API for US and Canadian users on July 10, 2023. This is a full shutdown of the existing API and a new Omron Partner API will be created to include:<br /><br />- Security improvements<br />- Increased reliability<br />- Streamlined onboarding process<br /><br />The new Omron Partner API introduces extensive changes compared to their existing Partner API, and as a result, Omron cloud will no longer be supported by the legacy Validic API.<br /><br />If you are a legacy (v1) API customer and you would like to continue to use the Omron cloud integration, please reach out to your Validic Client Success Executive or the Validic Customer Support team to discuss our migration process to the Inform platform, which will support the new Omron Partner API. <br /><br />Validic is working to remove Omron cloud from all legacy Validic marketplaces on June 29, 2023.</p><p><small>Apr <var data-var='date'>27</var>, <var data-var='time'>14:21</var> EDT</small><br><strong>Scheduled</strong> - Omron has informed Validic that they are planning some changes to their Partner API in the Summer of 2023.<br /><br />Validic is working closely with Omron to determine how these changes will impact Validic clients.<br /><br />We will provide updates here when they are available.</p>tag:status.validic.com,2005:Incident/177036912023-06-28T00:41:27-04:002023-06-28T00:41:27-04:00Fitbit Reporting Login or Data Issues for Google Users<p><small>Jun <var data-var='date'>28</var>, <var data-var='time'>00:41</var> EDT</small><br><strong>Resolved</strong> - Fitbit has resolved this issue.</p><p><small>Jun <var data-var='date'>27</var>, <var data-var='time'>19:10</var> EDT</small><br><strong>Investigating</strong> - 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.<br /><br />As a result, you may not see some Fitbit user data in the Validic API while Fitbit works to resolve this issue.<br /><br />Validic will continue to monitor this and provide updates here when they are available.</p>tag:status.validic.com,2005:Incident/175638722023-06-13T19:10:49-04:002023-06-13T19:10:49-04:00OneTouch Data Delays<p><small>Jun <var data-var='date'>13</var>, <var data-var='time'>19:10</var> EDT</small><br><strong>Resolved</strong> - This incident has been resolved.</p><p><small>Jun <var data-var='date'>13</var>, <var data-var='time'>17:02</var> EDT</small><br><strong>Monitoring</strong> - OneTouch data is starting to flow as expected. Validic will continue to monitor.</p><p><small>Jun <var data-var='date'>13</var>, <var data-var='time'>16:22</var> EDT</small><br><strong>Identified</strong> - This issue appears to be related to a widespread AWS issue. We are continuing to monitor.</p><p><small>Jun <var data-var='date'>13</var>, <var data-var='time'>15:54</var> EDT</small><br><strong>Investigating</strong> - Validic is investigating possible issues with the delivery of data from OneTouch.<br /><br />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.<br /><br />We will provide updates here when they are available.</p>tag:status.validic.com,2005:Incident/175618462023-06-13T17:00:57-04:002023-06-13T17:00:57-04:00MyFitnessPal Data Delays<p><small>Jun <var data-var='date'>13</var>, <var data-var='time'>17:00</var> EDT</small><br><strong>Resolved</strong> - This incident has been resolved.</p><p><small>Jun <var data-var='date'>13</var>, <var data-var='time'>14:20</var> EDT</small><br><strong>Monitoring</strong> - MyFitnessPal data is starting to flow as expected. Validic will continue to monitor.</p><p><small>Jun <var data-var='date'>13</var>, <var data-var='time'>13:28</var> EDT</small><br><strong>Investigating</strong> - Validic is investigating possible issues with the delivery of data from MyFitnessPal.<br /><br />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.<br /><br />We will provide updates here when they are available.</p>tag:status.validic.com,2005:Incident/175622722023-06-13T17:00:44-04:002023-06-13T17:00:44-04:00Fitbit Data Delays<p><small>Jun <var data-var='date'>13</var>, <var data-var='time'>17:00</var> EDT</small><br><strong>Resolved</strong> - This incident has been resolved.</p><p><small>Jun <var data-var='date'>13</var>, <var data-var='time'>14:38</var> EDT</small><br><strong>Monitoring</strong> - Fitbit data is starting to flow as expected. Validic will continue to monitor.</p><p><small>Jun <var data-var='date'>13</var>, <var data-var='time'>14:20</var> EDT</small><br><strong>Investigating</strong> - Validic is investigating possible issues with the delivery of data from Fitbit.<br /><br />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.<br /><br />We will provide updates here when they are available.</p>tag:status.validic.com,2005:Incident/175605162023-06-13T11:14:45-04:002023-06-13T11:14:45-04:00Legacy API Documentation Changes<p><small>Jun <var data-var='date'>13</var>, <var data-var='time'>11:14</var> EDT</small><br><strong>Completed</strong> - The scheduled maintenance has been completed.</p><p><small>Jun <var data-var='date'>13</var>, <var data-var='time'>10:56</var> EDT</small><br><strong>Scheduled</strong> - Effective immediately, our Legacy API documentation will be relocated to our support site. Any previous traffic directed to https://docs.validic.com will now be redirected to https://help.validic.com/space/VCS/3497361441. <br /><br />Although the new documentation structure closely resembles our original docs, if you feel like something is missing, please don't hesitate to open a support case.</p>tag:status.validic.com,2005:Incident/174898472023-06-13T10:36:57-04:002023-06-13T10:36:57-04:00Polar Flow Consent Requirements<p><small>Jun <var data-var='date'>13</var>, <var data-var='time'>10:36</var> EDT</small><br><strong>Completed</strong> - The scheduled maintenance has been completed.</p><p><small>Jun <var data-var='date'> 6</var>, <var data-var='time'>09:46</var> EDT</small><br><strong>Scheduled</strong> - On June 5, 2023, Polar reached out to their users with a notice that all users will need to update their consent to share their data via Polar Flow.<br /><br />Users must log in to their Polar Flow account and accept the new consent terms in order to have their data continue to be available via the Polar API.</p>tag:status.validic.com,2005:Incident/175034412023-06-07T19:00:31-04:002023-06-07T19:00:31-04:00Fitbit Reporting Data Issues for Google Users<p><small>Jun <var data-var='date'> 7</var>, <var data-var='time'>19:00</var> EDT</small><br><strong>Resolved</strong> - Fitbit has reported that this issue is resolved. Details can be found here:<br />https://www.fitbitstatus.com/incidents/5p02cq0yd4pf</p><p><small>Jun <var data-var='date'> 7</var>, <var data-var='time'>12:58</var> EDT</small><br><strong>Investigating</strong> - Correction: Fitbit is still investigating this issue and Validic will continue to monitor.</p><p><small>Jun <var data-var='date'> 7</var>, <var data-var='time'>12:57</var> EDT</small><br><strong>Monitoring</strong> - Fitbit has implemented a fix to this issue. We will continue to monitor.</p><p><small>Jun <var data-var='date'> 7</var>, <var data-var='time'>12:33</var> EDT</small><br><strong>Investigating</strong> - Fitbit has reported that users who have connected their Fitbit accounts via Google may not have their data available in the Fitbit public API.<br /><br />As a result, you may not see some Fitbit user data in the Validic API while Fitbit works to resolve this issue.<br /><br />Validic will continue to monitor this and provide updates here when they are available.</p>tag:status.validic.com,2005:Incident/174958262023-06-07T10:17:54-04:002023-06-07T10:17:54-04:00OneTouch Data Delays<p><small>Jun <var data-var='date'> 7</var>, <var data-var='time'>10:17</var> EDT</small><br><strong>Resolved</strong> - This incident has been resolved.</p><p><small>Jun <var data-var='date'> 7</var>, <var data-var='time'>06:31</var> EDT</small><br><strong>Monitoring</strong> - OneTouch data has been flowing as expected. Validic will continue to monitor for stability.</p><p><small>Jun <var data-var='date'> 6</var>, <var data-var='time'>21:33</var> EDT</small><br><strong>Investigating</strong> - Validic is investigating possible issues with the delivery of data from OneTouch.<br /><br />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.<br /><br />We will provide updates here when they are available.</p>tag:status.validic.com,2005:Incident/174406482023-06-01T10:56:41-04:002023-06-01T10:56:42-04:00Omron Data Delays<p><small>Jun <var data-var='date'> 1</var>, <var data-var='time'>10:56</var> EDT</small><br><strong>Resolved</strong> - This incident has been resolved.</p><p><small>Jun <var data-var='date'> 1</var>, <var data-var='time'>09:09</var> EDT</small><br><strong>Monitoring</strong> - Omron data appears to be flowing as expected. We will continue to monitor for stability.</p><p><small>Jun <var data-var='date'> 1</var>, <var data-var='time'>05:01</var> EDT</small><br><strong>Investigating</strong> - Validic is investigating possible delays in the delivery of data from Omron.<br /><br />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.<br /><br />We will provide updates here when they are available.</p>tag:status.validic.com,2005:Incident/169656992023-04-26T09:09:38-04:002023-04-26T09:09:38-04:00Runkeeper Data Delays<p><small>Apr <var data-var='date'>26</var>, <var data-var='time'>09:09</var> EDT</small><br><strong>Resolved</strong> - This incident has been resolved.</p><p><small>Apr <var data-var='date'>25</var>, <var data-var='time'>16:12</var> EDT</small><br><strong>Investigating</strong> - Validic is investigating possible issues with the delivery of data from Runkeeper.<br /><br />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.<br /><br />We will provide updates here when they are available.</p>tag:status.validic.com,2005:Incident/167008552023-04-12T08:56:44-04:002023-04-12T08:56:44-04:00LifeScan Scheduled Maintenance - Wednesday, April 5, 2023<p><small>Apr <var data-var='date'>12</var>, <var data-var='time'>08:56</var> EDT</small><br><strong>Completed</strong> - The scheduled maintenance has been completed.</p><p><small>Mar <var data-var='date'>30</var>, <var data-var='time'>15:31</var> EDT</small><br><strong>Scheduled</strong> - LifeScan has announced that they will be performing database maintenance on Wednesday, April 5, 2023 starting at 10:00pm EDT lasting for approximately 1-2 hours.<br /><br />During this maintenance, users may not be able to sync to LifeScan via the Validic Marketplace and delivery data from LifeScan may be delayed until the maintenance is complete.</p>tag:status.validic.com,2005:Incident/167610532023-04-12T08:56:27-04:002023-04-12T08:56:27-04:00Garmin Data Delays<p><small>Apr <var data-var='date'>12</var>, <var data-var='time'>08:56</var> EDT</small><br><strong>Resolved</strong> - The backfill data completely cleared our queue and everything is back to normal with the data flow for Garmin. We're resolving this issue</p><p><small>Apr <var data-var='date'>11</var>, <var data-var='time'>16:34</var> EDT</small><br><strong>Update</strong> - 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.</p><p><small>Apr <var data-var='date'>11</var>, <var data-var='time'>16:33</var> EDT</small><br><strong>Update</strong> - 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.</p><p><small>Apr <var data-var='date'>11</var>, <var data-var='time'>11:25</var> EDT</small><br><strong>Update</strong> - 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.</p><p><small>Apr <var data-var='date'> 7</var>, <var data-var='time'>13:30</var> EDT</small><br><strong>Update</strong> - 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.</p><p><small>Apr <var data-var='date'> 7</var>, <var data-var='time'>10:00</var> EDT</small><br><strong>Update</strong> - 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</p><p><small>Apr <var data-var='date'> 6</var>, <var data-var='time'>08:49</var> EDT</small><br><strong>Monitoring</strong> - 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.</p><p><small>Apr <var data-var='date'> 5</var>, <var data-var='time'>12:06</var> EDT</small><br><strong>Investigating</strong> - Validic is investigating possible issues with the delivery of data from Garmin.<br /><br />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.<br /><br />We will provide updates here when they are available.</p>tag:status.validic.com,2005:Incident/167712842023-04-07T09:59:25-04:002023-04-07T09:59:25-04:00Data Collection Error<p><small>Apr <var data-var='date'> 7</var>, <var data-var='time'>09:59</var> EDT</small><br><strong>Resolved</strong> - 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.</p><p><small>Apr <var data-var='date'> 6</var>, <var data-var='time'>20:54</var> EDT</small><br><strong>Update</strong> - The Withings data has caught up. This will be monitored overnight and accessed in the morning. There will be an update then</p><p><small>Apr <var data-var='date'> 6</var>, <var data-var='time'>16:22</var> EDT</small><br><strong>Monitoring</strong> - 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.</p><p><small>Apr <var data-var='date'> 6</var>, <var data-var='time'>12:06</var> EDT</small><br><strong>Update</strong> - Additional investigation has added more affected sources. Investigation continues, but a path to resolution is being worked on.<br /><br />MyFitnessPal<br />Garmin<br />Misfit<br />Withings<br />Strava<br />Polar<br />Tomtom<br />UA</p><p><small>Apr <var data-var='date'> 6</var>, <var data-var='time'>11:42</var> EDT</small><br><strong>Investigating</strong> - 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.</p>tag:status.validic.com,2005:Incident/165792032023-04-04T15:12:21-04:002023-04-04T15:12:21-04:00Misfit Integration to be Sunset April 1, 2023<p><small>Apr <var data-var='date'> 4</var>, <var data-var='time'>15:12</var> EDT</small><br><strong>Completed</strong> - The scheduled maintenance has been completed.</p><p><small>Mar <var data-var='date'>22</var>, <var data-var='time'>11:05</var> EDT</small><br><strong>Update</strong> - It appears that Misfit stopped sending data through their api the week of 3/6/23. <br /><br />We have taken the action of removing Misfit from the standard marketplace of any org with a connected user. <br /><br />If you are using a custom marketplace you will need to update that to remove Misfit from it. Misfit Oauth has also been shutdown on their end, so removing Misfit from your marketplace now would avoid user confusion.</p><p><small>Mar <var data-var='date'>20</var>, <var data-var='time'>14:46</var> EDT</small><br><strong>Scheduled</strong> - Misfit's parent company, Fossil, has announced that they will be fully sunsetting the Misfit integration by April 1, 2023. This is a full shutdown of their API and ability to authorize or share Misfit data.<br /><br />As a result, Misfit smart watches will no longer be supported by the Validic API.<br /><br />Validic is working to remove Misfit from all Validic marketplaces by April 1. In the meantime, you may have users who attempt to authorize Misfit encounter errors.</p>tag:status.validic.com,2005:Incident/166791402023-03-28T16:45:39-04:002023-03-28T16:45:39-04:00Fitbit Data Delays<p><small>Mar <var data-var='date'>28</var>, <var data-var='time'>16:45</var> EDT</small><br><strong>Resolved</strong> - This incident has been resolved.</p><p><small>Mar <var data-var='date'>28</var>, <var data-var='time'>14:46</var> EDT</small><br><strong>Investigating</strong> - Validic is investigating possible issues with the delivery of data from Fitbit.<br /><br />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.<br /><br />We will provide updates here when they are available.</p>tag:status.validic.com,2005:Incident/163481082023-03-06T15:48:56-05:002023-03-06T15:48:56-05:00Fitbit Reporting API Errors<p><small>Mar <var data-var='date'> 6</var>, <var data-var='time'>15:48</var> EST</small><br><strong>Resolved</strong> - Fitbit has resolved this issue and all is working as expected.</p><p><small>Mar <var data-var='date'> 5</var>, <var data-var='time'>16:37</var> EST</small><br><strong>Monitoring</strong> - Fitbit is reporting that they are no longer seeing a spike in errors with the API. Validic will continue to monitor.</p><p><small>Mar <var data-var='date'> 5</var>, <var data-var='time'>14:08</var> EST</small><br><strong>Investigating</strong> - Fitbit is currently reporting a higher than expected rate of errors with their API at this time and are investigating the issue.<br /><br />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.<br /><br />We will provide updates here when they are available.</p>tag:status.validic.com,2005:Incident/162943332023-02-28T12:22:54-05:002023-02-28T12:22:54-05:00iHealth Authorization Error<p><small>Feb <var data-var='date'>28</var>, <var data-var='time'>12:22</var> EST</small><br><strong>Resolved</strong> - iHealth has implemented a fix and this issue is resolved.</p><p><small>Feb <var data-var='date'>27</var>, <var data-var='time'>19:49</var> EST</small><br><strong>Identified</strong> - iHealth is actively working on a fix to this issue.</p><p><small>Feb <var data-var='date'>27</var>, <var data-var='time'>16:11</var> EST</small><br><strong>Update</strong> - We've reached out to our iHealth contacts for assistance in resolving this. The issue appears intermittent. iHealth is investigating</p><p><small>Feb <var data-var='date'>27</var>, <var data-var='time'>10:02</var> EST</small><br><strong>Investigating</strong> - Some users are currently reporting errors when trying to connect to iHealth via the Validic Marketplace.<br /><br />Validic is investigating this issue and will provide updates here as they become available.</p>tag:status.validic.com,2005:Incident/162214842023-02-21T11:25:53-05:002023-02-21T11:25:53-05:00Withings is Reporting Authorization Issues<p><small>Feb <var data-var='date'>21</var>, <var data-var='time'>11:25</var> EST</small><br><strong>Resolved</strong> - Withings authorization endpoints are working as expected.</p><p><small>Feb <var data-var='date'>21</var>, <var data-var='time'>09:22</var> EST</small><br><strong>Monitoring</strong> - Withings has implemented a fix to the OAuth2 issue. Validic will continue to monitor.</p><p><small>Feb <var data-var='date'>21</var>, <var data-var='time'>09:05</var> EST</small><br><strong>Investigating</strong> - 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.<br /><br />As a result, some users may not be able to sync their Withings users to Validic.<br /><br />We will provide updates here when they are available.</p>tag:status.validic.com,2005:Incident/159377832023-02-10T13:05:38-05:002023-02-10T13:05:38-05:00Under Armour Data Delays<p><small>Feb <var data-var='date'>10</var>, <var data-var='time'>13:05</var> EST</small><br><strong>Resolved</strong> - This incident has been resolved.</p><p><small>Jan <var data-var='date'>30</var>, <var data-var='time'>16:10</var> EST</small><br><strong>Update</strong> - 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.</p><p><small>Jan <var data-var='date'>26</var>, <var data-var='time'>13:30</var> EST</small><br><strong>Monitoring</strong> - The issue appears to be resolved. We're monitoring this now to ensure stability of the data delivery.</p><p><small>Jan <var data-var='date'>25</var>, <var data-var='time'>21:19</var> EST</small><br><strong>Investigating</strong> - Validic is investigating possible issues with the delivery of data from Under Armour.<br /><br />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.<br /><br />We will provide updates here when they are available.</p>