12-04-2015 08:46
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report this post

12-04-2015 08:46
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report this post
Sometimes api.fitbit.com resolves to 104.16.66.50 and sometimes it resolves to 104.16.65.50. Attempts to connect to 104.16.65.50 on port 443 have been timing out since yesterday afternoon, only from one of my hosts.
nslookup returns the following.
$ nslookup api.fitbit.com
Non-authoritative answer:
api.fitbit.com canonical name = api.fitbit.com.cdn.cloudflare.net.
Name: api.fitbit.com.cdn.cloudflare.net
Address: 104.16.66.50
Name: api.fitbit.com.cdn.cloudflare.net
Address: 104.16.65.50
This always works, when api.fitbit.com resolves to .66
$ telnet api.fitbit.com 443
This never works, when api.fitbit.com resolves to .65
$ telnet api.fitbit.com 443
12-04-2015 10:25
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report this post



12-04-2015 10:25
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report this post
@John-S: Are you still experiencing this problem? I'm able to connect to 104.16.65.50 from three different ISPs.

12-04-2015 10:37 - last edited on 01-19-2016 11:48 by JeremiahFitbit
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report this post

12-04-2015 10:37 - last edited on 01-19-2016 11:48 by JeremiahFitbit
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report this post
Yes, still experiencing the problem.
$ date
Fri Dec 4 12:29:08 CST 2015
worked
$ telnet 104.16.65.50 443
Trying 104.16.65.50...
Connected to 104.16.65.50.
Escape character is '^]'.
5 seconds later, did not work
$ telnet 104.16.65.50 443
Trying 104.16.65.50...
5 seconds later, still not working
$ telnet 104.16.65.50 443
Trying 104.16.65.50...
1 minute later, works again
$ telnet 104.16.65.50 443
Trying 104.16.65.50...
Connected to 104.16.65.50.
a few seconds later, timeouts again.
Can you confirm a firewall or IDS is not blocking traffic? I emailed you earlier today with my source IP address, application names, and client IDs.
Edit: removed email address

01-18-2016 23:21
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report this post

01-18-2016 23:21
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report this post
I seeing the same thing. After tracing the requests, it appears the cloudfare is putting up a capatcha screen (i.e. go to https://client.fitbit.com/tracker/client/message in your browser) - even if you set pass the capatcha and it sets the cookie in the browser, the app or my phone on wifi will continue to fail as cloudflare is blocking the connection.

01-19-2016 11:37
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report this post



01-19-2016 11:37
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report this post
@goodes: If you're making a high volume of requests, CloudFlare may do this. Contact us privately and we can look into it.

