1	09:30:55.246	'66036191': connect failed [ûÓÐÁ¬½Ó]
0	09:34:43.543	'66036191': login on HeroCapitalPty-Server through DC#5 (ping: n/a)
0	09:35:48.043	'66036191': login on HeroCapitalPty-Server through DC#5 (ping: n/a)
0	09:36:52.981	'66036191': login on HeroCapitalPty-Server through DC#5 (ping: n/a)
0	09:36:53.777	'66036191': login datacenter on HeroCapitalPty-Server through DC#5 (ping: n/a)
0	09:36:54.106	'66036191': previous successful authorization performed from 152.32.252.153
0	09:36:57.606	'66036191': auto connecting to a better access point DC#2 (ping is 13.85 ms)
0	09:36:58.012	'66036191': login on HeroCapitalPty-Server through DC#2 (ping: 13.85 ms)
0	09:36:58.121	'66036191': login datacenter on HeroCapitalPty-Server through DC#2 (ping: 13.85 ms)
0	09:36:58.293	'66036191': previous successful authorization performed from 152.32.252.153
1	10:42:21.282	'66036191': ping failed
1	10:42:21.298	'66036191': datacenter connecting failed [6]
0	10:42:21.845	'66036191': login on HeroCapitalPty-Server through DC#3 (ping: 71.00 ms)
0	10:42:25.392	'66036191': login datacenter on HeroCapitalPty-Server through DC#3 (ping: 71.00 ms)
0	10:42:25.923	'66036191': previous successful authorization performed from 152.32.252.153
0	10:42:34.845	'66036191': ping to current access point DC#3 is 71.11 ms
0	12:50:11.921	'66036191': login on HeroCapitalPty-Server through DC#3 (ping: 71.11 ms)
0	12:50:14.046	'66036191': login datacenter on HeroCapitalPty-Server through DC#3 (ping: 71.11 ms)
0	12:50:14.296	'66036191': previous successful authorization performed from 152.32.252.153
0	12:50:28.874	'66036191': auto connecting to a better access point DC#2 (ping is 3.40 ms)
0	12:50:29.202	'66036191': login on HeroCapitalPty-Server through DC#2 (ping: 3.40 ms)
0	12:50:29.296	'66036191': login datacenter on HeroCapitalPty-Server through DC#2 (ping: 3.40 ms)
0	12:50:29.421	'66036191': previous successful authorization performed from 152.32.252.153