1	04:27:19.391	'66036191': connect failed [ûÓÐÁ¬½Ó]
0	04:31:04.766	'66036191': login on HeroCapitalPty-Server through DC#2 (ping: n/a)
0	04:32:10.391	'66036191': login on HeroCapitalPty-Server through DC#3 (ping: n/a)
0	04:32:11.672	'66036191': login datacenter on HeroCapitalPty-Server through DC#3 (ping: n/a)
0	04:32:11.922	'66036191': previous successful authorization performed from 152.32.252.153
0	04:32:13.032	'66036191': auto connecting to a better access point DC#2 (ping is 3.95 ms)
0	04:32:13.266	'66036191': login on HeroCapitalPty-Server through DC#2 (ping: 3.95 ms)
0	04:32:16.829	'66036191': login datacenter on HeroCapitalPty-Server through DC#2 (ping: 3.95 ms)
0	04:32:16.969	'66036191': previous successful authorization performed from 152.32.252.153
1	22:49:39.204	'66036191': ping failed
1	22:49:39.204	'66036191': datacenter connecting failed [6]
0	22:49:41.969	'66036191': login on HeroCapitalPty-Server through DC#3 (ping: 71.62 ms)
0	22:49:43.844	'66036191': login datacenter on HeroCapitalPty-Server through DC#3 (ping: 71.62 ms)
0	22:49:44.079	'66036191': previous successful authorization performed from 152.32.252.153
0	22:49:44.876	'66036191': auto connecting to a better access point DC#2 (ping is 5.02 ms)
0	22:49:45.126	'66036191': login on HeroCapitalPty-Server through DC#2 (ping: 5.02 ms)
0	22:49:45.251	'66036191': login datacenter on HeroCapitalPty-Server through DC#2 (ping: 5.02 ms)
0	22:49:45.391	'66036191': previous successful authorization performed from 152.32.252.153
1	22:57:45.626	'66036191': ping failed
1	22:57:45.626	'66036191': datacenter connecting failed [6]
0	22:57:46.126	'66036191': login on HeroCapitalPty-Server through DC#3 (ping: 67.32 ms)
0	22:57:47.501	'66036191': login datacenter on HeroCapitalPty-Server through DC#3 (ping: 67.32 ms)
0	22:57:47.735	'66036191': previous successful authorization performed from 152.32.252.153