Monitoring - When a new Fitbit profile is connected to a Fitabase participant portal, regular data delivery may be delayed to Fitabase by as much as 12 hours. We have identified examples of situations where Fitbit's subscription service is correctly registered by 3rd party applications, but does not immediately begin. In this scenario our dashboards will show "No Device Sync Yet" even though the profile is set up correctly. Once the delay passes, syncing does appear to follow normal behavior.
Important note to customers: While we investigate this, be assured that we do not see any opportunity for data loss as the data is being correctly delivered to Fitbit's servers. The delay is the notifications that Fitabase needs to receive to trigger our timely synchronization. All examples of this have self-corrected after a number of hours and all unpulled data was correctly retrieved.
Oct 11, 2024 - 15:22 PDT
Important note to customers: While we investigate this, be assured that we do not see any opportunity for data loss as the data is being correctly delivered to Fitbit's servers. The delay is the notifications that Fitabase needs to receive to trigger our timely synchronization. All examples of this have self-corrected after a number of hours and all unpulled data was correctly retrieved.
Oct 11, 2024 - 15:22 PDT
Identified - We're aware that after the partial outage last week, a few profiles have missing data within a few key daily value fields. We are working to fully identify the affected profiles, working with Fitbit's team, and once fully scoped we will backfill missing values of affected profiles.
Sep 13, 2024 - 14:27 PDT
Sep 13, 2024 - 14:27 PDT
About This Site
Keep an eye here for any issue related to Fitabase's operational status. If you are observing odd behavior and it isn't listed on this page, please email us so we can investigate: support@fitabase.com.
Web App
?
Operational
Fitbit Syncing
?
Degraded Performance
API
?
Operational
Operational
Degraded Performance
Partial Outage
Major Outage
Maintenance