1	15:33:24.251	'66036191': ping failed
1	15:33:24.251	'66036191': datacenter connecting failed [6]
0	15:33:28.736	'66036191': login on HeroCapitalPty-Server through DC#5 (ping: 87.38 ms)
0	15:33:33.173	'66036191': login datacenter on HeroCapitalPty-Server through DC#5 (ping: 87.38 ms)
0	15:33:34.595	'66036191': previous successful authorization performed from 152.32.252.153
0	15:33:44.142	'66036191': auto connecting to a better access point DC#2 (ping is 4.06 ms)
0	15:33:45.173	'66036191': login on HeroCapitalPty-Server through DC#2 (ping: 4.06 ms)
0	15:33:45.267	'66036191': login datacenter on HeroCapitalPty-Server through DC#2 (ping: 4.06 ms)
0	15:33:45.408	'66036191': previous successful authorization performed from 152.32.252.153
1	16:30:28.986	'66036191': ping failed
1	16:30:28.986	'66036191': datacenter connecting failed [6]
0	16:30:29.408	'66036191': login on HeroCapitalPty-Server through DC#3 (ping: 72.25 ms)
0	16:30:33.236	'66036191': login datacenter on HeroCapitalPty-Server through DC#3 (ping: 72.25 ms)
0	16:30:33.689	'66036191': previous successful authorization performed from 152.32.252.153
1	18:48:45.704	'66036191': ping failed
1	18:48:45.720	'66036191': datacenter connecting failed [6]
0	18:48:46.298	'66036191': login on HeroCapitalPty-Server through DC#5 (ping: 87.82 ms)
0	18:48:49.564	'66036191': login datacenter on HeroCapitalPty-Server through DC#5 (ping: 87.82 ms)
0	18:48:50.376	'66036191': previous successful authorization performed from 152.32.252.153
0	18:48:57.767	'66036191': auto connecting to a better access point DC#2 (ping is 3.88 ms)
0	18:48:58.095	'66036191': login on HeroCapitalPty-Server through DC#2 (ping: 3.88 ms)
0	18:48:58.220	'66036191': login datacenter on HeroCapitalPty-Server through DC#2 (ping: 3.88 ms)
0	18:48:58.345	'66036191': previous successful authorization performed from 152.32.252.153