02-16-2017 14:48
02-16-2017 14:48
The api returns a 502 Error for 1% of our calls. Are fitbit servers having issues? Where can I see the status of the api servers?
Best Answer02-16-2017 16:37
Community Moderator Alumni are previous members of the Moderation Team, which ensures conversations are friendly, factual, and on-topic. Moderators are here to answer questions, escalate bugs, and make sure your voice is heard by the larger Fitbit team. Learn more
02-16-2017 16:37
Best Answer02-16-2017 18:32
02-16-2017 18:32
Best Answer02-16-2017 18:33
02-16-2017 18:33
status page is down?
Best Answer02-17-2017 11:19
Community Moderator Alumni are previous members of the Moderation Team, which ensures conversations are friendly, factual, and on-topic. Moderators are here to answer questions, escalate bugs, and make sure your voice is heard by the larger Fitbit team. Learn more
02-17-2017 11:19
@SteveWT Status page should be back up.
We weren't able to find any 502s in the last 7 days. It'd be helpful if you provided your ClientID, the requests that resulted in 502s, and the timestamps of the requests.
Best Answer02-17-2017 14:20
02-17-2017 14:20
ClientId:22998K
The error timestamp is at:
Thu, Feb 16, 2017 at 12:29 PM Pacific Time.
We're also getting 504 errors as well.
02-17-2017 14:22
02-17-2017 14:22
Another 502 just came through.
Best Answer02-23-2017 21:35
02-23-2017 21:35
i just received a Fitbit 504 error.
Best Answer02-24-2017 13:28
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.
02-24-2017 13:28
Can you please provide the response headers and response body? The status codes alone don't give us enough information to diagnose the issue.
Best Answer