504 and 530 Error Codes returned from API

[SteveWT]

We have been experiencing intermittent api errors. The error codes are 504, 530 and 500. Anyone else seeing this? This together with the refresh token bug that's been happening since June we have been very frustrated with Fitbit's support and communications regarding these issues. Can someone from Fitbit escalate these issues and give us an update or a timeline on fixes. Our business relies on the api's to be reliable. 

[aarondcoleman]

Hey @SteveWT we were experiencing the same thing. At about 2:30pm Pacific Time on Friday Oct 13th it all of a sudden seems to have gone away and all our connections behaved normally. Did you see the same thing?

[SteveWT]

Its happening again, it is quite frequent 

[IoanbsuFitbit]

SteveWT, can you please provide more details on what endpoints produce 5xx errors, and also, if you have access to the request id please post it as well. It will help us to triage the issue.

[aarondcoleman]

@IoanbsuFitbit I posted a couple here: https://community.fitbit.com/t5/Web-API-Development/Intermittent-HTTP-Connection-Failures/m-p/224280...

As we were experiencing the same thing. I can gather more if need be.

--Aaron

[IoanbsuFitbit]

Can you also post the endpoints that generates such responses?

[SteveWT]

What do you mean by endpoint? 

[IoanbsuFitbit]

So, the 504 and 530 error status codes you see as the response to the request that you make against specific endpoint. I'm wondering how those requests look like?

For example in request like this 

curl -H "Authorization:valid header" https://api.fitbit.com/1/user/-/profile.json

the endpoint is https://api.fitbit.com/1/user/-/profile.json, or just /1/user/-/profile.json.

[IoanbsuFitbit]

Update in regards to 530.

We don't have evidence that 530 were generated by Fitbit's API. We are working with our CDN to figure out why 530 responses have been generated.