1	01:24:14.331	'23221917': ping failed
1	01:24:14.488	'23221917': datacenter connecting failed [6]
0	01:24:15.519	'23221917': login on FOREX.comGlobalCN-Live 118 through London Live INX (DC18-1) (ping: 282.79 ms)
0	01:24:17.956	'23221917': login datacenter on FOREX.comGlobalCN-Live 118 through London Live INX (DC18-1) (ping: 282.79 ms)
0	01:24:19.160	'23221917': previous successful authorization performed from 10.56.128.68
0	01:24:48.066	'23221917': auto connecting to a better access point London Live SH5 (DC18-1) (ping is 248.78 ms)
0	01:24:48.941	'23221917': login on FOREX.comGlobalCN-Live 118 through London Live SH5 (DC18-1) (ping: 248.78 ms)
0	01:24:53.753	'23221917': login datacenter on FOREX.comGlobalCN-Live 118 through London Live SH5 (DC18-1) (ping: 248.78 ms)
0	01:24:54.253	'23221917': previous successful authorization performed from 152.32.252.153
0	09:49:24.644	'23221917': login on FOREX.comGlobalCN-Live 118 through London Live SH5 (DC18-1) (ping: 248.78 ms)
0	09:49:28.066	'23221917': login datacenter on FOREX.comGlobalCN-Live 118 through London Live SH5 (DC18-1) (ping: 248.78 ms)
0	09:49:29.785	'23221917': previous successful authorization performed from 152.32.252.153
0	09:49:37.441	'23221917': auto connecting to a better access point London Live SH5 (DC18-2) (ping is 247.90 ms)
0	09:49:38.597	'23221917': login on FOREX.comGlobalCN-Live 118 through London Live SH5 (DC18-2) (ping: 247.90 ms)
0	09:49:43.519	'23221917': login datacenter on FOREX.comGlobalCN-Live 118 through London Live SH5 (DC18-2) (ping: 247.90 ms)
0	09:49:44.628	'23221917': previous successful authorization performed from 152.32.252.153
1	10:05:34.753	'23221917': datacenter connecting failed [6]
0	10:05:49.191	'23221917': login on FOREX.comGlobalCN-Live 118 through London Live SH5 (DC18-1) (ping: 275.77 ms)
0	10:05:57.519	'23221917': login datacenter on FOREX.comGlobalCN-Live 118 through London Live SH5 (DC18-1) (ping: 275.77 ms)
0	10:05:58.613	'23221917': previous successful authorization performed from 152.32.252.153
0	13:47:43.144	'23221917': login on FOREX.comGlobalCN-Live 118 through London Live SH5 (DC18-1) (ping: 275.77 ms)
0	13:47:53.785	'23221917': login datacenter on FOREX.comGlobalCN-Live 118 through London Live SH5 (DC18-1) (ping: 275.77 ms)
0	13:47:56.863	'23221917': ping to current access point London Live SH5 (DC18-1) is 249.15 ms
0	13:47:58.753	'23221917': previous successful authorization performed from 152.32.252.153
1	14:17:06.097	'23221917': datacenter connecting failed [6]
0	14:17:10.003	'23221917': login on FOREX.comGlobalCN-Live 118 through London Live SH5 (DC18-2) (ping: 249.01 ms)
0	14:17:20.769	'23221917': login datacenter on FOREX.comGlobalCN-Live 118 through London Live SH5 (DC18-2) (ping: 249.01 ms)
0	14:17:21.425	'23221917': previous successful authorization performed from 152.32.252.153
1	15:18:22.972	'23221917': datacenter connecting failed [6]
0	15:18:36.519	'23221917': login on FOREX.comGlobalCN-Live 118 through London Live SH5 (DC18-2) (ping: 249.01 ms)
0	15:19:10.019	'23221917': auto connecting to a better access point London Live Azure (DC18-1) (ping is 277.99 ms)
1	15:19:10.238	'23221917': datacenter connecting failed [2]
0	15:19:16.488	'23221917': login on FOREX.comGlobalCN-Live 118 through London Live Azure (DC18-1) (ping: 277.99 ms)
0	15:19:17.722	'23221917': login datacenter on FOREX.comGlobalCN-Live 118 through London Live Azure (DC18-1) (ping: 277.99 ms)
0	15:19:18.097	'23221917': previous successful authorization performed from 152.32.252.153
1	18:11:07.753	'23221917': datacenter connecting failed [6]
0	18:11:08.378	'23221917': login on FOREX.comGlobalCN-Live 118 through London Live Azure (DC18-1) (ping: 277.99 ms)
0	18:11:10.441	'23221917': login datacenter on FOREX.comGlobalCN-Live 118 through London Live Azure (DC18-1) (ping: 277.99 ms)
0	18:11:10.816	'23221917': previous successful authorization performed from 10.56.128.69
0	18:11:20.472	'23221917': ping to current access point London Live Azure (DC18-1) is 186.59 ms