1	13:55:43.962	'66036191': ping failed
1	13:55:43.962	'66036191': datacenter connecting failed [6]
0	13:55:44.525	'66036191': login on HeroCapitalPty-Server through DC#5 (ping: 214.99 ms)
0	13:55:45.166	'66036191': login datacenter on HeroCapitalPty-Server through DC#5 (ping: 214.99 ms)
0	13:55:45.462	'66036191': previous successful authorization performed from 152.32.252.153
0	13:55:45.947	'66036191': auto connecting to a better access point DC#2 (ping is 3.12 ms)
0	13:55:46.353	'66036191': login on HeroCapitalPty-Server through DC#2 (ping: 3.12 ms)
0	13:55:46.431	'66036191': login datacenter on HeroCapitalPty-Server through DC#2 (ping: 3.12 ms)
0	13:55:46.556	'66036191': previous successful authorization performed from 152.32.252.153
1	22:26:52.218	'66036191': ping failed
1	22:26:52.218	'66036191': datacenter connecting failed [6]
0	22:26:52.843	'66036191': login on HeroCapitalPty-Server through DC#3 (ping: 102.73 ms)
0	22:26:53.359	'66036191': login datacenter on HeroCapitalPty-Server through DC#3 (ping: 102.73 ms)
0	22:26:53.578	'66036191': previous successful authorization performed from 152.32.252.153
0	22:26:54.140	'66036191': auto connecting to a better access point DC#2 (ping is 2.47 ms)
0	22:26:54.546	'66036191': login on HeroCapitalPty-Server through DC#2 (ping: 2.47 ms)
0	22:26:55.140	'66036191': login datacenter on HeroCapitalPty-Server through DC#2 (ping: 2.47 ms)
0	22:26:55.296	'66036191': previous successful authorization performed from 152.32.252.153