1	21:04:47.322	'66036191': ping failed
1	21:04:47.322	'66036191': datacenter connecting failed [6]
0	21:04:47.884	'66036191': login on HeroCapitalPty-Server through DC#4 (ping: 92.57 ms)
0	21:04:50.259	'66036191': login datacenter on HeroCapitalPty-Server through DC#4 (ping: 92.57 ms)
0	21:04:50.556	'66036191': previous successful authorization performed from 152.32.252.153
0	21:04:51.025	'66036191': auto connecting to a better access point DC#2 (ping is 4.57 ms)
0	21:04:51.369	'66036191': login on HeroCapitalPty-Server through DC#2 (ping: 4.57 ms)
0	21:04:51.494	'66036191': login datacenter on HeroCapitalPty-Server through DC#2 (ping: 4.57 ms)
0	21:04:51.650	'66036191': previous successful authorization performed from 152.32.252.153
1	21:05:31.525	'66036191': ping failed
1	21:05:31.525	'66036191': datacenter connecting failed [6]
0	21:05:32.119	'66036191': login on HeroCapitalPty-Server through DC#4 (ping: 111.86 ms)
0	21:05:32.759	'66036191': login datacenter on HeroCapitalPty-Server through DC#4 (ping: 111.86 ms)
0	21:05:33.040	'66036191': previous successful authorization performed from 152.32.252.153
1	23:24:06.811	'66036191': connect failed [ûÓÐÁ¬½Ó]
0	23:24:22.295	'66036191': login on HeroCapitalPty-Server through DC#2 (ping: n/a)
0	23:24:22.373	'66036191': login datacenter on HeroCapitalPty-Server through DC#2 (ping: n/a)
0	23:24:22.498	'66036191': previous successful authorization performed from 152.32.252.153
0	23:24:23.233	'66036191': ping to current access point DC#2 is 2.89 ms