1	21:30:45.342	'66036191': ping failed
1	21:30:45.358	'66036191': datacenter connecting failed [6]
0	21:30:45.858	'66036191': login on HeroCapitalPty-Server through DC#2-1 (ping: 36.69 ms)
0	21:30:48.326	'66036191': login datacenter on HeroCapitalPty-Server through DC#2-1 (ping: 36.69 ms)
0	21:30:49.904	'66036191': previous successful authorization performed from 152.32.252.153
0	21:31:05.858	'66036191': auto connecting to a better access point DC#2 (ping is 93.36 ms)
0	21:31:06.420	'66036191': login on HeroCapitalPty-Server through DC#2 (ping: 93.36 ms)
0	21:32:11.951	'66036191': login on HeroCapitalPty-Server through DC#2 (ping: 93.36 ms)
0	21:33:26.795	'66036191': login on HeroCapitalPty-Server through DC#3 (ping: 147.21 ms)
0	21:34:44.936	'66036191': login on HeroCapitalPty-Server through DC#5 (ping: 174.16 ms)
0	21:35:53.748	'66036191': login on HeroCapitalPty-Server through DC#2-1 (ping: 181.53 ms)
0	21:36:01.623	'66036191': login datacenter on HeroCapitalPty-Server through DC#2-1 (ping: 181.53 ms)
0	21:36:02.326	'66036191': previous successful authorization performed from 152.32.252.153
1	21:40:04.467	'66036191': ping failed
0	21:40:04.858	'66036191': login datacenter on HeroCapitalPty-Server
1	21:40:04.998	'66036191': connect failed [ûÓÐÁ¬½Ó]
0	21:40:12.436	'66036191': login on HeroCapitalPty-Server through DC#2 (ping: n/a)
0	21:41:19.279	'66036191': login on HeroCapitalPty-Server through DC#2 (ping: n/a)
0	21:42:23.608	'66036191': login on HeroCapitalPty-Server through DC#2 (ping: n/a)
0	21:42:29.295	'66036191': login datacenter on HeroCapitalPty-Server through DC#2 (ping: n/a)
0	21:42:30.998	'66036191': previous successful authorization performed from 152.32.252.153
0	21:42:36.217	'66036191': ping to current access point DC#2 is 88.53 ms