1	05:07:04.670	'4130542': connect failed [ûÓÐÁ¬½Ó]
0	05:08:32.052	'4130542': login on JPMarketsSA-Live through DC-2 (ping: n/a)
0	05:08:34.114	'4130542': login datacenter on JPMarketsSA-Live through DC-2 (ping: n/a)
0	05:08:34.739	'4130542': previous successful authorization performed from 152.32.128.46
0	05:09:03.224	'4130542': auto connecting to a better access point DC-1 (ping is 234.46 ms)
0	05:09:03.942	'4130542': login on JPMarketsSA-Live through DC-1 (ping: 234.46 ms)
0	05:09:05.817	'4130542': login datacenter on JPMarketsSA-Live through DC-1 (ping: 234.46 ms)
0	05:09:06.380	'4130542': previous successful authorization performed from 152.32.128.46
1	05:18:26.508	'4130542': ping failed
1	05:18:26.508	'4130542': datacenter connecting failed [6]
0	05:18:27.243	'4130542': login on JPMarketsSA-Live through DC-6 (ping: 235.04 ms)
0	05:18:29.196	'4130542': login datacenter on JPMarketsSA-Live through DC-6 (ping: 235.04 ms)
0	05:18:29.805	'4130542': previous successful authorization performed from 152.32.128.46
1	22:00:26.114	'4130542': ping failed
0	22:01:09.067	'4130542': login on JPMarketsSA-Live through DC-3 (ping: 289.27 ms)
0	22:01:11.349	'4130542': login datacenter on JPMarketsSA-Live through DC-3 (ping: 289.27 ms)
0	22:01:12.036	'4130542': previous successful authorization performed from 152.32.128.46
0	22:01:43.536	'4130542': ping to current access point DC-3 is 288.87 ms