1	22:30:04.353	'66036191': datacenter connecting failed [6]
0	22:30:04.713	'66036191': login on HeroCapitalPty-Server through DC#2 (ping: 4.64 ms)
0	22:30:05.306	'66036191': login datacenter on HeroCapitalPty-Server through DC#2 (ping: 4.64 ms)
0	22:30:06.322	'66036191': previous successful authorization performed from 152.32.252.153
0	22:30:09.072	'66036191': ping to current access point DC#2 is 3.39 ms
0	22:31:20.806	'66036191': login datacenter on HeroCapitalPty-Server
0	22:31:21.291	'66036191': login on HeroCapitalPty-Server through DC#4 (ping: 90.92 ms)
0	22:31:45.306	'66036191': login datacenter on HeroCapitalPty-Server through DC#4 (ping: 90.92 ms)
0	22:31:45.572	'66036191': previous successful authorization performed from 152.32.252.153
0	22:32:58.697	'66036191': login datacenter on HeroCapitalPty-Server through DC#4 (ping: 90.92 ms)
0	22:32:59.228	'66036191': login on HeroCapitalPty-Server through DC#4 (ping: 90.92 ms)
0	22:33:01.041	'66036191': login datacenter on HeroCapitalPty-Server through DC#4 (ping: 90.92 ms)
0	22:33:01.338	'66036191': previous successful authorization performed from 152.32.252.153
0	22:35:03.009	'66036191': login on HeroCapitalPty-Server through DC#4 (ping: 90.92 ms)
0	22:35:05.056	'66036191': login datacenter on HeroCapitalPty-Server through DC#4 (ping: 90.92 ms)
0	22:35:05.338	'66036191': previous successful authorization performed from 152.32.252.153
1	22:36:05.963	'66036191': datacenter connecting failed [6]
0	22:36:06.322	'66036191': login on HeroCapitalPty-Server through DC#4 (ping: 90.92 ms)
0	22:36:21.791	'66036191': login datacenter on HeroCapitalPty-Server through DC#4 (ping: 90.92 ms)
0	22:36:22.056	'66036191': previous successful authorization performed from 152.32.252.153
1	22:36:40.838	'66036191': datacenter connecting failed [6]
0	22:36:41.228	'66036191': login on HeroCapitalPty-Server through DC#4 (ping: 90.92 ms)
0	22:36:42.588	'66036191': login datacenter on HeroCapitalPty-Server through DC#4 (ping: 90.92 ms)
0	22:36:42.869	'66036191': previous successful authorization performed from 152.32.252.153
1	22:48:43.525	'66036191': ping failed
0	22:48:45.494	'66036191': login on HeroCapitalPty-Server through DC#4 (ping: 90.92 ms)
0	22:49:48.447	'66036191': login datacenter on HeroCapitalPty-Server through DC#4 (ping: 90.92 ms)
0	22:49:54.416	'66036191': login on HeroCapitalPty-Server through DC#4 (ping: 90.92 ms)
0	22:50:54.900	'66036191': login datacenter on HeroCapitalPty-Server
0	22:50:55.556	'66036191': auto connecting to a better access point DC#2 (ping is 3.90 ms)
0	22:51:00.416	'66036191': login on HeroCapitalPty-Server through DC#2 (ping: 3.90 ms)
0	22:51:03.494	'66036191': login datacenter on HeroCapitalPty-Server through DC#2 (ping: 3.90 ms)
0	22:51:03.634	'66036191': previous successful authorization performed from 152.32.252.153
1	22:52:03.556	'66036191': ping failed
1	22:52:03.556	'66036191': datacenter connecting failed [6]
1	22:52:05.931	'66036191': connect failed [ûÓÐÁ¬½Ó]
0	22:52:21.400	'66036191': login on HeroCapitalPty-Server through DC#2 (ping: n/a)
0	22:52:21.478	'66036191': login datacenter on HeroCapitalPty-Server through DC#2 (ping: n/a)
0	22:52:21.603	'66036191': previous successful authorization performed from 152.32.252.153
0	22:52:22.306	'66036191': ping to current access point DC#2 is 3.40 ms
1	22:53:21.525	'66036191': ping failed
1	22:53:21.525	'66036191': datacenter connecting failed [6]
0	22:53:24.213	'66036191': login on HeroCapitalPty-Server through DC#4 (ping: 93.29 ms)
0	22:53:24.994	'66036191': login datacenter on HeroCapitalPty-Server through DC#4 (ping: 93.29 ms)
0	22:53:25.259	'66036191': previous successful authorization performed from 152.32.252.153
1	23:29:25.730	'66036191': datacenter connecting failed [6]
0	23:29:26.121	'66036191': login on HeroCapitalPty-Server through DC#4 (ping: 93.29 ms)
0	23:29:27.683	'66036191': login datacenter on HeroCapitalPty-Server through DC#4 (ping: 93.29 ms)
0	23:29:27.949	'66036191': previous successful authorization performed from 152.32.252.153