05-07-2015 03:31
05-07-2015 03:31
Hello
I am seeing a large number of unknown host errors in the API since 615am EDT. There were no changes in my application and it does not appear that there are any network errors. Are there any known issues that may cause this?
Answered! Go to the Best Answer.
05-07-2015 08:55 - edited 05-07-2015 09:06
05-07-2015 08:55 - edited 05-07-2015 09:06
Issue had been resolved now.
If you application has been disabled due to this issue please go ahead and enable it back.
05-07-2015 03:46
05-07-2015 03:46
Same issues here..
05-07-2015 05:35
05-07-2015 05:35
I'm experiencing the same issue
05-07-2015 06:10
05-07-2015 06:10
We are having the same problem. Are there any changes made on Fitbit API side or any issues they experience? Fitbit team, any updates witll be greatly appreciated.
05-07-2015 06:36 - edited 05-07-2015 07:53
05-07-2015 06:36 - edited 05-07-2015 07:53
Confirmed for cafewell.com too.
05-07-2015 06:42
05-07-2015 06:42
PS: I've informed the Fitbit team, let's wait and see with what they come up.
05-07-2015 06:56
05-07-2015 06:56
I guess it has to with this: https://community.fitbit.com/t5/Web-API/Heart-Rate-GPS-and-OAuth-2-0-Update/td-p/730277
05-07-2015 07:05
05-07-2015 07:05
At 6:28am CT, I recevied an email from Fitbit stating that my endpoint had been disabled. I checked my developer account and found that about 20% of the notifcations failed to be delivered. In the endpoint details, I see that most of the failures are UnknownHostException. I re-enabled my endpoint and am seeing the same behavior.
Can you provide more details about the failures? That would be helpful to determine if the problem is on my end or Fitbit's end or somewhere in the hops between us.
Thanks
05-07-2015 07:18
05-07-2015 07:18
Same here. Received disabled API subscriber for my app at 5:17 AM this morning (CST). I'm still seeing SocketExceptions and UnknownHostExceptions pretty frequently. We didn't deploy anything to production in the last day. This had been working flawlesslessy for at least a few months.
App is https://matchup.io
Thanks -
John
05-07-2015 07:28 - edited 05-07-2015 07:28
05-07-2015 07:28 - edited 05-07-2015 07:28
I got same message, and am seing UnknownHostException in my status also.
05-07-2015 07:56
05-07-2015 07:56
I just want to chime in that our app, too, was disable at 6:13am and I am seeing quite a few "UnknownHostExceptions" in our app's log in my developer account. I have traced into our endpoint from several cities w/o any drops, and I don't see any resolution failures in our DNS servers -- I'm not sure what else to look at.
What information would be helpful?
05-07-2015 08:37
05-07-2015 08:37
Confirmed.
Working on respoving issue.
05-07-2015 08:55 - edited 05-07-2015 09:06
05-07-2015 08:55 - edited 05-07-2015 09:06
Issue had been resolved now.
If you application has been disabled due to this issue please go ahead and enable it back.
05-07-2015 08:58
05-07-2015 08:58
Confirmed. Error rate is falling.
05-07-2015 09:02
05-07-2015 09:02
Perfect, thanks!