1	21:35:12.568	'66036191': ping failed
0	21:35:12.568	'66036191': login datacenter on HeroCapitalPty-Server
0	21:35:12.755	'66036191': login on HeroCapitalPty-Server through DC#2 (ping: 16.10 ms)
0	21:35:13.615	'66036191': login datacenter on HeroCapitalPty-Server through DC#2 (ping: 16.10 ms)
0	21:35:18.505	'66036191': previous successful authorization performed from 152.32.252.153
0	21:35:34.052	'66036191': auto connecting to a better access point DC#2-1 (ping is 45.65 ms)
0	21:35:34.255	'66036191': login on HeroCapitalPty-Server through DC#2-1 (ping: 45.65 ms)
0	21:35:34.521	'66036191': login datacenter on HeroCapitalPty-Server through DC#2-1 (ping: 45.65 ms)
0	21:35:34.990	'66036191': previous successful authorization performed from 152.32.252.153
1	21:38:34.719	'66036191': ping failed
0	21:38:34.719	'66036191': login datacenter on HeroCapitalPty-Server
0	21:38:35.016	'66036191': login on HeroCapitalPty-Server through DC#2 (ping: 116.75 ms)
0	21:39:44.688	'66036191': login on HeroCapitalPty-Server through DC#5 (ping: 177.90 ms)
0	21:40:50.750	'66036191': login on HeroCapitalPty-Server through DC#3 (ping: 340.11 ms)
1	21:41:55.844	'66036191': connect failed [ûÓÐÁ¬½Ó]
0	21:42:01.875	'66036191': login on HeroCapitalPty-Server through DC#2 (ping: n/a)
0	21:43:08.672	'66036191': login on HeroCapitalPty-Server through DC#3 (ping: n/a)
0	21:44:15.266	'66036191': login on HeroCapitalPty-Server through DC#2-1 (ping: n/a)
0	21:45:22.610	'66036191': login on HeroCapitalPty-Server through DC#5 (ping: n/a)
0	21:45:28.594	'66036191': login datacenter on HeroCapitalPty-Server through DC#5 (ping: n/a)
0	21:45:29.704	'66036191': previous successful authorization performed from 152.32.252.153
0	21:45:45.563	'66036191': ping to current access point DC#5 is 206.41 ms