1	20:35:12.042	'66036191': ping failed
1	20:35:12.042	'66036191': datacenter connecting failed [6]
0	20:35:12.839	'66036191': login on HeroCapitalPty-Server through DC#2 (ping: 21.20 ms)
0	20:35:12.933	'66036191': login datacenter on HeroCapitalPty-Server through DC#2 (ping: 21.20 ms)
0	20:35:13.464	'66036191': previous successful authorization performed from 152.32.252.153
0	20:35:15.058	'66036191': auto connecting to a better access point DC#2-1 (ping is 3.68 ms)
0	20:35:15.308	'66036191': login on HeroCapitalPty-Server through DC#2-1 (ping: 3.68 ms)
0	20:35:15.729	'66036191': login datacenter on HeroCapitalPty-Server through DC#2-1 (ping: 3.68 ms)
0	20:35:16.198	'66036191': previous successful authorization performed from 152.32.252.153
1	22:01:39.768	'66036191': ping failed
1	22:01:39.768	'66036191': datacenter connecting failed [6]
0	22:01:40.549	'66036191': login on HeroCapitalPty-Server through DC#2 (ping: 17.73 ms)
0	22:01:41.002	'66036191': login datacenter on HeroCapitalPty-Server through DC#2 (ping: 17.73 ms)
0	22:01:41.971	'66036191': previous successful authorization performed from 152.32.252.153
0	22:01:44.018	'66036191': auto connecting to a better access point DC#2-1 (ping is 24.67 ms)
0	22:01:44.174	'66036191': login on HeroCapitalPty-Server through DC#2-1 (ping: 24.67 ms)
0	22:01:47.299	'66036191': login datacenter on HeroCapitalPty-Server through DC#2-1 (ping: 24.67 ms)
0	22:01:47.861	'66036191': previous successful authorization performed from 152.32.252.153