1	01:10:06.093	'5002952': ping failed
1	01:10:06.109	'5002952': datacenter connecting failed [6]
0	01:10:30.985	'5002952': login on RoboForex-Pro-2 through DataCenter Hong Kong (ping: 197.28 ms)
0	01:10:32.501	'5002952': login datacenter on RoboForex-Pro-2 through DataCenter Hong Kong (ping: 197.28 ms)
0	01:10:32.985	'5002952': previous successful authorization performed from 103.233.11.57
0	01:11:10.909	'5002952': ping to current access point DataCenter Hong Kong is 196.43 ms
0	04:15:34.320	'5002952': login on RoboForex-Pro-2 through DataCenter Russia (ping: 235.43 ms)
0	04:15:36.382	'5002952': login datacenter on RoboForex-Pro-2 through DataCenter Russia (ping: 235.43 ms)
0	04:15:37.101	'5002952': previous successful authorization performed from 103.233.11.57
0	04:16:05.008	'5002952': auto connecting to a better access point DataCenter Europe #4 (ping is 201.61 ms)
0	04:16:05.930	'5002952': login on RoboForex-Pro-2 through DataCenter Europe #4 (ping: 201.61 ms)
0	04:16:07.774	'5002952': login datacenter on RoboForex-Pro-2 through DataCenter Europe #4 (ping: 201.61 ms)
0	04:16:09.009	'5002952': previous successful authorization performed from 103.233.11.57
1	17:01:43.297	'5002952': datacenter connecting failed [6]
0	17:01:47.297	'5002952': login on RoboForex-Pro-2 through DataCenter Europe #4 (ping: 201.61 ms)
0	17:01:49.782	'5002952': login datacenter on RoboForex-Pro-2 through DataCenter Europe #4 (ping: 201.61 ms)
0	17:01:50.626	'5002952': previous successful authorization performed from 103.233.11.57
0	17:02:09.377	'5002952': auto connecting to a better access point DataCenter Hong Kong (ping is 196.76 ms)
0	17:02:10.299	'5002952': login on RoboForex-Pro-2 through DataCenter Hong Kong (ping: 196.76 ms)
0	17:02:11.877	'5002952': login datacenter on RoboForex-Pro-2 through DataCenter Hong Kong (ping: 196.76 ms)
0	17:02:12.455	'5002952': previous successful authorization performed from 103.233.11.57