1	18:01:22.000	'66036191': ping failed
0	18:01:22.094	'66036191': login datacenter on HeroCapitalPty-Server
0	18:01:23.625	'66036191': login on HeroCapitalPty-Server through DC#4 (ping: 89.63 ms)
0	18:01:25.063	'66036191': login datacenter on HeroCapitalPty-Server through DC#4 (ping: 89.63 ms)
0	18:01:25.438	'66036191': previous successful authorization performed from 152.32.252.153
0	18:01:28.438	'66036191': auto connecting to a better access point DC#2 (ping is 32.61 ms)
0	18:01:28.828	'66036191': login on HeroCapitalPty-Server through DC#2 (ping: 32.61 ms)
0	18:01:29.500	'66036191': login datacenter on HeroCapitalPty-Server through DC#2 (ping: 32.61 ms)
0	18:01:29.797	'66036191': previous successful authorization performed from 152.32.252.153
0	18:07:34.031	'66036191': login on HeroCapitalPty-Server through DC#2 (ping: 32.61 ms)
0	18:07:35.219	'66036191': login datacenter on HeroCapitalPty-Server through DC#2 (ping: 32.61 ms)
0	18:07:35.500	'66036191': previous successful authorization performed from 152.32.252.153
1	20:18:32.976	'66036191': datacenter connecting failed [6]
0	20:18:33.413	'66036191': login on HeroCapitalPty-Server through DC#4 (ping: 91.85 ms)
0	20:18:38.663	'66036191': login datacenter on HeroCapitalPty-Server through DC#4 (ping: 91.85 ms)
0	20:18:39.054	'66036191': previous successful authorization performed from 152.32.252.153
0	20:18:40.491	'66036191': auto connecting to a better access point DC#2 (ping is 52.64 ms)
0	20:18:40.913	'66036191': login on HeroCapitalPty-Server through DC#2 (ping: 52.64 ms)
0	20:18:43.741	'66036191': login datacenter on HeroCapitalPty-Server through DC#2 (ping: 52.64 ms)
0	20:18:44.038	'66036191': previous successful authorization performed from 152.32.252.153
0	20:23:36.351	'66036191': login datacenter on HeroCapitalPty-Server
0	20:23:40.757	'66036191': login on HeroCapitalPty-Server through DC#4 (ping: 90.86 ms)
0	20:23:42.523	'66036191': login datacenter on HeroCapitalPty-Server through DC#4 (ping: 90.86 ms)
0	20:23:42.851	'66036191': previous successful authorization performed from 152.32.252.153
0	20:32:16.773	'66036191': login datacenter on HeroCapitalPty-Server through DC#4 (ping: 90.86 ms)
1	20:32:16.773	'66036191': ping failed
0	20:32:18.788	'66036191': login on HeroCapitalPty-Server through DC#4 (ping: 90.86 ms)
0	20:32:19.460	'66036191': login datacenter on HeroCapitalPty-Server through DC#4 (ping: 90.86 ms)
0	20:32:19.773	'66036191': previous successful authorization performed from 152.32.252.153
0	20:33:44.929	'66036191': login on HeroCapitalPty-Server through DC#4 (ping: 90.86 ms)
0	20:33:47.101	'66036191': login datacenter on HeroCapitalPty-Server through DC#4 (ping: 90.86 ms)
0	20:33:47.413	'66036191': previous successful authorization performed from 152.32.252.153
0	20:35:19.351	'66036191': login datacenter on HeroCapitalPty-Server through DC#4 (ping: 90.86 ms)
0	20:35:23.445	'66036191': login on HeroCapitalPty-Server through DC#4 (ping: 90.86 ms)
0	20:35:24.898	'66036191': login datacenter on HeroCapitalPty-Server through DC#4 (ping: 90.86 ms)
0	20:35:25.241	'66036191': previous successful authorization performed from 152.32.252.153
0	20:37:42.116	'66036191': login on HeroCapitalPty-Server through DC#4 (ping: 90.86 ms)
0	20:37:45.460	'66036191': login datacenter on HeroCapitalPty-Server through DC#4 (ping: 90.86 ms)
0	20:37:45.820	'66036191': previous successful authorization performed from 152.32.252.153
0	20:40:52.835	'66036191': login on HeroCapitalPty-Server through DC#4 (ping: 90.86 ms)
0	20:40:54.038	'66036191': login datacenter on HeroCapitalPty-Server through DC#4 (ping: 90.86 ms)
0	20:40:54.366	'66036191': previous successful authorization performed from 152.32.252.153