1	10:49:41.521	'66036191': ping failed
1	10:49:41.537	'66036191': datacenter connecting failed [6]
0	10:49:41.928	'66036191': login on HeroCapitalPty-Server through DC#3 (ping: 74.61 ms)
0	10:49:50.209	'66036191': login datacenter on HeroCapitalPty-Server through DC#3 (ping: 74.61 ms)
0	10:49:53.428	'66036191': previous successful authorization performed from 152.32.252.153
0	10:49:59.678	'66036191': auto connecting to a better access point DC#2-1 (ping is 3.96 ms)
0	10:49:59.912	'66036191': login on HeroCapitalPty-Server through DC#2-1 (ping: 3.96 ms)
0	10:51:03.271	'66036191': login on HeroCapitalPty-Server through DC#2-1 (ping: 3.96 ms)
0	10:51:07.756	'66036191': login datacenter on HeroCapitalPty-Server through DC#2-1 (ping: 3.96 ms)
0	10:51:08.240	'66036191': previous successful authorization performed from 152.32.252.153
1	15:01:19.521	'66036191': ping failed
0	15:01:19.584	'66036191': login datacenter on HeroCapitalPty-Server
0	15:01:20.037	'66036191': login on HeroCapitalPty-Server through DC#2 (ping: 12.97 ms)
0	15:01:20.115	'66036191': login datacenter on HeroCapitalPty-Server through DC#2 (ping: 12.97 ms)
0	15:01:20.568	'66036191': previous successful authorization performed from 152.32.252.153
0	15:01:21.834	'66036191': ping to current access point DC#2 is 6.34 ms