Combine all syncing problems in one topic

[SunsetRunner]

By now you, Fitbit team, should have combined all syncing issues into a single topic. At the moment syncing issues are spread over iOS, Android, Windows 10 apps forums, and product forums from Charge HR to Ionic. People think that it is a problem with their device, although it is that Fitbit is failing to acknowledge officially that there is a problem with the communication with the server (they admit it hesitantly over the phone).
For example, one of workarounds is to change user's IP address in some way (switch from WiFi to radio data link or vice versa), use a VPN, or ask you Internet Service Provider to change your IP address, or, as a last resort, get a free WiFi connection somewhere.

I had problems with my old Charge 2, got new a Charge 2 and then Charge 3 (complimentary) replacement, sent them back - they did not work for the sole reason: Fitbit's cloud server of choice cloudflare.net was blocking my IP address. I guess it blocks some IP addresses randomly, no need to check your IP address reputation. Having said that I admit that in some cases the problem is with pairing via Bluetooth.

But keep in mind that the last step that the app does after pairing is accessing the server, and this is where it fails making you think that the problem was with pairing.

[LanuzaFitbit]

Hello @SunsetRunner.

Thanks for sharing your feedback on the matter. 

It is important to mention that not all syncing issues are necessarily the same and thus they can't all be treated as the exact same. When there are generalized issues they are usually merged into a single topic so that it can be easily updated and to serve as a hub for users experiencing that issue with those specifications. 

Feel free to reach out with any questions.

[SunsetRunner]

@LanuzaFitbitWith all due respect I am planning to go well beyond this forum: you guys fail to admit the problem with cloudflare.net.