1	15:26:34.357	'66036191': ping failed
1	15:26:34.560	'66036191': ping failed
1	15:26:34.560	'66036191': datacenter connecting failed [6]
0	15:26:35.716	'66036191': login on HeroCapitalPty-Server through DC#2-1 (ping: 3.27 ms)
0	15:26:36.060	'66036191': login datacenter on HeroCapitalPty-Server through DC#2-1 (ping: 3.27 ms)
0	15:26:36.529	'66036191': previous successful authorization performed from 152.32.252.153
0	15:26:37.810	'66036191': ping to current access point DC#2-1 is 2.14 ms
1	17:01:07.449	'66036191': ping failed
1	17:01:07.495	'66036191': ping failed
1	17:01:07.495	'66036191': datacenter connecting failed [6]
0	17:01:31.527	'66036191': login on HeroCapitalPty-Server through DC#2 (ping: 4.15 ms)
0	17:02:37.532	'66036191': login on HeroCapitalPty-Server through DC#3 (ping: 66.89 ms)
0	17:02:38.048	'66036191': login datacenter on HeroCapitalPty-Server through DC#3 (ping: 66.89 ms)
0	17:02:38.626	'66036191': previous successful authorization performed from 152.32.252.153
0	17:02:38.829	'66036191': auto connecting to a better access point DC#2 (ping is 2.46 ms)
0	17:02:39.126	'66036191': login on HeroCapitalPty-Server through DC#2 (ping: 2.46 ms)
0	17:02:39.236	'66036191': login datacenter on HeroCapitalPty-Server through DC#2 (ping: 2.46 ms)
0	17:02:39.720	'66036191': previous successful authorization performed from 152.32.252.153
1	21:32:35.565	'66036191': ping failed
1	21:32:35.752	'66036191': ping failed
1	21:32:35.752	'66036191': datacenter connecting failed [6]
0	21:32:38.018	'66036191': login on HeroCapitalPty-Server through DC#2-1 (ping: 2.58 ms)
0	21:32:38.330	'66036191': login datacenter on HeroCapitalPty-Server through DC#2-1 (ping: 2.58 ms)
0	21:32:39.143	'66036191': previous successful authorization performed from 152.32.252.153
0	21:32:39.518	'66036191': auto connecting to a better access point DC#2 (ping is 2.88 ms)
0	21:32:39.799	'66036191': login on HeroCapitalPty-Server through DC#2 (ping: 2.88 ms)
0	21:32:39.924	'66036191': login datacenter on HeroCapitalPty-Server through DC#2 (ping: 2.88 ms)
0	21:32:40.377	'66036191': previous successful authorization performed from 152.32.252.153
0	21:34:14.375	'66036191': login datacenter on HeroCapitalPty-Server
1	21:34:14.485	'66036191': ping failed
0	21:34:14.860	'66036191': login on HeroCapitalPty-Server through DC#2-1 (ping: 3.33 ms)
0	21:34:15.360	'66036191': login datacenter on HeroCapitalPty-Server through DC#2-1 (ping: 3.33 ms)
0	21:34:15.969	'66036191': previous successful authorization performed from 152.32.252.153
1	21:39:30.656	'66036191': datacenter connecting failed [6]
0	21:39:31.328	'66036191': login on HeroCapitalPty-Server through DC#3 (ping: 68.78 ms)
0	21:39:36.563	'66036191': login datacenter on HeroCapitalPty-Server through DC#3 (ping: 68.78 ms)
0	21:39:37.422	'66036191': previous successful authorization performed from 152.32.252.153
1	21:44:29.735	'66036191': datacenter connecting failed [6]
0	21:44:30.297	'66036191': login on HeroCapitalPty-Server through DC#5 (ping: 78.91 ms)
0	21:44:31.797	'66036191': login datacenter on HeroCapitalPty-Server through DC#5 (ping: 78.91 ms)
0	21:44:32.391	'66036191': previous successful authorization performed from 152.32.252.153
1	21:51:44.891	'66036191': datacenter connecting failed [6]
1	21:51:45.000	'66036191': connect failed [ûÓÐÁ¬½Ó]
0	21:53:15.844	'66036191': login on HeroCapitalPty-Server through DC#2 (ping: n/a)
0	21:53:15.985	'66036191': login datacenter on HeroCapitalPty-Server through DC#2 (ping: n/a)
0	21:53:16.438	'66036191': previous successful authorization performed from 152.32.252.153
0	21:53:17.125	'66036191': ping to current access point DC#2 is 2.39 ms