Cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

API failures starting at 615AM on 5/7/15

ANSWERED

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?

Best Answer
1 BEST ANSWER

Accepted Solutions

Issue had been resolved now.

If you application has been disabled due to this issue please go ahead and enable it back.

Ivan Bahdanau
Senior Software Developer at Fitbit

View best answer in original post

Best Answer
14 REPLIES 14

Same issues here..

Best Answer

I'm experiencing the same issue

Best Answer

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.

Best Answer

Confirmed for cafewell.com too.

Best Answer


PS: I've informed the Fitbit team, let's wait and see with what they come up.

Best Answer
Best Answer
0 Votes

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

Best Answer
0 Votes

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 

Best Answer
0 Votes

I got same message, and am seing UnknownHostException in my status also.

Best Answer
0 Votes

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?

Best Answer

Confirmed. 

Working on respoving issue.

Ivan Bahdanau
Senior Software Developer at Fitbit
Best Answer
0 Votes

Issue had been resolved now.

If you application has been disabled due to this issue please go ahead and enable it back.

Ivan Bahdanau
Senior Software Developer at Fitbit
Best Answer

Confirmed. Error rate is falling.

Best Answer
0 Votes

Perfect, thanks!

Best Answer
0 Votes