1	11:24:09.967	MQL5.community: authorization failed
0	11:24:40.313	'877844': login on Tri-Real through Real - Seoul (ping: 171.74 ms)
0	11:24:42.156	'877844': login datacenter on Tri-Real through Real - Seoul (ping: 171.74 ms)
0	11:24:42.688	'877844': previous successful authorization performed from 103.233.11.57
0	11:25:04.111	'877844': auto connecting to a better access point Real - Hong Kong (ping is 6.45 ms)
0	11:25:04.767	'877844': login on Tri-Real through Real - Hong Kong (ping: 6.45 ms)
0	11:25:05.079	'877844': login datacenter on Tri-Real through Real - Hong Kong (ping: 6.45 ms)
0	11:25:05.408	'877844': previous successful authorization performed from 103.233.11.57
0	15:29:27.860	'877844': login on Tri-Real through Real - Hong Kong (ping: 6.45 ms)
0	15:29:28.125	'877844': login datacenter on Tri-Real through Real - Hong Kong (ping: 6.45 ms)
0	15:29:28.516	'877844': previous successful authorization performed from 103.233.11.57
0	15:29:51.111	'877844': ping to current access point Real - Hong Kong is 6.81 ms
0	15:32:35.025	'877844': login on Tri-Real through Real - Shanghai (ping: 101.76 ms)
0	15:32:37.166	'877844': login datacenter on Tri-Real through Real - Shanghai (ping: 101.76 ms)
0	15:32:37.759	'877844': previous successful authorization performed from 103.233.11.57
1	16:18:00.093	'877844': ping failed
0	16:18:01.202	'877844': login on Tri-Real through Real - Shanghai (ping: 101.76 ms)
0	16:18:02.593	'877844': login datacenter on Tri-Real through Real - Shanghai (ping: 101.76 ms)
0	16:18:03.156	'877844': previous successful authorization performed from 103.233.11.57
1	19:39:20.515	'877844': datacenter connecting failed [6]
0	19:40:03.486	'877844': login on Tri-Real through Real - Seoul (ping: 167.34 ms)
0	19:40:04.533	'877844': login datacenter on Tri-Real through Real - Seoul (ping: 167.34 ms)
0	19:40:05.064	'877844': previous successful authorization performed from 103.233.11.57
0	19:40:25.159	'877844': auto connecting to a better access point Real - Hong Kong (ping is 6.75 ms)
0	19:40:25.831	'877844': login on Tri-Real through Real - Hong Kong (ping: 6.75 ms)
0	19:40:26.143	'877844': login datacenter on Tri-Real through Real - Hong Kong (ping: 6.75 ms)
0	19:40:26.487	'877844': previous successful authorization performed from 103.233.11.57
0	21:43:54.467	'877844': login on Tri-Real through Real - Seoul (ping: 162.75 ms)
0	21:43:56.905	'877844': login datacenter on Tri-Real through Real - Seoul (ping: 162.75 ms)
0	21:43:57.702	'877844': previous successful authorization performed from 103.233.11.57
0	21:44:36.156	'877844': auto connecting to a better access point Real - Hong Kong (ping is 6.80 ms)
0	21:44:36.844	'877844': login on Tri-Real through Real - Hong Kong (ping: 6.80 ms)
0	21:44:37.266	'877844': login datacenter on Tri-Real through Real - Hong Kong (ping: 6.80 ms)
0	21:44:37.610	'877844': previous successful authorization performed from 103.233.11.57
0	23:47:44.042	'877844': login on Tri-Real through Real - Seoul (ping: 165.38 ms)
0	23:47:46.432	'877844': login datacenter on Tri-Real through Real - Seoul (ping: 165.38 ms)
0	23:47:47.339	'877844': previous successful authorization performed from 103.233.11.57
0	23:48:10.152	'877844': auto connecting to a better access point Real - Hong Kong (ping is 6.64 ms)
0	23:48:10.855	'877844': login on Tri-Real through Real - Hong Kong (ping: 6.64 ms)
0	23:48:39.810	'877844': login datacenter on Tri-Real through Real - Hong Kong (ping: 6.64 ms)
0	23:48:40.122	'877844': previous successful authorization performed from 103.233.11.57