0	01:00:12.871	'35191254': login on HFMarketsSV-Live Server 4 through Amsterdam 1 (ping: 175.45 ms)
0	01:00:14.511	'35191254': login datacenter on HFMarketsSV-Live Server 4 through Amsterdam 1 (ping: 175.45 ms)
0	01:00:15.027	'35191254': previous successful authorization performed from 101.36.110.43
0	01:00:43.902	'35191254': auto connecting to a better access point Amsterdam 3 (ping is 174.88 ms)
0	01:00:44.558	'35191254': login on HFMarketsSV-Live Server 4 through Amsterdam 3 (ping: 174.88 ms)
0	01:00:46.371	'35191254': login datacenter on HFMarketsSV-Live Server 4 through Amsterdam 3 (ping: 174.88 ms)
0	01:00:46.871	'35191254': previous successful authorization performed from 101.36.110.43
1	14:43:47.962	'35191254': ping failed
0	14:43:48.775	'35191254': login on HFMarketsSV-Live Server 4 through Amsterdam 3 (ping: 174.88 ms)
0	14:43:50.541	'35191254': login datacenter on HFMarketsSV-Live Server 4 through Amsterdam 3 (ping: 174.88 ms)
0	14:43:51.009	'35191254': previous successful authorization performed from 101.36.110.43
0	14:44:08.369	'35191254': ping to current access point Amsterdam 3 is 178.73 ms
1	17:30:18.746	'35191254': ping failed
1	17:30:18.746	'35191254': datacenter connecting failed [6]
0	17:30:19.542	'35191254': login on HFMarketsSV-Live Server 4 through Amsterdam 2 (ping: 179.12 ms)
0	17:30:21.402	'35191254': login datacenter on HFMarketsSV-Live Server 4 through Amsterdam 2 (ping: 179.12 ms)
0	17:30:21.902	'35191254': previous successful authorization performed from 101.36.110.43
0	17:30:38.933	'35191254': ping to current access point Amsterdam 2 is 174.84 ms
1	22:08:14.554	'35191254': datacenter connecting failed [6]
0	22:08:15.398	'35191254': login on HFMarketsSV-Live Server 4 through Amsterdam 3 (ping: 174.35 ms)
0	22:08:17.289	'35191254': login datacenter on HFMarketsSV-Live Server 4 through Amsterdam 3 (ping: 174.35 ms)
0	22:08:17.789	'35191254': previous successful authorization performed from 101.36.110.43
0	22:08:35.335	'35191254': auto connecting to a better access point Amsterdam 2 (ping is 173.74 ms)
0	22:08:36.039	'35191254': login on HFMarketsSV-Live Server 4 through Amsterdam 2 (ping: 173.74 ms)
0	22:08:37.773	'35191254': login datacenter on HFMarketsSV-Live Server 4 through Amsterdam 2 (ping: 173.74 ms)
0	22:08:38.226	'35191254': previous successful authorization performed from 101.36.110.43
1	22:36:19.241	'35191254': ping failed
1	22:36:19.288	'35191254': datacenter connecting failed [6]
0	22:36:20.053	'35191254': login on HFMarketsSV-Live Server 4 through Amsterdam 3 (ping: 178.91 ms)
0	22:36:22.053	'35191254': login datacenter on HFMarketsSV-Live Server 4 through Amsterdam 3 (ping: 178.91 ms)
0	22:36:22.616	'35191254': previous successful authorization performed from 101.36.110.43
1	23:50:31.708	'35191254': datacenter connecting failed [6]
0	23:50:32.537	'35191254': login on HFMarketsSV-Live Server 4 through Amsterdam 1 (ping: 182.63 ms)
0	23:50:34.224	'35191254': login datacenter on HFMarketsSV-Live Server 4 through Amsterdam 1 (ping: 182.63 ms)
0	23:50:34.724	'35191254': previous successful authorization performed from 101.36.110.43
0	23:50:52.287	'35191254': auto connecting to a better access point Amsterdam 2 (ping is 179.32 ms)
0	23:50:52.974	'35191254': login on HFMarketsSV-Live Server 4 through Amsterdam 2 (ping: 179.32 ms)
0	23:50:54.755	'35191254': login datacenter on HFMarketsSV-Live Server 4 through Amsterdam 2 (ping: 179.32 ms)
0	23:50:55.224	'35191254': previous successful authorization performed from 101.36.110.43