1	05:07:10.402	'4130542': datacenter connecting failed [6]
1	05:07:11.027	'4130542': connect failed [ûÓÐÁ¬½Ó]
0	05:08:27.255	'4130542': login on JPMarketsSA-Live through DC-2 (ping: n/a)
0	05:08:29.365	'4130542': login datacenter on JPMarketsSA-Live through DC-2 (ping: n/a)
0	05:08:30.005	'4130542': previous successful authorization performed from 152.32.128.46
0	05:09:00.584	'4130542': auto connecting to a better access point DC-6 (ping is 261.90 ms)
0	05:09:04.318	'4130542': login on JPMarketsSA-Live through DC-6 (ping: 261.90 ms)
0	05:09:06.349	'4130542': login datacenter on JPMarketsSA-Live through DC-6 (ping: 261.90 ms)
0	05:09:06.974	'4130542': previous successful authorization performed from 152.32.128.46
1	09:59:17.074	'4130542': ping failed
0	09:59:17.965	'4130542': login on JPMarketsSA-Live through DC-6 (ping: 261.90 ms)
0	09:59:20.026	'4130542': login datacenter on JPMarketsSA-Live through DC-6 (ping: 261.90 ms)
0	09:59:20.666	'4130542': previous successful authorization performed from 152.32.128.46
0	09:59:51.696	'4130542': ping to current access point DC-6 is 265.18 ms
1	11:56:22.357	'4130542': ping failed
0	11:56:23.185	'4130542': login on JPMarketsSA-Live through DC-6 (ping: 265.18 ms)
0	11:56:25.371	'4130542': login datacenter on JPMarketsSA-Live through DC-6 (ping: 265.18 ms)
0	11:56:26.043	'4130542': previous successful authorization performed from 152.32.128.46
0	11:56:56.558	'4130542': auto connecting to a better access point DC-2 (ping is 269.06 ms)
0	11:57:27.916	'4130542': login on JPMarketsSA-Live through DC-1 (ping: 265.60 ms)
0	11:57:30.524	'4130542': login datacenter on JPMarketsSA-Live through DC-1 (ping: 265.60 ms)
0	11:57:31.164	'4130542': previous successful authorization performed from 152.32.128.46