1	13:09:29.312	'23221917': ping failed
1	13:09:29.327	'23221917': datacenter connecting failed [6]
0	13:09:51.234	'23221917': login on FOREX.comGlobalCN-Live 118 through London Live SH5 (DC18-2) (ping: 239.14 ms)
0	13:09:52.890	'23221917': login datacenter on FOREX.comGlobalCN-Live 118 through London Live SH5 (DC18-2) (ping: 239.14 ms)
0	13:09:54.187	'23221917': previous successful authorization performed from 152.32.215.116
0	13:10:08.499	'23221917': ping to current access point London Live SH5 (DC18-2) is 188.45 ms
1	14:30:43.970	'23221917': connect failed [ûÓÐÁ¬½Ó]
0	14:33:50.970	'23221917': login on FOREX.comGlobalCN-Live 118 through London Live SH5 (DC18-2) (ping: n/a)
0	14:33:59.548	'23221917': login datacenter on FOREX.comGlobalCN-Live 118 through London Live SH5 (DC18-2) (ping: n/a)
0	14:34:00.314	'23221917': previous successful authorization performed from 152.32.215.116
0	14:34:16.517	'23221917': ping to current access point London Live SH5 (DC18-2) is 269.18 ms
1	22:37:35.472	'23221917': datacenter connecting failed [6]
0	22:38:19.941	'23221917': login on FOREX.comGlobalCN-Live 118 through London Live SH5 (DC18-1) (ping: 275.37 ms)
0	22:39:26.895	'23221917': login on FOREX.comGlobalCN-Live 118 through London Live SH5 (DC18-2) (ping: 269.18 ms)
0	22:40:46.114	'23221917': login datacenter on FOREX.comGlobalCN-Live 118
0	22:41:05.895	'23221917': auto connecting to a better access point London Live INX (DC18-1) (ping is 262.29 ms)
0	22:41:12.458	'23221917': login on FOREX.comGlobalCN-Live 118 through London Live INX (DC18-1) (ping: 262.29 ms)
0	22:41:14.364	'23221917': login datacenter on FOREX.comGlobalCN-Live 118 through London Live INX (DC18-1) (ping: 262.29 ms)
0	22:41:15.301	'23221917': previous successful authorization performed from 152.32.215.116