1	20:32:30.994	'66036191': datacenter connecting failed [6]
0	20:32:31.728	'66036191': login on HeroCapitalPty-Server through DC#3 (ping: 66.55 ms)
0	20:32:32.385	'66036191': login datacenter on HeroCapitalPty-Server through DC#3 (ping: 66.55 ms)
0	20:32:32.619	'66036191': previous successful authorization performed from 152.32.252.153
0	20:32:33.197	'66036191': auto connecting to a better access point DC#2 (ping is 4.45 ms)
0	20:32:33.510	'66036191': login on HeroCapitalPty-Server through DC#2 (ping: 4.45 ms)
0	20:32:33.807	'66036191': login datacenter on HeroCapitalPty-Server through DC#2 (ping: 4.45 ms)
0	20:32:34.885	'66036191': previous successful authorization performed from 152.32.252.153
0	20:36:55.900	'66036191': login on HeroCapitalPty-Server through DC#2 (ping: 4.45 ms)
0	20:36:56.010	'66036191': login datacenter on HeroCapitalPty-Server through DC#2 (ping: 4.45 ms)
0	20:36:56.182	'66036191': previous successful authorization performed from 152.32.252.153
1	20:41:56.557	'66036191': ping failed
0	20:41:56.807	'66036191': login on HeroCapitalPty-Server through DC#2 (ping: 4.45 ms)
0	20:41:56.900	'66036191': login datacenter on HeroCapitalPty-Server through DC#2 (ping: 4.45 ms)
0	20:41:57.025	'66036191': previous successful authorization performed from 152.32.252.153