1	00:32:02.295	'66036191': ping failed
1	00:32:02.311	'66036191': datacenter connecting failed [6]
0	00:32:02.889	'66036191': login on HeroCapitalPty-Server through DC#4 (ping: 91.19 ms)
0	00:32:03.607	'66036191': login datacenter on HeroCapitalPty-Server through DC#4 (ping: 91.19 ms)
0	00:32:03.873	'66036191': previous successful authorization performed from 152.32.252.153
0	00:32:04.420	'66036191': auto connecting to a better access point DC#2 (ping is 3.26 ms)
0	00:32:04.826	'66036191': login on HeroCapitalPty-Server through DC#2 (ping: 3.26 ms)
1	00:32:25.936	'66036191': datacenter connecting failed [6]
0	00:32:26.092	'66036191': previous successful authorization performed from 152.32.252.153
1	11:47:38.301	'66036191': connect failed [ûÓÐÁ¬½Ó]
0	11:48:19.488	'66036191': login on HeroCapitalPty-Server through DC#2 (ping: n/a)
0	11:48:21.019	'66036191': login datacenter on HeroCapitalPty-Server through DC#2 (ping: n/a)
0	11:48:21.144	'66036191': previous successful authorization performed from 152.32.252.153
0	11:48:21.910	'66036191': ping to current access point DC#2 is 3.63 ms
0	11:49:18.426	'66036191': login on HeroCapitalPty-Server through DC#4 (ping: 91.30 ms)
0	11:49:20.738	'66036191': login datacenter on HeroCapitalPty-Server through DC#4 (ping: 91.30 ms)
0	11:49:21.004	'66036191': previous successful authorization performed from 152.32.252.153
1	11:50:21.144	'66036191': ping failed
0	11:50:22.629	'66036191': login on HeroCapitalPty-Server through DC#2 (ping: 3.63 ms)
0	11:50:22.707	'66036191': login datacenter on HeroCapitalPty-Server through DC#2 (ping: 3.63 ms)
0	11:50:22.816	'66036191': previous successful authorization performed from 152.32.252.153