1	00:16:38.359	'23221917': ping failed
1	00:16:38.452	'23221917': ping failed
1	00:16:40.093	'23221917': datacenter connecting failed [6]
0	00:16:41.468	'23221917': login on FOREX.comGlobalCN-Live 118 through London Live SH5 (DC18-1) (ping: 209.56 ms)
0	00:16:43.937	'23221917': login datacenter on FOREX.comGlobalCN-Live 118 through London Live SH5 (DC18-1) (ping: 209.56 ms)
0	00:16:45.265	'23221917': previous successful authorization performed from 152.32.252.153
1	00:55:13.251	'23221917': ping failed
1	00:55:13.720	'23221917': datacenter connecting failed [6]
0	00:55:14.767	'23221917': login on FOREX.comGlobalCN-Live 118 through London Live SH5 (DC18-2) (ping: 209.40 ms)
0	00:55:17.189	'23221917': login datacenter on FOREX.comGlobalCN-Live 118 through London Live SH5 (DC18-2) (ping: 209.40 ms)
0	00:55:18.345	'23221917': previous successful authorization performed from 152.32.252.153
0	00:55:22.470	'23221917': auto connecting to a better access point London Live Azure (DC18-1) (ping is 192.05 ms)
0	00:55:23.251	'23221917': login on FOREX.comGlobalCN-Live 118 through London Live Azure (DC18-1) (ping: 192.05 ms)
0	00:55:24.767	'23221917': login datacenter on FOREX.comGlobalCN-Live 118 through London Live Azure (DC18-1) (ping: 192.05 ms)
0	00:55:25.454	'23221917': previous successful authorization performed from 152.32.252.153
1	01:45:16.742	'23221917': datacenter connecting failed [6]
0	01:45:31.149	'23221917': login on FOREX.comGlobalCN-Live 118 through London Live SH5 (DC18-1) (ping: 204.64 ms)
0	01:45:33.555	'23221917': login datacenter on FOREX.comGlobalCN-Live 118 through London Live SH5 (DC18-1) (ping: 204.64 ms)
0	01:45:34.695	'23221917': previous successful authorization performed from 152.32.252.153