1	01:50:45.551	'877844': ping failed
1	01:50:45.567	'877844': datacenter connecting failed [6]
0	01:51:29.835	'877844': login on Tri-Real through Real - London (ping: 590.88 ms)
0	01:51:35.788	'877844': login datacenter on Tri-Real through Real - London (ping: 590.88 ms)
0	01:51:37.257	'877844': previous successful authorization performed from 103.233.11.57
0	01:51:58.149	'877844': auto connecting to a better access point Real - Hong Kong (ping is 6.91 ms)
0	01:51:58.836	'877844': login on Tri-Real through Real - Hong Kong (ping: 6.91 ms)
0	01:51:59.227	'877844': login datacenter on Tri-Real through Real - Hong Kong (ping: 6.91 ms)
0	01:51:59.555	'877844': previous successful authorization performed from 103.233.11.57
0	03:55:19.394	'877844': login on Tri-Real through Real - Seoul (ping: 160.58 ms)
0	03:55:21.941	'877844': login datacenter on Tri-Real through Real - Seoul (ping: 160.58 ms)
0	03:55:22.628	'877844': previous successful authorization performed from 103.233.11.57
0	03:55:44.160	'877844': auto connecting to a better access point Real - Hong Kong (ping is 6.46 ms)
0	03:55:44.864	'877844': login on Tri-Real through Real - Hong Kong (ping: 6.46 ms)
0	03:55:45.239	'877844': login datacenter on Tri-Real through Real - Hong Kong (ping: 6.46 ms)
0	03:55:45.676	'877844': previous successful authorization performed from 103.233.11.57
0	05:59:08.328	'877844': login on Tri-Real through Real - Seoul (ping: 162.13 ms)
0	05:59:10.359	'877844': login datacenter on Tri-Real through Real - Seoul (ping: 162.13 ms)
0	05:59:10.953	'877844': previous successful authorization performed from 103.233.11.57
0	05:59:32.157	'877844': auto connecting to a better access point Real - Hong Kong (ping is 6.62 ms)
0	05:59:32.844	'877844': login on Tri-Real through Real - Hong Kong (ping: 6.62 ms)
0	05:59:33.204	'877844': login datacenter on Tri-Real through Real - Hong Kong (ping: 6.62 ms)
0	05:59:33.532	'877844': previous successful authorization performed from 103.233.11.57
1	10:06:04.756	'877844': ping failed
1	10:06:04.772	'877844': datacenter connecting failed [6]
0	10:06:57.790	'877844': login on Tri-Real through Real - London (ping: 561.22 ms)
0	10:07:01.884	'877844': login datacenter on Tri-Real through Real - London (ping: 561.22 ms)
0	10:07:03.118	'877844': previous successful authorization performed from 103.233.11.57
0	10:07:23.150	'877844': auto connecting to a better access point Real - Hong Kong (ping is 6.54 ms)
0	10:07:23.885	'877844': login on Tri-Real through Real - Hong Kong (ping: 6.54 ms)
0	10:07:24.275	'877844': login datacenter on Tri-Real through Real - Hong Kong (ping: 6.54 ms)
0	10:07:24.603	'877844': previous successful authorization performed from 103.233.11.57
1	12:09:59.081	'877844': datacenter connecting failed [6]
0	12:10:42.598	'877844': login on Tri-Real through Real - Seoul (ping: 176.26 ms)
0	12:10:45.114	'877844': login datacenter on Tri-Real through Real - Seoul (ping: 176.26 ms)
0	12:10:45.645	'877844': previous successful authorization performed from 103.233.11.57
0	12:11:07.162	'877844': auto connecting to a better access point Real - Hong Kong (ping is 6.50 ms)
0	12:11:07.865	'877844': login on Tri-Real through Real - Hong Kong (ping: 6.50 ms)
0	12:11:08.256	'877844': login datacenter on Tri-Real through Real - Hong Kong (ping: 6.50 ms)
0	12:11:08.615	'877844': previous successful authorization performed from 103.233.11.57
0	14:14:32.220	'877844': login on Tri-Real through Real - Seoul (ping: 170.22 ms)
0	14:14:35.267	'877844': login datacenter on Tri-Real through Real - Seoul (ping: 170.22 ms)
0	14:14:36.345	'877844': previous successful authorization performed from 103.233.11.57
0	14:14:58.159	'877844': auto connecting to a better access point Real - Hong Kong (ping is 6.70 ms)
0	14:14:58.815	'877844': login on Tri-Real through Real - Hong Kong (ping: 6.70 ms)
0	14:14:59.221	'877844': login datacenter on Tri-Real through Real - Hong Kong (ping: 6.70 ms)
0	14:14:59.549	'877844': previous successful authorization performed from 103.233.11.57
0	16:18:24.232	'877844': login on Tri-Real through Real - Seoul (ping: 169.91 ms)
0	16:18:56.218	'877844': login datacenter on Tri-Real through Real - Seoul (ping: 169.91 ms)
0	16:18:57.046	'877844': previous successful authorization performed from 103.233.11.57
0	16:19:22.157	'877844': auto connecting to a better access point Real - Hong Kong (ping is 6.80 ms)
0	16:19:22.891	'877844': login on Tri-Real through Real - Hong Kong (ping: 6.80 ms)
0	16:19:23.235	'877844': login datacenter on Tri-Real through Real - Hong Kong (ping: 6.80 ms)
0	16:19:23.610	'877844': previous successful authorization performed from 103.233.11.57
1	20:34:15.182	'877844': ping failed
1	20:34:15.198	'877844': datacenter connecting failed [6]
0	20:34:16.463	'877844': login on Tri-Real through Real - Shanghai (ping: 99.12 ms)
0	20:34:17.651	'877844': login datacenter on Tri-Real through Real - Shanghai (ping: 99.12 ms)
0	20:34:18.714	'877844': previous successful authorization performed from 103.233.11.57
0	20:34:40.183	'877844': auto connecting to a better access point Real - Hong Kong (ping is 6.66 ms)
0	20:34:40.887	'877844': login on Tri-Real through Real - Hong Kong (ping: 6.66 ms)
0	20:34:41.183	'877844': login datacenter on Tri-Real through Real - Hong Kong (ping: 6.66 ms)
0	20:34:41.480	'877844': previous successful authorization performed from 103.233.11.57
0	22:29:52.608	'877844': login on Tri-Real through Real - Seoul (ping: 161.05 ms)
0	22:29:55.171	'877844': login datacenter on Tri-Real through Real - Seoul (ping: 161.05 ms)
0	22:29:55.702	'877844': previous successful authorization performed from 103.233.11.57
0	22:30:23.188	'877844': auto connecting to a better access point Real - Hong Kong (ping is 7.23 ms)
0	22:30:24.172	'877844': login on Tri-Real through Real - Hong Kong (ping: 7.23 ms)
0	22:30:25.438	'877844': login datacenter on Tri-Real through Real - Hong Kong (ping: 7.23 ms)
0	22:30:25.750	'877844': previous successful authorization performed from 103.233.11.57