1	03:20:20.311	MQL5.community: authorization failed
1	03:20:26.311	MQL5.community: authorization failed
0	03:20:42.202	'5002952': login on RoboForex-Pro-2 through DataCenter Singapore (ping: 265.84 ms)
0	03:20:44.124	'5002952': login datacenter on RoboForex-Pro-2 through DataCenter Singapore (ping: 265.84 ms)
0	03:20:44.656	'5002952': previous successful authorization performed from 103.233.11.58
0	03:21:11.204	'5002952': ping to current access point DataCenter Singapore is 201.93 ms
1	10:25:27.407	MQL5.community: authorization failed
1	10:25:39.455	MQL5.community: authorization failed
0	10:25:41.845	'5002952': login on RoboForex-Pro-2 through DataCenter India (ping: 233.66 ms)
0	10:25:43.799	'5002952': login datacenter on RoboForex-Pro-2 through DataCenter India (ping: 233.66 ms)
0	10:25:44.470	'5002952': previous successful authorization performed from 103.233.11.58
0	10:26:10.331	'5002952': auto connecting to a better access point DataCenter Singapore (ping is 201.85 ms)
0	10:26:11.253	'5002952': login on RoboForex-Pro-2 through DataCenter Singapore (ping: 201.85 ms)
0	10:26:13.175	'5002952': login datacenter on RoboForex-Pro-2 through DataCenter Singapore (ping: 201.85 ms)
0	10:26:13.800	'5002952': previous successful authorization performed from 103.233.11.58
0	17:10:41.166	'5002952': login on RoboForex-Pro-2 through DataCenter Singapore (ping: 201.85 ms)
0	17:10:43.791	'5002952': login datacenter on RoboForex-Pro-2 through DataCenter Singapore (ping: 201.85 ms)
0	17:10:44.525	'5002952': previous successful authorization performed from 103.233.11.58
0	17:11:13.714	'5002952': ping to current access point DataCenter Singapore is 207.24 ms