1	02:44:09.315	'4202355': ping failed
1	02:44:09.487	'4202355': datacenter connecting failed [6]
0	02:44:10.205	'4202355': login on IMFCapital-Live through DC-10 (ping: 46.89 ms)
0	02:44:10.830	'4202355': login datacenter on IMFCapital-Live through DC-10 (ping: 46.89 ms)
0	02:44:11.065	'4202355': previous successful authorization performed from 152.32.252.153
0	02:44:25.534	'4202355': auto connecting to a better access point DC-2 (ping is 89.71 ms)
0	02:44:26.190	'4202355': login on IMFCapital-Live through DC-2 (ping: 89.71 ms)
0	02:44:27.080	'4202355': login datacenter on IMFCapital-Live through DC-2 (ping: 89.71 ms)
0	02:44:27.377	'4202355': previous successful authorization performed from 152.32.252.153
1	06:27:37.778	'4202355': ping failed
1	06:27:37.965	'4202355': datacenter connecting failed [6]
1	06:27:38.371	'4202355': connect failed [ûÓÐÁ¬½Ó]
0	06:27:43.996	'4202355': login on IMFCapital-Live through DC-7 (ping: 49.57 ms)
0	06:27:44.731	'4202355': login datacenter on IMFCapital-Live through DC-7 (ping: 49.57 ms)
0	06:27:44.996	'4202355': previous successful authorization performed from 152.32.252.153
0	06:27:58.746	'4202355': auto connecting to a better access point DC-1 (ping is 105.19 ms)
0	06:27:59.340	'4202355': login on IMFCapital-Live through DC-1 (ping: 105.19 ms)
0	06:29:05.840	'4202355': login on IMFCapital-Live through DC-7 (ping: 49.33 ms)
0	06:29:06.512	'4202355': login datacenter on IMFCapital-Live through DC-7 (ping: 49.33 ms)
0	06:29:06.746	'4202355': previous successful authorization performed from 152.32.252.153