Oops, looks like the "Not ready" thing is coming again in China...

Teamviewer now keeps showing 'Not ready. Please check your connection' in China, ISP: China telecom, location e.g. Shanghai, Shenzhen, Nanjing, Hefei...

It happens approximately on this morning(UTC +8), and it also happened back in April this year and that topic was "Cannot connect to Teamviewer server since yesterday".

I got repeated logs as follows:

2017/09/02 17:34:45.166  4112 13308 G1   Activating Router carrier
2017/09/02 17:34:45.539  4112 10548 G1   CKeepAliveClientClient::HandlePing(): success
2017/09/02 17:34:45.539  4112 10548 G1   Resource-Language: en
2017/09/02 17:34:45.540  4112 10548 G1   Activating Router carrier
2017/09/02 17:34:45.540  4112 10548 G1   CProcessCommandHandlerMasterConnect[178]::CreateMasterConnect(): master16.teamviewer.com:5938, Connection 178, proxy=''
2017/09/02 17:34:50.540  4112 10036 G1   CTcpConnectionBase[178]::HandleConnectTimeout(). Connect timed out to master16.teamviewer.com:5938
2017/09/02 17:34:50.540  4112 10548 G1!  CProcessCommandHandlerMasterConnect[178]::HandleMasterConnect(): MasterConnect to 0.0.0.0 failed
2017/09/02 17:34:50.540  4112 12640 G1!  CTcpConnectionBase[178]::HandleConnect: Connect aborted to dest-ip master16.teamviewer.com:5938 with error system:995.
2017/09/02 17:34:50.541  4112 10548 G1!!!Connect to Master master16.teamviewer.com / 185.188.32.6 failed!
2017/09/02 17:34:50.541  4112 10548 G1!! CMasterConnectorAsio::HandleMasterResponseLogin(): MasterConnect failed. ErrorCode=10
2017/09/02 17:34:53.542  4112 12640 G1   Activating Router carrier
2017/09/02 17:34:53.901  4112 10036 G1   CKeepAliveClientClient::HandlePing(): success
2017/09/02 17:34:53.901  4112 10036 G1   Resource-Language: en
2017/09/02 17:34:53.901  4112 10036 G1   Activating Router carrier
2017/09/02 17:34:53.901  4112 10036 G1   CProcessCommandHandlerMasterConnect[180]::CreateMasterConnect(): master7.teamviewer.com:5938, Connection 180, proxy=''
2017/09/02 17:34:58.903  4112 12408 G1   CTcpConnectionBase[180]::HandleConnectTimeout(). Connect timed out to master7.teamviewer.com:5938
2017/09/02 17:34:58.903  4112 13308 G1!  CProcessCommandHandlerMasterConnect[180]::HandleMasterConnect(): MasterConnect to 0.0.0.0 failed
2017/09/02 17:34:58.903  4112 10548 G1!  CTcpConnectionBase[180]::HandleConnect: Connect aborted to dest-ip master7.teamviewer.com:5938 with error system:995.
2017/09/02 17:34:58.904  4112 13308 G1!!!Connect to Master master7.teamviewer.com / 185.188.32.1 failed!
2017/09/02 17:34:58.904  4112 13308 G1!! CMasterConnectorAsio::HandleMasterResponseLogin(): MasterConnect failed. ErrorCode=10
2017/09/02 17:35:01.904  4112 10548 G1   Activating Router carrier
2017/09/02 17:35:02.245  4112 12408 G1   CKeepAliveClientClient::HandlePing(): success
2017/09/02 17:35:02.245  4112 12408 G1   Resource-Language: en
2017/09/02 17:35:02.245  4112 12408 G1   Activating Router carrier
2017/09/02 17:35:02.245  4112 12408 G1   CProcessCommandHandlerMasterConnect[182]::CreateMasterConnect(): master4.teamviewer.com:5938, Connection 182, proxy=''
2017/09/02 17:35:07.246  4112 10036 G1   CTcpConnectionBase[182]::HandleConnectTimeout(). Connect timed out to master4.teamviewer.com:5938
2017/09/02 17:35:07.246  4112 13308 G1!  CProcessCommandHandlerMasterConnect[182]::HandleMasterConnect(): MasterConnect to 0.0.0.0 failed
2017/09/02 17:35:07.246  4112 12640 G1!  CTcpConnectionBase[182]::HandleConnect: Connect aborted to dest-ip master4.teamviewer.com:5938 with error system:995.
2017/09/02 17:35:07.247  4112 13308 G1!!!Connect to Master master4.teamviewer.com / 185.188.32.4 failed!
2017/09/02 17:35:07.253  4112 13308 G1!! CMasterConnectorAsio::HandleMasterResponseLogin(): MasterConnect failed. ErrorCode=10

It's difficult to tell if it's coming again for sure, but... IMHO it is... most likely.

I hope it would self-recovers within this weekend.