1	08:30:30.428	'66036191': ping failed
0	08:30:30.428	'66036191': login datacenter on HeroCapitalPty-Server
0	08:30:30.803	'66036191': login on HeroCapitalPty-Server through DC#3 (ping: 76.67 ms)
0	08:31:37.006	'66036191': login on HeroCapitalPty-Server through DC#5 (ping: 86.88 ms)
0	08:31:37.787	'66036191': login datacenter on HeroCapitalPty-Server through DC#5 (ping: 86.88 ms)
0	08:31:38.381	'66036191': previous successful authorization performed from 152.32.252.153
0	08:31:39.553	'66036191': auto connecting to a better access point DC#2-1 (ping is 20.14 ms)
0	08:31:39.772	'66036191': login on HeroCapitalPty-Server through DC#2-1 (ping: 20.14 ms)
0	08:31:40.444	'66036191': login datacenter on HeroCapitalPty-Server through DC#2-1 (ping: 20.14 ms)
0	08:31:40.881	'66036191': previous successful authorization performed from 152.32.252.153
0	23:04:40.616	'66036191': login on HeroCapitalPty-Server through DC#2-1 (ping: 20.14 ms)
0	23:04:43.148	'66036191': login datacenter on HeroCapitalPty-Server through DC#2-1 (ping: 20.14 ms)
0	23:04:46.773	'66036191': previous successful authorization performed from 152.32.252.153
0	23:04:49.616	'66036191': ping to current access point DC#2-1 is 4.98 ms
1	23:05:23.179	'66036191': ping failed
1	23:05:23.179	'66036191': datacenter connecting failed [6]
0	23:05:23.351	'66036191': login on HeroCapitalPty-Server through DC#2 (ping: 29.78 ms)
0	23:05:25.382	'66036191': login datacenter on HeroCapitalPty-Server through DC#2 (ping: 29.78 ms)
0	23:05:26.445	'66036191': previous successful authorization performed from 152.32.252.153