1	14:03:18.834	'66036191': ping failed
1	14:03:18.912	'66036191': ping failed
1	14:03:18.912	'66036191': datacenter connecting failed [6]
0	14:03:21.209	'66036191': login on HeroCapitalPty-Server through DC#3 (ping: 75.00 ms)
0	14:03:21.762	'66036191': login datacenter on HeroCapitalPty-Server through DC#3 (ping: 75.00 ms)
0	14:03:22.367	'66036191': previous successful authorization performed from 152.32.252.153
0	14:03:22.727	'66036191': auto connecting to a better access point DC#2 (ping is 2.52 ms)
0	14:03:22.977	'66036191': login on HeroCapitalPty-Server through DC#2 (ping: 2.52 ms)
0	14:03:23.070	'66036191': login datacenter on HeroCapitalPty-Server through DC#2 (ping: 2.52 ms)
0	14:03:23.539	'66036191': previous successful authorization performed from 152.32.252.153
1	16:01:48.280	'66036191': ping failed
1	16:01:48.296	'66036191': datacenter connecting failed [6]
0	16:01:49.827	'66036191': login on HeroCapitalPty-Server through DC#2-1 (ping: 2.72 ms)
0	16:01:50.187	'66036191': login datacenter on HeroCapitalPty-Server through DC#2-1 (ping: 2.72 ms)
0	16:01:50.702	'66036191': previous successful authorization performed from 152.32.252.153
0	16:01:51.468	'66036191': auto connecting to a better access point DC#2 (ping is 2.36 ms)
0	16:01:51.905	'66036191': login on HeroCapitalPty-Server through DC#2 (ping: 2.36 ms)
0	16:01:52.124	'66036191': login datacenter on HeroCapitalPty-Server through DC#2 (ping: 2.36 ms)
0	16:01:52.609	'66036191': previous successful authorization performed from 152.32.252.153
0	16:43:17.056	'66036191': login on HeroCapitalPty-Server through DC#2-1 (ping: 3.73 ms)
0	16:43:17.415	'66036191': login datacenter on HeroCapitalPty-Server through DC#2-1 (ping: 3.73 ms)
0	16:43:17.931	'66036191': previous successful authorization performed from 152.32.252.153