If you look at other threads in this forum you'll see that this is a widely known issue, seemingly due to Ancestry carrying maintenance and/or upgrading their servers. This has affected Ancestry performance in general, and also FTM syncing, resulting in frequent Orange warnings and sometimes Red "blocks". This has become progressively worse over the last few days, and although Ancestry said they intended to complete the work by the 31st May, they've acknowledged that they've not managed to do that, and at the moment most of us are getting Red almost all the time. I agree it's really frustrating, but I imagine Ancestry are working hard to resolve it, because bad publicity doesn't do them any favours in the long term. They claim that the work, once finished, will result in better performance than before all this started. I imagine there's always a trade off between cost and performance, what with more source records, more users, and more member trees being added all the time.
To be fair, although it feels like forever, this has really only been a major issue for a few weeks, and prior to that I've found that syncing with the new FTM2017 (and especially after the 23.1 update) has always been fast and reliable. I imagine it will be fixed sooner or later (hopefully sooner!) and after a while we'll probably all forget about it and get back to researching and syncing as before.
To be fair, although it feels like forever, this has really only been a major issue for a few weeks, and prior to that I've found that syncing with the new FTM2017 (and especially after the 23.1 update) has always been fast and reliable. I imagine it will be fixed sooner or later (hopefully sooner!) and after a while we'll probably all forget about it and get back to researching and syncing as before.