1	05:34:08.426	'66036191': connect failed [ûÓÐÁ¬½Ó]
0	05:37:43.222	'66036191': login on HeroCapitalPty-Server through DC#3 (ping: n/a)
0	05:37:57.597	'66036191': login datacenter on HeroCapitalPty-Server through DC#3 (ping: n/a)
0	05:37:57.847	'66036191': previous successful authorization performed from 152.32.252.153
0	05:37:58.301	'66036191': auto connecting to a better access point DC#2 (ping is 2.72 ms)
0	05:37:58.676	'66036191': login on HeroCapitalPty-Server through DC#2 (ping: 2.72 ms)
0	05:38:13.222	'66036191': login datacenter on HeroCapitalPty-Server through DC#2 (ping: 2.72 ms)
0	05:38:13.347	'66036191': previous successful authorization performed from 152.32.252.153
0	15:58:14.431	'66036191': login on HeroCapitalPty-Server through DC#2 (ping: 2.72 ms)
0	15:58:14.556	'66036191': login datacenter on HeroCapitalPty-Server through DC#2 (ping: 2.72 ms)
0	15:58:14.681	'66036191': previous successful authorization performed from 152.32.252.153
0	15:58:15.322	'66036191': ping to current access point DC#2 is 2.85 ms
1	16:00:34.665	'66036191': ping failed
1	16:00:34.665	'66036191': datacenter connecting failed [6]
0	16:00:35.509	'66036191': login on HeroCapitalPty-Server through DC#5 (ping: 82.98 ms)
0	16:00:54.478	'66036191': login datacenter on HeroCapitalPty-Server through DC#5 (ping: 82.98 ms)
0	16:00:54.759	'66036191': previous successful authorization performed from 152.32.252.153
1	16:02:14.587	'66036191': ping failed
1	16:02:14.603	'66036191': datacenter connecting failed [6]
0	16:02:15.181	'66036191': login on HeroCapitalPty-Server through DC#3 (ping: 66.91 ms)
0	16:02:15.712	'66036191': login datacenter on HeroCapitalPty-Server through DC#3 (ping: 66.91 ms)
0	16:02:15.931	'66036191': previous successful authorization performed from 152.32.252.153