03-22-2018 12:18
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report this post

03-22-2018 12:18
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report this post
- Who Voted for this post?
Hello API Team,
We're seeing increase in 503 and 504 response codes from many of the resource API endpoints we hit. Immediate retries of the same request usually resolve. It's about 2-20 requests per minute right now, small volume of the thousands of calls we make but holding pretty consistently and increasing.
Thanks,
--Aaron

03-22-2018 12:59 - edited 03-22-2018 13:11
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report this post

03-22-2018 12:59 - edited 03-22-2018 13:11
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report this post
We are too ... a lot of them.
Where we would see maybe a couple a day (and then requeue the attempt for a later time), each of our runs currently encounter a 503 or 504 on about 1.2% of the attempts (and slowly growing). This problem seems to have started around 8:53 AM CT yesterday and is continuing to slowly increase.

03-22-2018 15:23
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report this post


03-22-2018 15:23
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report this post
- Who Voted for this post?
Thanks for bringing this up.
We are investigating this currently. You could follow the updates on our status page: http://www.fitbitstatus.com/
Thanks,
Oleg
03-23-2018 07:51
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report this post

03-23-2018 07:51
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report this post
We are getting too many Invalid Refresh Tokens during and after this issue was detected and resolved.
Can Fitbit confirm if this is a consequence of the previous issue? Was there any data loss due to this problem?

