1	16:51:23.664	'66036191': datacenter connecting failed [6]
0	16:51:24.133	'66036191': login on HeroCapitalPty-Server through DC#4 (ping: 90.28 ms)
0	16:51:29.570	'66036191': login datacenter on HeroCapitalPty-Server through DC#4 (ping: 90.28 ms)
0	16:51:29.836	'66036191': previous successful authorization performed from 152.32.252.153
0	16:51:30.789	'66036191': auto connecting to a better access point DC#2 (ping is 43.42 ms)
0	16:51:31.117	'66036191': login on HeroCapitalPty-Server through DC#2 (ping: 43.42 ms)
0	16:51:33.226	'66036191': login datacenter on HeroCapitalPty-Server through DC#2 (ping: 43.42 ms)
0	16:51:33.414	'66036191': previous successful authorization performed from 152.32.252.153
1	16:52:33.305	'66036191': ping failed
1	16:52:33.305	'66036191': datacenter connecting failed [6]
0	16:52:33.820	'66036191': login on HeroCapitalPty-Server through DC#4 (ping: 89.17 ms)
1	16:53:39.258	'66036191': connect failed [ûÓÐÁ¬½Ó]
0	16:53:49.742	'66036191': login on HeroCapitalPty-Server through DC#2 (ping: n/a)
0	16:53:50.242	'66036191': login datacenter on HeroCapitalPty-Server through DC#2 (ping: n/a)
0	16:53:50.492	'66036191': previous successful authorization performed from 152.32.252.153
0	16:53:54.289	'66036191': ping to current access point DC#2 is 38.57 ms
1	16:54:10.586	'66036191': ping failed
0	16:54:10.945	'66036191': login on HeroCapitalPty-Server through DC#2 (ping: 38.57 ms)
0	16:54:11.336	'66036191': login datacenter on HeroCapitalPty-Server through DC#2 (ping: 38.57 ms)
0	16:54:11.633	'66036191': previous successful authorization performed from 152.32.252.153