04-30-2018 12:27
04-30-2018 12:27
Starting at 1:15 PM Central Time, we are seeing a lot of 503 and 504 errors (mostly 503).
...
<span class="cf-error-type">Error</span>
<span class="cf-error-code">504</span>
<small class="heading-ray-id">Ray ID: 413c41989c0b9f11 • 2018-04-30 19:01:28 UTC</small>
</h1>
<h2 class="cf-subheadline">Gateway time-out</h2>
...
At this point in time, it appears better than 50% of our requests for data are receiving these errors. Can Fitbit assist?
Kind regards.
04-30-2018 12:31
04-30-2018 12:31
Yes, us as well. Has been about the last hour or so.
Best Answer04-30-2018 12:32
Fitbit Developers oversee the SDK and API forums. We're here to answer questions about Fitbit developer tools, assist with projects, and make sure your voice is heard by the development team.
04-30-2018 12:32
Hello,
We aware of the issue and trying to resolve it asap.
Sorry for any inconvenience.
Best Answer04-30-2018 15:23
04-30-2018 15:23
Any updates on this issue?
Would be nice if http://www.fitbitstatus.com/ were updated to reflect the problem
Best Answer05-03-2018 11:53
05-03-2018 11:53
Seems to be back this hour, lots more 503 and 504. Any update on things? Could we get updates on www.fitbitstatus.com
Thanks,
--Aaron
Best Answer05-08-2018 14:20
05-08-2018 14:20
We have also been seeing a lot of 503 & 504 errors on-and-off within the past few days. We've been seeing periods of these errors for the past couple of months. I too would like to see the Fitbit status page updated with information regarding these issues if possible.
Best Answer