1	05:36:47.211	'4130542': datacenter connecting failed [6]
0	05:36:51.008	'4130542': login on JPMarketsSA-Live through DC-6 (ping: 220.93 ms)
0	05:36:53.008	'4130542': login datacenter on JPMarketsSA-Live through DC-6 (ping: 220.93 ms)
0	05:36:53.554	'4130542': previous successful authorization performed from 152.32.128.46
0	05:37:22.067	'4130542': auto connecting to a better access point DC-2 (ping is 227.71 ms)
0	05:37:53.064	'4130542': login on JPMarketsSA-Live through DC-1 (ping: 221.04 ms)
0	05:37:55.970	'4130542': login datacenter on JPMarketsSA-Live through DC-1 (ping: 221.04 ms)
0	05:37:56.548	'4130542': previous successful authorization performed from 152.32.128.46
1	08:05:43.140	'4130542': ping failed
1	08:05:43.155	'4130542': datacenter connecting failed [6]
0	08:05:43.968	'4130542': login on JPMarketsSA-Live through DC-2 (ping: 227.71 ms)
0	08:05:45.733	'4130542': login datacenter on JPMarketsSA-Live through DC-2 (ping: 227.71 ms)
0	08:05:46.280	'4130542': previous successful authorization performed from 152.32.128.46
0	08:06:15.152	'4130542': auto connecting to a better access point DC-6 (ping is 220.34 ms)
0	08:06:15.886	'4130542': login on JPMarketsSA-Live through DC-6 (ping: 220.34 ms)
0	08:06:17.699	'4130542': login datacenter on JPMarketsSA-Live through DC-6 (ping: 220.34 ms)
0	08:06:18.246	'4130542': previous successful authorization performed from 152.32.128.46