1	20:30:26.771	'66036191': ping failed
0	20:30:26.786	'66036191': login datacenter on HeroCapitalPty-Server
0	20:30:27.318	'66036191': login on HeroCapitalPty-Server through DC#3 (ping: 83.60 ms)
0	20:30:27.833	'66036191': login datacenter on HeroCapitalPty-Server through DC#3 (ping: 83.60 ms)
0	20:30:28.083	'66036191': previous successful authorization performed from 152.32.252.153
0	20:30:29.005	'66036191': auto connecting to a better access point DC#2 (ping is 3.11 ms)
0	20:30:29.349	'66036191': login on HeroCapitalPty-Server through DC#2 (ping: 3.11 ms)
0	20:30:58.708	'66036191': login datacenter on HeroCapitalPty-Server through DC#2 (ping: 3.11 ms)
0	20:30:59.146	'66036191': previous successful authorization performed from 152.32.252.153
1	20:32:28.005	'66036191': ping failed
0	20:32:28.005	'66036191': login datacenter on HeroCapitalPty-Server
0	20:32:30.599	'66036191': login on HeroCapitalPty-Server through DC#3 (ping: 86.51 ms)
0	20:32:35.708	'66036191': login datacenter on HeroCapitalPty-Server through DC#3 (ping: 86.51 ms)
0	20:32:35.974	'66036191': previous successful authorization performed from 152.32.252.153
1	20:38:11.833	'66036191': datacenter connecting failed [6]
0	20:38:12.333	'66036191': login on HeroCapitalPty-Server through DC#3 (ping: 86.51 ms)
0	20:38:12.880	'66036191': login datacenter on HeroCapitalPty-Server through DC#3 (ping: 86.51 ms)
0	20:38:13.114	'66036191': previous successful authorization performed from 152.32.252.153
1	20:41:06.005	'66036191': datacenter connecting failed [6]
0	20:41:06.427	'66036191': login on HeroCapitalPty-Server through DC#3 (ping: 86.51 ms)
0	20:41:07.380	'66036191': login datacenter on HeroCapitalPty-Server through DC#3 (ping: 86.51 ms)
0	20:41:07.614	'66036191': previous successful authorization performed from 152.32.252.153