1	21:39:40.419	'66036191': ping failed
1	21:39:40.419	'66036191': datacenter connecting failed [6]
0	21:39:50.669	'66036191': login on HeroCapitalPty-Server through DC#3 (ping: 116.76 ms)
0	21:39:51.434	'66036191': login datacenter on HeroCapitalPty-Server through DC#3 (ping: 116.76 ms)
0	21:39:51.747	'66036191': previous successful authorization performed from 152.32.252.153
0	21:39:58.465	'66036191': auto connecting to a better access point DC#2 (ping is 3.91 ms)
0	21:39:58.747	'66036191': login on HeroCapitalPty-Server through DC#2 (ping: 3.91 ms)
0	21:39:58.825	'66036191': login datacenter on HeroCapitalPty-Server through DC#2 (ping: 3.91 ms)
0	21:39:58.981	'66036191': previous successful authorization performed from 152.32.252.153
1	21:45:59.100	'66036191': ping failed
1	21:45:59.100	'66036191': datacenter connecting failed [6]
0	21:46:20.585	'66036191': login on HeroCapitalPty-Server through DC#3 (ping: 108.08 ms)
0	21:46:21.569	'66036191': login datacenter on HeroCapitalPty-Server through DC#3 (ping: 108.08 ms)
0	21:46:21.850	'66036191': previous successful authorization performed from 152.32.252.153
1	23:30:27.551	'66036191': connect failed [ûÓÐÁ¬½Ó]
0	23:30:53.895	'66036191': login on HeroCapitalPty-Server through DC#2 (ping: n/a)
0	23:30:53.989	'66036191': login datacenter on HeroCapitalPty-Server through DC#2 (ping: n/a)
0	23:30:54.176	'66036191': previous successful authorization performed from 152.32.252.153
0	23:30:54.379	'66036191': ping to current access point DC#2 is 2.01 ms