api.fitbit.com timeouts/very long response times

[RARankin]

We've been experiencing a large amount of timeouts when calling api.fitbit.com.  This started back on 9/4 and lasted about 6 hours, then started again yesterday with larger and larger gaps of calls failing, and has been on and off all day today.   We are still receiving webhooks, but are having issues pulling the related data. 

I don't have a specific user to test on as I can make a call, it'll fail, and then make the same call with data being returned.  

Andrew

[Gordon-C]

Hi @RARankin 

We are aware of some latency issues with the Activity endpoints.   Would you please let me know which endpoints are slow to provide a response?

[HenryParadiz]

Hi @Gordon-C -

We have been trying to get a hold of John from Fitbit about this same problem for about a week now. No response. We are hitting this endpoint: 

https://api.fitbit.com/1/user/USERID/activities/distance/date/2024-xx-xx/2024-xx-xx.json

[RARankin]

Hey Gordon - 

I don't think it was limited to a specific endpoint for us.  I could even curl without a path and I'd get a few quick responses and then one that took 40 seconds.   At the moment it is behaving, it recovered around 5:30EST on the 10th.

Thanks,
Andrew

[RARankin]

A bit more from our APM; again not limited to activities, but did include times from that endpoint. 

[MCaruso]

This is still a major issue for us. We have upwards of 80k users for whom we are receiving no new data due to timeouts and this has been ongoing now for over a week. Can we have an update?

We are hitting this endpoint: 

https://api.fitbit.com/1/user/USERID/activities/distance/date/2024-xx-xx/2024-xx-xx.json