0	10:07:29.426	'66036191': login on HeroCapitalPty-Server through DC#5 (ping: 132.22 ms)
0	10:08:30.301	'66036191': login datacenter on HeroCapitalPty-Server
0	10:08:35.144	'66036191': auto connecting to a better access point DC#2-1 (ping is 2.67 ms)
0	10:08:36.285	'66036191': login on HeroCapitalPty-Server through DC#2-1 (ping: 2.67 ms)
0	10:08:36.660	'66036191': login datacenter on HeroCapitalPty-Server through DC#2-1 (ping: 2.67 ms)
0	10:08:37.176	'66036191': previous successful authorization performed from 152.32.252.153
1	17:36:48.114	'66036191': datacenter connecting failed [6]
0	17:36:49.551	'66036191': login on HeroCapitalPty-Server through DC#2 (ping: 25.71 ms)
0	17:36:50.457	'66036191': login datacenter on HeroCapitalPty-Server through DC#2 (ping: 25.71 ms)
0	17:36:51.723	'66036191': previous successful authorization performed from 152.32.252.153
0	17:37:14.660	'66036191': ping to current access point DC#2 is 93.86 ms
1	21:31:21.564	'66036191': ping failed
1	21:31:21.564	'66036191': datacenter connecting failed [6]
0	21:31:22.985	'66036191': login on HeroCapitalPty-Server through DC#3 (ping: 114.35 ms)
0	21:32:28.767	'66036191': login on HeroCapitalPty-Server through DC#5 (ping: 134.05 ms)
0	21:33:34.610	'66036191': login on HeroCapitalPty-Server through DC#2-1 (ping: 139.28 ms)
0	21:33:34.939	'66036191': login datacenter on HeroCapitalPty-Server through DC#2-1 (ping: 139.28 ms)
0	21:33:35.423	'66036191': previous successful authorization performed from 152.32.252.153
0	21:34:11.548	'66036191': ping to current access point DC#2-1 is 67.02 ms
1	21:35:55.079	'66036191': ping failed
0	21:35:55.079	'66036191': login datacenter on HeroCapitalPty-Server
0	21:35:55.907	'66036191': login on HeroCapitalPty-Server through DC#5 (ping: 190.31 ms)
0	21:35:57.954	'66036191': login datacenter on HeroCapitalPty-Server through DC#5 (ping: 190.31 ms)
0	21:35:58.907	'66036191': previous successful authorization performed from 152.32.252.153