06-24-2020 09:39 - edited 06-24-2020 09:43
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report this post

06-24-2020 09:39 - edited 06-24-2020 09:43
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report this post
Around 7 AM Central, we started receiving the following 502 responses to our requests for data (which we request in response to notifications via the subscription API).
<html>
<head><title>502 Bad Gateway</title></head>
<body bgcolor="white">
<center><h1>502 Bad Gateway</h1></center>
<hr><center>nginx</center>
</body>
</html>
At first it was a few, which quite often seem to go away, but now climbing to over 10% of the responses we receive.
We see no other communication errors with any other endpoints we interface with, just with https://api.fitbit.com.
Can you assist?
Answered! Go to the Best Answer.

- Labels:
-
Subscriptions API
Accepted Solutions
06-24-2020 11:57
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report this post



06-24-2020 11:57
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report this post
I believe we have fixed the 502 errors now. Please let me know if you're still seeing them during your next batch pull
Senior Technical Solutions Consultant
Fitbit Partner Engineering & Web API Support | Google

06-24-2020 10:14
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report this post

06-24-2020 10:14
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report this post
- Who Voted for this post?
We have observed a similar situation. We poll ~3k users every hour and have had internal alerts go off due to the number of 502 responses the past two hours.
Fitbit's status page is still green.
06-24-2020 10:28
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report this post



06-24-2020 10:28
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report this post
- Who Voted for this post?
Hi @jeaglemc and @LifeOmic-Dev for reporting the 502 errors. I'm looking into it.
Senior Technical Solutions Consultant
Fitbit Partner Engineering & Web API Support | Google
06-24-2020 10:37
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report this post



06-24-2020 10:37
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report this post
- Who Voted for this post?
We've updated fitbitstatus.com for this incident and will post updates on that site going forward. If you have not signed up to receive updates from fitbitstatus.com, please go to the web site to subscribe.
Senior Technical Solutions Consultant
Fitbit Partner Engineering & Web API Support | Google
06-24-2020 10:51
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report this post



06-24-2020 10:51
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report this post
@jeaglemc and @LifeOmic-Dev ,
I'm seeing the 5xx errors have dropped in our graphs. Are you still experience the problem?
Senior Technical Solutions Consultant
Fitbit Partner Engineering & Web API Support | Google

06-24-2020 10:55
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report this post

06-24-2020 10:55
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report this post
@Gordon-C
We have an hourly ingestion coming up soon. I'll reply again once I see how those responses look.

06-24-2020 11:09
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report this post

06-24-2020 11:09
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report this post
Our recent batch of data pulls (in response to Subscription API notifications) is still receiving a high number of 502 responses - I would say about the same quantity that made me decide I should notify Fitbit. In addition to the:
<html>
<head><title>502 Bad Gateway</title></head>
<body bgcolor="white">
<center><h1>502 Bad Gateway</h1></center>
<hr><center>nginx</center>
</body>
</html>
... response, we're now seeing one that's formatted this way:
<html><head>
<meta http-equiv="content-type" content="text/html;charset=utf-8">
<title>502 Server Error</title>
</head>
<body text=#000000 bgcolor=#ffffff>
<h1>Error: Server Error</h1>
<h2>The server encountered a temporary error and could not complete your request.<p>Please try again in 30 seconds.</h2>
<h2></h2>
</body></html>
The first format is the majority ... we're receiving a smaller quantity of the second format.
Kind regards.
Jay

06-24-2020 11:14
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report this post

06-24-2020 11:14
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report this post
It looks like we received roughly the same number of 502 errors with this latest bulk ingest.

06-24-2020 11:19
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report this post



06-24-2020 11:19
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report this post
Thank you. We're still investigating.
Senior Technical Solutions Consultant
Fitbit Partner Engineering & Web API Support | Google

06-24-2020 11:57
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report this post



06-24-2020 11:57
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report this post
I believe we have fixed the 502 errors now. Please let me know if you're still seeing them during your next batch pull
Senior Technical Solutions Consultant
Fitbit Partner Engineering & Web API Support | Google

06-24-2020 12:22
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report this post

06-24-2020 12:22
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report this post
@Gordon-C That seemed to do the trick this time. Thanks!

06-24-2020 12:28
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report this post

06-24-2020 12:28
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report this post
All is well now. Thank you.

06-24-2020 12:37
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report this post



06-24-2020 12:37
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report this post
Thanks for the update. We'll continue to monitor the services for a few hours to make certain it doesn't pop back up. If you see more 5xx, let me know.
Senior Technical Solutions Consultant
Fitbit Partner Engineering & Web API Support | Google

