1	21:08:23.529	'66036191': datacenter connecting failed [6]
0	21:08:23.779	'66036191': login on HeroCapitalPty-Server through DC#2 (ping: 3.24 ms)
0	21:08:23.904	'66036191': login datacenter on HeroCapitalPty-Server through DC#2 (ping: 3.24 ms)
0	21:08:24.029	'66036191': previous successful authorization performed from 152.32.252.153
0	21:08:24.779	'66036191': ping to current access point DC#2 is 4.86 ms
0	21:36:13.121	'66036191': login datacenter on HeroCapitalPty-Server through DC#2 (ping: 4.86 ms)
0	21:36:13.387	'66036191': login on HeroCapitalPty-Server through DC#2 (ping: 4.86 ms)
0	21:36:13.605	'66036191': login datacenter on HeroCapitalPty-Server through DC#2 (ping: 4.86 ms)
0	21:36:13.793	'66036191': previous successful authorization performed from 152.32.252.153
1	21:38:13.996	'66036191': ping failed
0	21:38:14.324	'66036191': login on HeroCapitalPty-Server through DC#2 (ping: 4.86 ms)
0	21:38:15.059	'66036191': login datacenter on HeroCapitalPty-Server through DC#2 (ping: 4.86 ms)
0	21:38:15.262	'66036191': previous successful authorization performed from 152.32.252.153
0	21:40:20.418	'66036191': login datacenter on HeroCapitalPty-Server through DC#2 (ping: 4.86 ms)
0	21:40:20.684	'66036191': login on HeroCapitalPty-Server through DC#2 (ping: 4.86 ms)
0	21:40:20.824	'66036191': login datacenter on HeroCapitalPty-Server through DC#2 (ping: 4.86 ms)
0	21:40:20.965	'66036191': previous successful authorization performed from 152.32.252.153
0	21:41:10.605	'66036191': login on HeroCapitalPty-Server through DC#2 (ping: 4.86 ms)
0	21:41:11.027	'66036191': login datacenter on HeroCapitalPty-Server through DC#2 (ping: 4.86 ms)
0	21:41:11.152	'66036191': previous successful authorization performed from 152.32.252.153