1	03:04:00.500	'66036191': ping failed
0	03:04:00.500	'66036191': login datacenter on HeroCapitalPty-Server
0	03:04:01.578	'66036191': login on HeroCapitalPty-Server through DC#3 (ping: 115.91 ms)
0	03:04:22.094	'66036191': login datacenter on HeroCapitalPty-Server through DC#3 (ping: 115.91 ms)
0	03:04:26.281	'66036191': previous successful authorization performed from 152.32.252.153
0	03:04:33.719	'66036191': auto connecting to a better access point DC#2 (ping is 36.34 ms)
0	03:04:34.859	'66036191': login on HeroCapitalPty-Server through DC#2 (ping: 36.34 ms)
0	03:04:35.297	'66036191': login datacenter on HeroCapitalPty-Server through DC#2 (ping: 36.34 ms)
0	03:04:35.781	'66036191': previous successful authorization performed from 152.32.252.153
1	16:15:32.509	'66036191': ping failed
0	16:15:35.603	'66036191': login datacenter on HeroCapitalPty-Server
0	16:15:37.916	'66036191': login on HeroCapitalPty-Server through DC#2-1 (ping: 37.88 ms)
0	16:15:38.431	'66036191': login datacenter on HeroCapitalPty-Server through DC#2-1 (ping: 37.88 ms)
0	16:15:38.931	'66036191': previous successful authorization performed from 152.32.252.153
0	16:15:51.103	'66036191': ping to current access point DC#2-1 is 4.80 ms
1	16:30:38.744	'66036191': datacenter connecting failed [6]
0	16:30:39.166	'66036191': login on HeroCapitalPty-Server through DC#3 (ping: 73.87 ms)
0	16:31:45.088	'66036191': login on HeroCapitalPty-Server through DC#3 (ping: 73.87 ms)
0	16:32:55.056	'66036191': login on HeroCapitalPty-Server through DC#5 (ping: 199.68 ms)
1	16:34:00.134	'66036191': connect failed [ûÓÐÁ¬½Ó]
0	16:34:05.463	'66036191': login on HeroCapitalPty-Server through DC#2 (ping: n/a)
0	16:34:05.603	'66036191': login datacenter on HeroCapitalPty-Server through DC#2 (ping: n/a)
0	16:34:06.541	'66036191': previous successful authorization performed from 152.32.252.153
0	16:34:23.556	'66036191': ping to current access point DC#2 is 197.90 ms