1	14:41:53.311	'4130542': ping failed
0	14:41:54.046	'4130542': login on JPMarketsSA-Live through DC-6 (ping: 218.98 ms)
0	14:41:55.780	'4130542': login datacenter on JPMarketsSA-Live through DC-6 (ping: 218.98 ms)
0	14:41:56.327	'4130542': previous successful authorization performed from 152.32.128.46
0	14:42:25.030	'4130542': auto connecting to a better access point DC-1 (ping is 218.80 ms)
0	14:42:25.765	'4130542': login on JPMarketsSA-Live through DC-1 (ping: 218.80 ms)
0	14:42:27.499	'4130542': login datacenter on JPMarketsSA-Live through DC-1 (ping: 218.80 ms)
0	14:42:28.046	'4130542': previous successful authorization performed from 152.32.128.46
1	22:08:17.759	'4130542': datacenter connecting failed [6]
0	22:08:18.508	'4130542': login on JPMarketsSA-Live through DC-2 (ping: 223.97 ms)
0	22:08:20.289	'4130542': login datacenter on JPMarketsSA-Live through DC-2 (ping: 223.97 ms)
0	22:08:20.883	'4130542': previous successful authorization performed from 152.32.128.46
0	22:08:50.177	'4130542': auto connecting to a better access point DC-3 (ping is 233.34 ms)
0	22:08:53.958	'4130542': login on JPMarketsSA-Live through DC-3 (ping: 233.34 ms)
0	22:08:55.848	'4130542': login datacenter on JPMarketsSA-Live through DC-3 (ping: 233.34 ms)
0	22:08:56.442	'4130542': previous successful authorization performed from 152.32.128.46
1	22:36:36.007	'4130542': datacenter connecting failed [6]
0	22:36:36.772	'4130542': login on JPMarketsSA-Live through DC-2 (ping: 225.18 ms)
0	22:36:38.725	'4130542': login datacenter on JPMarketsSA-Live through DC-2 (ping: 225.18 ms)
0	22:36:39.350	'4130542': previous successful authorization performed from 152.32.128.46