0	01:51:28.647	'5002952': login on RoboForex-Pro-2 through DataCenter Europe #4 (ping: 274.22 ms)
0	01:51:31.210	'5002952': login datacenter on RoboForex-Pro-2 through DataCenter Europe #4 (ping: 274.22 ms)
0	01:51:32.194	'5002952': previous successful authorization performed from 103.233.11.57
0	01:51:51.398	'5002952': auto connecting to a better access point DataCenter Hong Kong (ping is 195.55 ms)
0	01:51:52.445	'5002952': login on RoboForex-Pro-2 through DataCenter Hong Kong (ping: 195.55 ms)
0	01:51:53.898	'5002952': login datacenter on RoboForex-Pro-2 through DataCenter Hong Kong (ping: 195.55 ms)
0	01:51:54.383	'5002952': previous successful authorization performed from 103.233.11.57
1	03:54:39.657	'5002952': ping failed
1	03:54:39.673	'5002952': datacenter connecting failed [6]
0	03:55:23.081	'5002952': login on RoboForex-Pro-2 through DataCenter Europe #5 (ping: 297.64 ms)
0	03:55:26.316	'5002952': login datacenter on RoboForex-Pro-2 through DataCenter Europe #5 (ping: 297.64 ms)
0	03:55:27.300	'5002952': previous successful authorization performed from 103.233.11.57
0	03:55:46.129	'5002952': auto connecting to a better access point DataCenter Hong Kong (ping is 195.53 ms)
0	03:55:46.895	'5002952': login on RoboForex-Pro-2 through DataCenter Hong Kong (ping: 195.53 ms)
0	03:55:48.333	'5002952': login datacenter on RoboForex-Pro-2 through DataCenter Hong Kong (ping: 195.53 ms)
0	03:55:48.848	'5002952': previous successful authorization performed from 103.233.11.57
1	05:58:27.966	'5002952': datacenter connecting failed [6]
0	05:59:11.093	'5002952': login on RoboForex-Pro-2 through DataCenter Europe #4 (ping: 268.09 ms)
0	05:59:13.406	'5002952': login datacenter on RoboForex-Pro-2 through DataCenter Europe #4 (ping: 268.09 ms)
0	05:59:14.328	'5002952': previous successful authorization performed from 103.233.11.57
0	05:59:32.922	'5002952': auto connecting to a better access point DataCenter Hong Kong (ping is 195.31 ms)
0	05:59:33.813	'5002952': login on RoboForex-Pro-2 through DataCenter Hong Kong (ping: 195.31 ms)
0	05:59:35.376	'5002952': login datacenter on RoboForex-Pro-2 through DataCenter Hong Kong (ping: 195.31 ms)
0	05:59:35.938	'5002952': previous successful authorization performed from 103.233.11.57
1	10:06:06.928	'5002952': ping failed
1	10:06:06.944	'5002952': datacenter connecting failed [6]
0	10:06:53.055	'5002952': login on RoboForex-Pro-2 through DataCenter Europe #3 (ping: 268.37 ms)
0	10:06:55.743	'5002952': login datacenter on RoboForex-Pro-2 through DataCenter Europe #3 (ping: 268.37 ms)
0	10:06:56.587	'5002952': previous successful authorization performed from 103.233.11.57
0	10:07:15.369	'5002952': auto connecting to a better access point DataCenter Hong Kong (ping is 195.41 ms)
0	10:07:16.228	'5002952': login on RoboForex-Pro-2 through DataCenter Hong Kong (ping: 195.41 ms)
0	10:07:17.728	'5002952': login datacenter on RoboForex-Pro-2 through DataCenter Hong Kong (ping: 195.41 ms)
0	10:07:18.338	'5002952': previous successful authorization performed from 103.233.11.57
0	12:10:42.255	'5002952': login on RoboForex-Pro-2 through DataCenter Europe #5 (ping: 279.24 ms)
0	12:10:44.817	'5002952': login datacenter on RoboForex-Pro-2 through DataCenter Europe #5 (ping: 279.24 ms)
0	12:10:45.739	'5002952': previous successful authorization performed from 103.233.11.57
0	12:11:04.318	'5002952': auto connecting to a better access point DataCenter Hong Kong (ping is 195.47 ms)
0	12:11:05.162	'5002952': login on RoboForex-Pro-2 through DataCenter Hong Kong (ping: 195.47 ms)
0	12:11:06.646	'5002952': login datacenter on RoboForex-Pro-2 through DataCenter Hong Kong (ping: 195.47 ms)
0	12:11:07.162	'5002952': previous successful authorization performed from 103.233.11.57
1	14:13:52.405	'5002952': ping failed
1	14:13:52.421	'5002952': datacenter connecting failed [6]
0	14:14:35.486	'5002952': login on RoboForex-Pro-2 through DataCenter Europe #4 (ping: 271.06 ms)
0	14:14:39.001	'5002952': login datacenter on RoboForex-Pro-2 through DataCenter Europe #4 (ping: 271.06 ms)
0	14:14:39.876	'5002952': previous successful authorization performed from 103.233.11.57
0	14:15:10.706	'5002952': auto connecting to a better access point DataCenter Hong Kong (ping is 195.53 ms)
0	14:15:11.690	'5002952': login on RoboForex-Pro-2 through DataCenter Hong Kong (ping: 195.53 ms)
0	14:15:13.175	'5002952': login datacenter on RoboForex-Pro-2 through DataCenter Hong Kong (ping: 195.53 ms)
0	14:15:13.691	'5002952': previous successful authorization performed from 103.233.11.57
1	16:17:38.902	'5002952': ping failed
1	16:17:38.917	'5002952': datacenter connecting failed [6]
0	16:18:22.154	'5002952': login on RoboForex-Pro-2 through DataCenter Europe #5 (ping: 293.44 ms)
0	16:18:25.216	'5002952': login datacenter on RoboForex-Pro-2 through DataCenter Europe #5 (ping: 293.44 ms)
0	16:18:26.201	'5002952': previous successful authorization performed from 103.233.11.57
0	16:18:48.014	'5002952': auto connecting to a better access point DataCenter Hong Kong (ping is 195.57 ms)
0	16:18:48.921	'5002952': login on RoboForex-Pro-2 through DataCenter Hong Kong (ping: 195.57 ms)
0	16:18:50.421	'5002952': login datacenter on RoboForex-Pro-2 through DataCenter Hong Kong (ping: 195.57 ms)
0	16:18:50.936	'5002952': previous successful authorization performed from 103.233.11.57
1	22:29:07.762	'5002952': ping failed
1	22:29:07.778	'5002952': datacenter connecting failed [6]
1	22:29:29.654	MQL5.community: authorization failed
0	22:29:54.014	'5002952': login on RoboForex-Pro-2 through DataCenter Europe #2 (ping: 304.13 ms)
0	22:29:56.749	'5002952': login datacenter on RoboForex-Pro-2 through DataCenter Europe #2 (ping: 304.13 ms)
0	22:29:57.733	'5002952': previous successful authorization performed from 103.233.11.57
0	22:30:21.469	'5002952': auto connecting to a better access point DataCenter Hong Kong (ping is 195.39 ms)
0	22:30:22.313	'5002952': login on RoboForex-Pro-2 through DataCenter Hong Kong (ping: 195.39 ms)
0	22:30:23.766	'5002952': login datacenter on RoboForex-Pro-2 through DataCenter Hong Kong (ping: 195.39 ms)
0	22:30:24.282	'5002952': previous successful authorization performed from 103.233.11.57