1	21:25:04.094	'66036191': ping failed
1	21:25:04.094	'66036191': datacenter connecting failed [6]
0	21:25:07.656	'66036191': login on HeroCapitalPty-Server through DC#3 (ping: 66.60 ms)
0	21:25:08.922	'66036191': login datacenter on HeroCapitalPty-Server through DC#3 (ping: 66.60 ms)
0	21:25:09.156	'66036191': previous successful authorization performed from 152.32.252.153
0	21:25:09.797	'66036191': auto connecting to a better access point DC#2 (ping is 4.03 ms)
0	21:25:10.125	'66036191': login on HeroCapitalPty-Server through DC#2 (ping: 4.03 ms)
0	21:25:10.219	'66036191': login datacenter on HeroCapitalPty-Server through DC#2 (ping: 4.03 ms)
0	21:25:10.344	'66036191': previous successful authorization performed from 152.32.252.153
1	21:34:30.656	'66036191': ping failed
1	21:34:30.656	'66036191': datacenter connecting failed [6]
0	21:34:31.125	'66036191': login on HeroCapitalPty-Server through DC#5 (ping: 103.47 ms)
0	21:34:43.281	'66036191': login datacenter on HeroCapitalPty-Server through DC#5 (ping: 103.47 ms)
0	21:34:43.625	'66036191': previous successful authorization performed from 152.32.252.153
1	21:37:10.391	'66036191': datacenter connecting failed [6]
0	21:37:10.766	'66036191': login on HeroCapitalPty-Server through DC#3 (ping: 169.80 ms)
0	21:37:11.437	'66036191': login datacenter on HeroCapitalPty-Server through DC#3 (ping: 169.80 ms)
0	21:37:11.703	'66036191': previous successful authorization performed from 152.32.252.153