1	13:13:01.252	'66036191': ping failed
0	13:13:04.049	'66036191': login on HeroCapitalPty-Server through DC#3 (ping: 68.68 ms)
0	13:13:10.018	'66036191': login datacenter on HeroCapitalPty-Server through DC#3 (ping: 68.68 ms)
0	13:13:10.252	'66036191': previous successful authorization performed from 152.32.252.153
0	13:13:13.486	'66036191': ping to current access point DC#3 is 70.09 ms
1	13:13:36.221	'66036191': connect failed [ûÓÐÁ¬½Ó]
0	13:17:30.892	'66036191': login on HeroCapitalPty-Server through DC#2 (ping: n/a)
0	13:18:37.126	'66036191': login on HeroCapitalPty-Server through DC#3 (ping: n/a)
0	13:18:47.610	'66036191': login datacenter on HeroCapitalPty-Server through DC#3 (ping: n/a)
0	13:18:48.142	'66036191': previous successful authorization performed from 152.32.252.153
0	13:19:13.845	'66036191': ping to current access point DC#3 is 70.90 ms
1	19:16:25.262	'66036191': ping failed
1	19:16:25.262	'66036191': datacenter connecting failed [6]
0	19:16:25.684	'66036191': login on HeroCapitalPty-Server through DC#2 (ping: 6.45 ms)
0	19:16:25.793	'66036191': login datacenter on HeroCapitalPty-Server through DC#2 (ping: 6.45 ms)
0	19:16:25.918	'66036191': previous successful authorization performed from 152.32.252.153
0	19:16:35.259	'66036191': ping to current access point DC#2 is 5.02 ms
0	23:22:05.517	'66036191': login on HeroCapitalPty-Server through DC#2 (ping: 5.02 ms)
0	23:22:05.611	'66036191': login datacenter on HeroCapitalPty-Server through DC#2 (ping: 5.02 ms)
0	23:22:05.799	'66036191': previous successful authorization performed from 152.32.252.153
0	23:22:06.799	'66036191': ping to current access point DC#2 is 4.35 ms