1	20:15:39.260	'66036191': ping failed
1	20:15:39.276	'66036191': datacenter connecting failed [6]
0	20:15:40.089	'66036191': login on HeroCapitalPty-Server through DC#3 (ping: 63.91 ms)
0	20:15:41.057	'66036191': login datacenter on HeroCapitalPty-Server through DC#3 (ping: 63.91 ms)
0	20:15:41.307	'66036191': previous successful authorization performed from 152.32.252.153
0	20:15:46.026	'66036191': auto connecting to a better access point DC#2 (ping is 3.03 ms)
0	20:15:46.401	'66036191': login on HeroCapitalPty-Server through DC#2 (ping: 3.03 ms)
0	20:15:46.495	'66036191': login datacenter on HeroCapitalPty-Server through DC#2 (ping: 3.03 ms)
0	20:15:46.870	'66036191': previous successful authorization performed from 152.32.252.153
1	22:08:05.164	'66036191': datacenter connecting failed [6]
0	22:08:05.632	'66036191': login on HeroCapitalPty-Server through DC#3 (ping: 63.79 ms)
0	22:08:06.132	'66036191': login datacenter on HeroCapitalPty-Server through DC#3 (ping: 63.79 ms)
0	22:08:06.445	'66036191': previous successful authorization performed from 152.32.252.153
0	22:08:10.148	'66036191': auto connecting to a better access point DC#2 (ping is 4.20 ms)
0	22:08:10.476	'66036191': login on HeroCapitalPty-Server through DC#2 (ping: 4.20 ms)
0	22:08:11.211	'66036191': login datacenter on HeroCapitalPty-Server through DC#2 (ping: 4.20 ms)
0	22:08:11.336	'66036191': previous successful authorization performed from 152.32.252.153
1	22:09:51.304	'66036191': ping failed
0	22:09:51.304	'66036191': login datacenter on HeroCapitalPty-Server
0	22:09:52.211	'66036191': login on HeroCapitalPty-Server through DC#3 (ping: 61.89 ms)
0	22:10:02.351	'66036191': login datacenter on HeroCapitalPty-Server through DC#3 (ping: 61.89 ms)
0	22:10:02.882	'66036191': previous successful authorization performed from 152.32.252.153