1	22:21:19.620	'66036191': ping failed
0	22:21:19.620	'66036191': login datacenter on HeroCapitalPty-Server
0	22:21:20.073	'66036191': login on HeroCapitalPty-Server through DC#3 (ping: 70.23 ms)
0	22:21:20.589	'66036191': login datacenter on HeroCapitalPty-Server through DC#3 (ping: 70.23 ms)
0	22:21:20.823	'66036191': previous successful authorization performed from 152.32.252.153
0	22:21:21.261	'66036191': auto connecting to a better access point DC#2 (ping is 2.14 ms)
0	22:21:21.589	'66036191': login on HeroCapitalPty-Server through DC#2 (ping: 2.14 ms)
0	22:21:21.683	'66036191': login datacenter on HeroCapitalPty-Server through DC#2 (ping: 2.14 ms)
0	22:21:21.808	'66036191': previous successful authorization performed from 152.32.252.153
1	22:34:06.714	'66036191': ping failed
1	22:34:06.714	'66036191': datacenter connecting failed [6]
0	22:34:07.277	'66036191': login on HeroCapitalPty-Server through DC#3 (ping: 101.10 ms)
0	22:34:07.761	'66036191': login datacenter on HeroCapitalPty-Server through DC#3 (ping: 101.10 ms)
0	22:34:07.980	'66036191': previous successful authorization performed from 152.32.252.153
1	23:05:46.689	'66036191': datacenter connecting failed [6]
0	23:05:47.048	'66036191': login on HeroCapitalPty-Server through DC#3 (ping: 101.10 ms)
0	23:05:52.595	'66036191': login datacenter on HeroCapitalPty-Server through DC#3 (ping: 101.10 ms)
0	23:05:52.829	'66036191': previous successful authorization performed from 152.32.252.153
0	23:06:38.204	'66036191': login on HeroCapitalPty-Server through DC#3 (ping: 101.10 ms)
0	23:06:48.564	'66036191': login datacenter on HeroCapitalPty-Server through DC#3 (ping: 101.10 ms)
0	23:06:48.782	'66036191': previous successful authorization performed from 152.32.252.153