0	01:00:07.724	'35191254': login on HFMarketsSV-Live Server 4 through Amsterdam 1 (ping: 235.61 ms)
0	01:00:09.646	'35191254': login datacenter on HFMarketsSV-Live Server 4 through Amsterdam 1 (ping: 235.61 ms)
0	01:00:10.459	'35191254': previous successful authorization performed from 103.233.11.57
0	01:00:53.258	'35191254': auto connecting to a better access point Amsterdam 2 (ping is 250.11 ms)
0	01:00:54.352	'35191254': login on HFMarketsSV-Live Server 4 through Amsterdam 2 (ping: 250.11 ms)
0	01:00:56.399	'35191254': login datacenter on HFMarketsSV-Live Server 4 through Amsterdam 2 (ping: 250.11 ms)
0	01:00:57.242	'35191254': previous successful authorization performed from 103.233.11.57
0	03:39:37.720	'35191254': login on HFMarketsSV-Live Server 4 through Amsterdam 2 (ping: 250.11 ms)
1	03:41:00.255	'35191254': datacenter connecting failed [6]
0	03:41:47.367	'35191254': auto connecting to a better access point Hong Kong 1 (ping is 249.01 ms)
0	03:41:57.570	'35191254': login on HFMarketsSV-Live Server 4 through Amsterdam 3 (ping: n/a)
0	03:42:26.228	'35191254': login datacenter on HFMarketsSV-Live Server 4 through Amsterdam 3 (ping: n/a)
0	03:42:27.041	'35191254': previous successful authorization performed from 103.233.11.57
0	03:42:59.370	'35191254': ping to current access point Amsterdam 3 is 259.30 ms
1	14:35:17.066	'35191254': ping failed
1	14:35:17.082	'35191254': datacenter connecting failed [6]
0	14:35:18.425	'35191254': login on HFMarketsSV-Live Server 4 through Hong Kong 1 (ping: 248.91 ms)
0	14:35:20.144	'35191254': login datacenter on HFMarketsSV-Live Server 4 through Hong Kong 1 (ping: 248.91 ms)
0	14:35:20.832	'35191254': previous successful authorization performed from 103.233.11.57
0	14:35:54.240	'35191254': ping to current access point Hong Kong 1 is 248.82 ms