1	18:08:24.377	'66036191': ping failed
0	18:08:24.627	'66036191': login on HeroCapitalPty-Server through DC#2 (ping: 55.40 ms)
0	18:08:58.267	'66036191': login datacenter on HeroCapitalPty-Server through DC#2 (ping: 55.40 ms)
0	18:08:59.220	'66036191': auto connecting to a better access point DC#2-1 (ping is 3.53 ms)
0	18:09:03.970	'66036191': login on HeroCapitalPty-Server through DC#2-1 (ping: 3.53 ms)
0	18:09:04.142	'66036191': login datacenter on HeroCapitalPty-Server through DC#2-1 (ping: 3.53 ms)
0	18:09:04.658	'66036191': previous successful authorization performed from 152.32.252.153
1	20:30:30.771	'66036191': ping failed
1	20:30:30.771	'66036191': datacenter connecting failed [6]
0	20:30:30.974	'66036191': login on HeroCapitalPty-Server through DC#2 (ping: 4.82 ms)
0	20:30:31.755	'66036191': login datacenter on HeroCapitalPty-Server through DC#2 (ping: 4.82 ms)
0	20:30:32.380	'66036191': previous successful authorization performed from 152.32.252.153
0	20:30:50.537	'66036191': auto connecting to a better access point DC#2-1 (ping is 9.28 ms)
0	20:30:50.709	'66036191': login on HeroCapitalPty-Server through DC#2-1 (ping: 9.28 ms)
0	20:30:54.271	'66036191': login datacenter on HeroCapitalPty-Server through DC#2-1 (ping: 9.28 ms)
0	20:30:55.271	'66036191': previous successful authorization performed from 152.32.252.153
1	20:31:54.334	'66036191': ping failed
0	20:31:54.818	'66036191': login on HeroCapitalPty-Server through DC#2 (ping: 56.71 ms)
0	20:31:59.240	'66036191': login datacenter on HeroCapitalPty-Server through DC#2 (ping: 56.71 ms)
0	20:31:59.677	'66036191': previous successful authorization performed from 152.32.252.153