1	18:17:32.597	'66036191': ping failed
1	18:17:32.613	'66036191': datacenter connecting failed [6]
0	18:17:33.644	'66036191': login on HeroCapitalPty-Server through DC#5 (ping: 89.10 ms)
0	18:18:34.675	'66036191': login datacenter on HeroCapitalPty-Server
0	18:18:35.081	'66036191': auto connecting to a better access point DC#2 (ping is 4.18 ms)
0	18:18:40.253	'66036191': login on HeroCapitalPty-Server through DC#2 (ping: 4.18 ms)
0	18:18:40.347	'66036191': login datacenter on HeroCapitalPty-Server through DC#2 (ping: 4.18 ms)
0	18:18:40.472	'66036191': previous successful authorization performed from 152.32.252.153
1	22:33:32.341	'66036191': ping failed
1	22:33:32.341	'66036191': datacenter connecting failed [6]
0	22:33:32.888	'66036191': login on HeroCapitalPty-Server through DC#3 (ping: 67.97 ms)
0	22:33:34.201	'66036191': login datacenter on HeroCapitalPty-Server through DC#3 (ping: 67.97 ms)
0	22:33:34.435	'66036191': previous successful authorization performed from 152.32.252.153
0	22:33:35.888	'66036191': auto connecting to a better access point DC#2 (ping is 4.81 ms)
0	22:33:36.232	'66036191': login on HeroCapitalPty-Server through DC#2 (ping: 4.81 ms)
0	22:33:36.622	'66036191': login datacenter on HeroCapitalPty-Server through DC#2 (ping: 4.81 ms)
0	22:33:36.747	'66036191': previous successful authorization performed from 152.32.252.153