1	07:55:15.595	'38635536': datacenter connecting failed [2]
1	07:55:15.626	'38635536': connect failed [Ò»°ã´íÎó]
0	07:55:42.626	'38635536': login on GTCGlobalSA-Live 1 through Data Center HK1_EX (ping: 171.23 ms)
0	07:55:44.392	'38635536': login datacenter on GTCGlobalSA-Live 1 through Data Center HK1_EX (ping: 171.23 ms)
0	07:55:45.392	'38635536': previous successful authorization performed from 152.32.252.153
0	07:56:34.704	'38635536': auto connecting to a better access point Data Center HK3 (ping is 172.59 ms)
0	07:56:35.407	'38635536': login on GTCGlobalSA-Live 1 through Data Center HK3 (ping: 172.59 ms)
0	07:56:36.548	'38635536': login datacenter on GTCGlobalSA-Live 1 through Data Center HK3 (ping: 172.59 ms)
0	07:56:37.126	'38635536': previous successful authorization performed from 152.32.252.153
1	20:05:12.816	'38635536': datacenter connecting failed [6]
1	20:05:12.862	'38635536': connect failed [Ò»°ã´íÎó]
0	20:05:34.612	'38635536': login on GTCGlobalSA-Live 1 through Data Center DU_EX (ping: 299.32 ms)
0	20:05:37.847	'38635536': login datacenter on GTCGlobalSA-Live 1 through Data Center DU_EX (ping: 299.32 ms)
0	20:05:38.722	'38635536': previous successful authorization performed from 152.32.252.153
0	20:06:29.300	'38635536': auto connecting to a better access point Data Center HK3 (ping is 168.68 ms)
0	20:06:29.956	'38635536': login on GTCGlobalSA-Live 1 through Data Center HK3 (ping: 168.68 ms)
0	20:06:31.097	'38635536': login datacenter on GTCGlobalSA-Live 1 through Data Center HK3 (ping: 168.68 ms)
0	20:06:31.675	'38635536': previous successful authorization performed from 152.32.252.153