1	20:31:12.052	'66036191': ping failed
1	20:31:12.052	'66036191': datacenter connecting failed [6]
0	20:31:12.442	'66036191': login on HeroCapitalPty-Server through DC#5 (ping: 100.18 ms)
0	20:31:14.114	'66036191': login datacenter on HeroCapitalPty-Server through DC#5 (ping: 100.18 ms)
0	20:31:15.645	'66036191': previous successful authorization performed from 152.32.252.153
0	20:31:16.270	'66036191': auto connecting to a better access point DC#2-1 (ping is 12.08 ms)
0	20:31:16.427	'66036191': login on HeroCapitalPty-Server through DC#2-1 (ping: 12.08 ms)
0	20:31:17.442	'66036191': login datacenter on HeroCapitalPty-Server through DC#2-1 (ping: 12.08 ms)
0	20:31:17.911	'66036191': previous successful authorization performed from 152.32.252.153
1	20:32:48.599	'66036191': ping failed
1	20:32:48.614	'66036191': datacenter connecting failed [6]
0	20:32:49.020	'66036191': login on HeroCapitalPty-Server through DC#3 (ping: 77.06 ms)
0	20:32:49.708	'66036191': login datacenter on HeroCapitalPty-Server through DC#3 (ping: 77.06 ms)
0	20:32:50.317	'66036191': previous successful authorization performed from 152.32.252.153
1	20:54:54.324	'66036191': ping failed
1	20:54:54.355	'66036191': datacenter connecting failed [6]
0	20:54:58.637	'66036191': login on HeroCapitalPty-Server through DC#5 (ping: 85.68 ms)
0	20:54:59.637	'66036191': login datacenter on HeroCapitalPty-Server through DC#5 (ping: 85.68 ms)
0	20:55:00.527	'66036191': previous successful authorization performed from 152.32.252.153
1	21:09:31.233	'66036191': datacenter connecting failed [6]
1	21:10:10.342	'66036191': ping failed
0	21:10:11.295	'66036191': login on HeroCapitalPty-Server through DC#2 (ping: 101.61 ms)
0	21:10:11.420	'66036191': login datacenter on HeroCapitalPty-Server through DC#2 (ping: 101.61 ms)
0	21:10:11.952	'66036191': previous successful authorization performed from 152.32.252.153
1	21:35:22.847	'66036191': ping failed
1	21:35:22.893	'66036191': connect failed [ûÓÐÁ¬½Ó]
0	21:35:28.190	'66036191': login on HeroCapitalPty-Server through DC#2 (ping: n/a)
0	21:35:28.440	'66036191': login datacenter on HeroCapitalPty-Server through DC#2 (ping: n/a)
0	21:35:28.909	'66036191': previous successful authorization performed from 152.32.252.153
0	21:35:33.675	'66036191': auto connecting to a better access point DC#2-1 (ping is 2.75 ms)
0	21:35:33.862	'66036191': login on HeroCapitalPty-Server through DC#2-1 (ping: 2.75 ms)
0	21:35:33.956	'66036191': login datacenter on HeroCapitalPty-Server through DC#2-1 (ping: 2.75 ms)
0	21:35:34.440	'66036191': previous successful authorization performed from 152.32.252.153
1	22:44:22.626	'66036191': ping failed
1	22:44:22.626	'66036191': datacenter connecting failed [6]
0	22:44:23.454	'66036191': login on HeroCapitalPty-Server through DC#2 (ping: 5.72 ms)
0	22:44:23.673	'66036191': login datacenter on HeroCapitalPty-Server through DC#2 (ping: 5.72 ms)
0	22:44:24.126	'66036191': previous successful authorization performed from 152.32.252.153
0	22:44:24.923	'66036191': auto connecting to a better access point DC#2-1 (ping is 2.50 ms)
0	22:44:25.235	'66036191': login on HeroCapitalPty-Server through DC#2-1 (ping: 2.50 ms)
0	22:44:25.329	'66036191': login datacenter on HeroCapitalPty-Server through DC#2-1 (ping: 2.50 ms)
0	22:44:25.782	'66036191': previous successful authorization performed from 152.32.252.153
1	23:04:14.501	'66036191': datacenter connecting failed [6]
0	23:04:17.970	'66036191': login on HeroCapitalPty-Server through DC#2 (ping: 11.45 ms)
0	23:04:18.095	'66036191': login datacenter on HeroCapitalPty-Server through DC#2 (ping: 11.45 ms)
0	23:04:18.610	'66036191': previous successful authorization performed from 152.32.252.153
0	23:47:25.563	'66036191': login on HeroCapitalPty-Server through DC#2 (ping: 11.45 ms)
0	23:47:26.000	'66036191': login datacenter on HeroCapitalPty-Server through DC#2 (ping: 11.45 ms)
0	23:47:26.625	'66036191': previous successful authorization performed from 152.32.252.153
0	23:47:27.141	'66036191': ping to current access point DC#2 is 2.93 ms