1	01:43:35.416	'66036191': ping failed
1	01:43:35.416	'66036191': datacenter connecting failed [6]
0	01:43:36.229	'66036191': login on HeroCapitalPty-Server through DC#2 (ping: 42.98 ms)
0	01:43:39.854	'66036191': login datacenter on HeroCapitalPty-Server through DC#2 (ping: 42.98 ms)
0	01:43:41.448	'66036191': auto connecting to a better access point DC#2-1 (ping is 3.40 ms)
0	01:43:46.838	'66036191': login on HeroCapitalPty-Server through DC#2-1 (ping: 3.40 ms)
0	01:43:47.151	'66036191': login datacenter on HeroCapitalPty-Server through DC#2-1 (ping: 3.40 ms)
0	01:43:47.635	'66036191': previous successful authorization performed from 152.32.252.153
1	01:46:47.307	'66036191': ping failed
1	01:46:47.307	'66036191': datacenter connecting failed [6]
0	01:46:48.432	'66036191': login on HeroCapitalPty-Server through DC#2 (ping: 25.07 ms)
0	01:47:54.463	'66036191': login on HeroCapitalPty-Server through DC#5 (ping: 88.61 ms)
0	01:49:00.948	'66036191': login on HeroCapitalPty-Server through DC#3 (ping: 94.59 ms)
1	01:50:06.198	'66036191': connect failed [ûÓÐÁ¬½Ó]
0	01:50:13.541	'66036191': login on HeroCapitalPty-Server through DC#2 (ping: n/a)
0	01:50:28.104	'66036191': login datacenter on HeroCapitalPty-Server through DC#2 (ping: n/a)
0	01:50:31.010	'66036191': ping to current access point DC#2 is 122.26 ms
0	01:50:31.260	'66036191': previous successful authorization performed from 152.32.252.153