1	01:11:28.909	'880003669': ping failed
1	01:11:28.924	'880003669': datacenter connecting failed [6]
0	01:11:29.737	'880003669': login on EmperorFinancial-Live through DC2 (ping: 52.15 ms)
0	01:11:30.362	'880003669': login datacenter on EmperorFinancial-Live through DC2 (ping: 52.15 ms)
0	01:11:30.815	'880003669': previous successful authorization performed from 103.233.11.58
0	01:12:08.770	'880003669': auto connecting to a better access point DC1 (ping is 51.45 ms)
0	01:12:09.567	'880003669': login on EmperorFinancial-Live through DC1 (ping: 51.45 ms)
0	01:12:13.567	'880003669': login datacenter on EmperorFinancial-Live through DC1 (ping: 51.45 ms)
0	01:12:14.864	'880003669': previous successful authorization performed from 103.233.11.58
1	03:31:43.072	'880003669': datacenter connecting failed [6]
0	03:31:43.947	'880003669': login on EmperorFinancial-Live through Data Center 4 (ping: 53.00 ms)
0	03:31:44.510	'880003669': login datacenter on EmperorFinancial-Live through Data Center 4 (ping: 53.00 ms)
0	03:31:44.963	'880003669': previous successful authorization performed from 103.233.11.58
0	03:32:20.621	'880003669': auto connecting to a better access point DC2 (ping is 51.83 ms)
0	03:32:21.371	'880003669': login on EmperorFinancial-Live through DC2 (ping: 51.83 ms)
0	03:32:21.730	'880003669': login datacenter on EmperorFinancial-Live through DC2 (ping: 51.83 ms)
0	03:32:22.137	'880003669': previous successful authorization performed from 103.233.11.58
1	03:32:38.825	MQL5.community: authorization failed
0	05:34:40.749	'880003669': login on EmperorFinancial-Live through DC2 (ping: 51.83 ms)
0	05:34:41.374	'880003669': login datacenter on EmperorFinancial-Live through DC2 (ping: 51.83 ms)
0	05:34:41.780	'880003669': previous successful authorization performed from 103.233.11.58
0	05:35:17.626	'880003669': auto connecting to a better access point DC1 (ping is 52.34 ms)
0	05:35:18.360	'880003669': login on EmperorFinancial-Live through DC1 (ping: 52.34 ms)
0	05:35:29.376	'880003669': login datacenter on EmperorFinancial-Live through DC1 (ping: 52.34 ms)
0	05:35:29.751	'880003669': previous successful authorization performed from 103.233.11.58
1	05:46:50.502	'880003669': ping failed
0	05:46:51.252	'880003669': login on EmperorFinancial-Live through DC1 (ping: 52.34 ms)
0	05:46:51.815	'880003669': login datacenter on EmperorFinancial-Live through DC1 (ping: 52.34 ms)
0	05:46:52.221	'880003669': previous successful authorization performed from 103.233.11.58
1	06:06:12.729	'880003669': ping failed
1	06:06:12.745	'880003669': datacenter connecting failed [6]
0	06:06:13.573	'880003669': login on EmperorFinancial-Live through Data Center 4 (ping: 53.14 ms)
0	06:06:14.198	'880003669': login datacenter on EmperorFinancial-Live through Data Center 4 (ping: 53.14 ms)
0	06:06:14.557	'880003669': previous successful authorization performed from 103.233.11.58
1	08:22:24.428	'880003669': datacenter connecting failed [6]
0	08:22:28.272	'880003669': login on EmperorFinancial-Live through DC2 (ping: 53.32 ms)
0	08:22:28.881	'880003669': login datacenter on EmperorFinancial-Live through DC2 (ping: 53.32 ms)
0	08:22:29.319	'880003669': previous successful authorization performed from 103.233.11.58
0	08:23:04.008	'880003669': ping to current access point DC2 is 51.90 ms
1	09:08:13.183	'880003669': ping failed
1	09:08:13.199	'880003669': datacenter connecting failed [6]
0	09:08:14.058	'880003669': login on EmperorFinancial-Live through DC1 (ping: 52.44 ms)
0	09:08:14.683	'880003669': login datacenter on EmperorFinancial-Live through DC1 (ping: 52.44 ms)
0	09:08:15.136	'880003669': previous successful authorization performed from 103.233.11.58
1	09:54:21.111	'880003669': datacenter connecting failed [2]
0	09:54:21.939	'880003669': login on EmperorFinancial-Live through Data Center 4 (ping: 53.34 ms)
0	09:54:22.548	'880003669': login datacenter on EmperorFinancial-Live through Data Center 4 (ping: 53.34 ms)
0	09:54:22.939	'880003669': previous successful authorization performed from 103.233.11.58
0	09:54:58.128	'880003669': auto connecting to a better access point DC1 (ping is 51.72 ms)
0	09:54:58.862	'880003669': login on EmperorFinancial-Live through DC1 (ping: 51.72 ms)
0	09:54:59.456	'880003669': login datacenter on EmperorFinancial-Live through DC1 (ping: 51.72 ms)
0	09:54:59.909	'880003669': previous successful authorization performed from 103.233.11.58
1	09:58:46.154	'880003669': datacenter connecting failed [6]
0	09:58:55.967	'880003669': login on EmperorFinancial-Live through DC2 (ping: 52.20 ms)
0	09:58:56.624	'880003669': login datacenter on EmperorFinancial-Live through DC2 (ping: 52.20 ms)
0	09:58:57.311	'880003669': previous successful authorization performed from 103.233.11.58
1	10:12:57.288	'880003669': ping failed
1	10:12:57.304	'880003669': datacenter connecting failed [6]
0	10:12:58.210	'880003669': login on EmperorFinancial-Live through Data Center 4 (ping: 53.85 ms)
0	10:13:01.023	'880003669': login datacenter on EmperorFinancial-Live through Data Center 4 (ping: 53.85 ms)
0	10:13:01.445	'880003669': previous successful authorization performed from 103.233.11.58
1	10:31:08.965	'880003669': datacenter connecting failed [6]
0	10:31:09.824	'880003669': login on EmperorFinancial-Live through Data Center 2 (ping: 68.71 ms)
0	10:31:10.762	'880003669': login datacenter on EmperorFinancial-Live through Data Center 2 (ping: 68.71 ms)
0	10:31:11.184	'880003669': previous successful authorization performed from 103.233.11.58
0	13:26:00.430	'880003669': login on EmperorFinancial-Live through Data Center 2 (ping: 68.71 ms)
0	13:26:01.633	'880003669': login datacenter on EmperorFinancial-Live through Data Center 2 (ping: 68.71 ms)
0	13:26:02.039	'880003669': previous successful authorization performed from 103.233.11.58
0	13:26:39.494	'880003669': auto connecting to a better access point DC1 (ping is 51.46 ms)
0	13:26:40.619	'880003669': login on EmperorFinancial-Live through DC1 (ping: 51.46 ms)
0	13:26:44.307	'880003669': login datacenter on EmperorFinancial-Live through DC1 (ping: 51.46 ms)
0	13:26:44.729	'880003669': previous successful authorization performed from 103.233.11.58
1	18:37:53.908	'880003669': ping failed
1	18:37:53.924	'880003669': datacenter connecting failed [6]
0	18:37:54.799	'880003669': login on EmperorFinancial-Live through Data Center 4 (ping: 55.10 ms)
0	18:37:55.408	'880003669': login datacenter on EmperorFinancial-Live through Data Center 4 (ping: 55.10 ms)
0	18:37:55.861	'880003669': previous successful authorization performed from 103.233.11.58
0	18:38:31.254	'880003669': auto connecting to a better access point DC1 (ping is 52.37 ms)
0	18:38:32.050	'880003669': login on EmperorFinancial-Live through DC1 (ping: 52.37 ms)
0	18:38:32.629	'880003669': login datacenter on EmperorFinancial-Live through DC1 (ping: 52.37 ms)
0	18:38:33.019	'880003669': previous successful authorization performed from 103.233.11.58
1	19:54:16.859	'880003669': ping failed
0	19:54:17.718	'880003669': login on EmperorFinancial-Live through DC1 (ping: 52.37 ms)
0	19:54:18.281	'880003669': login datacenter on EmperorFinancial-Live through DC1 (ping: 52.37 ms)
0	19:54:18.687	'880003669': previous successful authorization performed from 103.233.11.58
0	19:54:54.017	'880003669': ping to current access point DC1 is 53.63 ms