1	20:00:27.405	'66036191': ping failed
0	20:00:27.405	'66036191': login datacenter on HeroCapitalPty-Server
0	20:00:27.936	'66036191': login on HeroCapitalPty-Server through DC#3 (ping: 62.40 ms)
0	20:00:31.608	'66036191': login datacenter on HeroCapitalPty-Server through DC#3 (ping: 62.40 ms)
0	20:00:31.858	'66036191': previous successful authorization performed from 152.32.252.153
0	20:00:50.905	'66036191': auto connecting to a better access point DC#2 (ping is 3.37 ms)
0	20:00:51.264	'66036191': login on HeroCapitalPty-Server through DC#2 (ping: 3.37 ms)
0	20:00:51.655	'66036191': login datacenter on HeroCapitalPty-Server through DC#2 (ping: 3.37 ms)
0	20:00:51.780	'66036191': previous successful authorization performed from 152.32.252.153
1	22:33:05.220	'66036191': ping failed
0	22:33:05.220	'66036191': login datacenter on HeroCapitalPty-Server
0	22:33:05.751	'66036191': login on HeroCapitalPty-Server through DC#3 (ping: 76.21 ms)
0	22:33:06.236	'66036191': login datacenter on HeroCapitalPty-Server through DC#3 (ping: 76.21 ms)
0	22:33:06.455	'66036191': previous successful authorization performed from 152.32.252.153
0	22:33:07.923	'66036191': auto connecting to a better access point DC#2 (ping is 5.73 ms)
0	22:33:08.517	'66036191': login on HeroCapitalPty-Server through DC#2 (ping: 5.73 ms)
0	22:33:09.376	'66036191': login datacenter on HeroCapitalPty-Server through DC#2 (ping: 5.73 ms)
0	22:33:09.767	'66036191': previous successful authorization performed from 152.32.252.153
1	23:00:21.054	'66036191': ping failed
1	23:00:21.054	'66036191': datacenter connecting failed [6]
0	23:00:21.523	'66036191': login on HeroCapitalPty-Server through DC#3 (ping: 62.69 ms)
0	23:00:24.617	'66036191': login datacenter on HeroCapitalPty-Server through DC#3 (ping: 62.69 ms)
0	23:00:24.835	'66036191': previous successful authorization performed from 152.32.252.153