CrazyMoeMew Posted July 6, 2018 Share Posted July 6, 2018 The Gorge servers of tencent were all offline since the morning of today(UTC time). Now the players of my country have to connect to US servers to start a match. The client log is down below: [00:34:50]: THREAD - started 'PingThread' (60852) [00:34:50]: THREAD - started 'PingThread' (60856) [00:34:50]: THREAD - started 'PingThread' (1356) [00:34:50]: THREAD - started 'PingThread' (60888) [00:34:50]: THREAD - started 'PingThread' (61216) [00:34:50]: THREAD - started 'PingThread' (60664) [00:34:50]: THREAD - started 'PingThread' (60008) [00:34:50]: THREAD - started 'PingThread' (60600) [00:34:50]: THREAD - started 'PingThread' (11172) [00:34:50]: THREAD - started 'PingThread' (12896) [00:34:50]: THREAD - started 'PingThread' (58552) [00:34:50]: Ping for aws/us-east-1 (ip: 18.208.227.20) took 211ms [00:34:50]: Ping for aws/ap-northeast-2 (ip: 13.125.228.183) took 231ms [00:34:50]: Ping for aws/us-west-2 (ip: 34.221.170.42) took 235ms [00:34:50]: Ping for aws/ap-southeast-1 (ip: 54.255.242.147) took 260ms [00:34:51]: Ping for aws/ap-southeast-2 (ip: 13.210.177.70) took 307ms [00:34:51]: Ping for aws/eu-west-1 (ip: 54.229.151.154) took 318ms [00:34:51]: Ping for aws/eu-west-3 (ip: 35.180.37.161) took 330ms [00:34:51]: Ping for aws/sa-east-1 (ip: 54.94.208.155) took 320ms [00:34:51]: Ping for aws/eu-central-1 (ip: 52.59.237.208) took 329ms [00:34:53]: Ping timed out; ignoring this pool: tencent/bj3 [00:34:53]: Ping timed out; ignoring this pool: tencent/cd2 [00:34:54]: Cloud Server Session Id is: 8129e85c-615b-4737-8ca0-920ca37e7513 I don't know if Klei can contact Tencent to solve this problem. Link to comment Share on other sites More sharing options...
Recommended Posts
Archived
This topic is now archived and is closed to further replies.
Please be aware that the content of this thread may be outdated and no longer applicable.