1	03:00:53.376	'66036191': ping failed
1	03:00:53.376	'66036191': datacenter connecting failed [6]
0	03:00:53.860	'66036191': login on HeroCapitalPty-Server through DC#3 (ping: 69.05 ms)
0	03:00:55.501	'66036191': login datacenter on HeroCapitalPty-Server through DC#3 (ping: 69.05 ms)
0	03:00:55.719	'66036191': previous successful authorization performed from 152.32.252.153
0	03:00:56.266	'66036191': auto connecting to a better access point DC#2 (ping is 3.93 ms)
0	03:00:56.579	'66036191': login on HeroCapitalPty-Server through DC#2 (ping: 3.93 ms)
0	03:00:57.063	'66036191': login datacenter on HeroCapitalPty-Server through DC#2 (ping: 3.93 ms)
0	03:00:57.204	'66036191': previous successful authorization performed from 152.32.252.153
1	03:07:13.860	'66036191': ping failed
1	03:07:13.860	'66036191': datacenter connecting failed [6]
0	03:07:14.422	'66036191': login on HeroCapitalPty-Server through DC#3 (ping: 68.28 ms)
0	03:07:17.704	'66036191': login datacenter on HeroCapitalPty-Server through DC#3 (ping: 68.28 ms)
0	03:07:17.938	'66036191': previous successful authorization performed from 152.32.252.153
1	06:27:27.485	'66036191': connect failed [ûÓÐÁ¬½Ó]
0	06:27:32.797	'66036191': login on HeroCapitalPty-Server through DC#5 (ping: 90.62 ms)
0	06:27:34.282	'66036191': login datacenter on HeroCapitalPty-Server through DC#5 (ping: 90.62 ms)
0	06:27:34.579	'66036191': previous successful authorization performed from 152.32.252.153
0	06:27:34.969	'66036191': auto connecting to a better access point DC#2 (ping is 4.14 ms)
0	06:27:35.204	'66036191': login on HeroCapitalPty-Server through DC#2 (ping: 4.14 ms)
0	06:27:35.344	'66036191': login datacenter on HeroCapitalPty-Server through DC#2 (ping: 4.14 ms)
0	06:27:35.485	'66036191': previous successful authorization performed from 152.32.252.153