1	09:59:21.036	'600377': ping failed
1	09:59:21.052	'600377': datacenter connecting failed [6]
0	09:59:21.833	'600377': login on PUPrime-Live through DC1 - NY (ping: 213.30 ms)
0	09:59:23.646	'600377': login datacenter on PUPrime-Live through DC1 - NY (ping: 213.30 ms)
0	09:59:24.552	'600377': previous successful authorization performed from 152.32.252.153
0	10:00:59.364	'600377': auto connecting to a better access point DC2 - NY (ping is 206.62 ms)
0	10:01:00.130	'600377': login on PUPrime-Live through DC2 - NY (ping: 206.62 ms)
0	10:01:02.005	'600377': login datacenter on PUPrime-Live through DC2 - NY (ping: 206.62 ms)
0	10:01:02.896	'600377': previous successful authorization performed from 152.32.252.153
1	10:10:09.068	'600377': ping failed
1	10:10:09.068	'600377': datacenter connecting failed [6]
0	10:10:09.927	'600377': login on PUPrime-Live through DC4 - HK (ping: 219.87 ms)
0	10:10:11.755	'600377': login datacenter on PUPrime-Live through DC4 - HK (ping: 219.87 ms)
0	10:10:12.443	'600377': previous successful authorization performed from 152.32.252.153
1	12:19:08.729	'600377': datacenter connecting failed [6]
0	12:19:09.807	'600377': login on PUPrime-Live through DC4 - HK (ping: 219.87 ms)
0	12:19:12.729	'600377': login datacenter on PUPrime-Live through DC4 - HK (ping: 219.87 ms)
0	12:19:13.635	'600377': previous successful authorization performed from 152.32.252.153
0	12:20:50.369	'600377': auto connecting to a better access point DC2 - NY (ping is 208.10 ms)
0	12:20:51.151	'600377': login on PUPrime-Live through DC2 - NY (ping: 208.10 ms)
0	12:20:52.994	'600377': login datacenter on PUPrime-Live through DC2 - NY (ping: 208.10 ms)
0	12:20:53.869	'600377': previous successful authorization performed from 152.32.252.153
1	16:14:33.468	'600377': ping failed
1	16:14:33.468	'600377': datacenter connecting failed [6]
0	16:14:41.718	'600377': login on PUPrime-Live through DC3 - LD (ping: 230.68 ms)
0	16:14:43.999	'600377': login datacenter on PUPrime-Live through DC3 - LD (ping: 230.68 ms)
0	16:14:44.874	'600377': previous successful authorization performed from 152.32.252.153
0	16:16:18.374	'600377': auto connecting to a better access point DC2 - NY (ping is 203.48 ms)
0	16:16:19.124	'600377': login on PUPrime-Live through DC2 - NY (ping: 203.48 ms)
0	16:16:20.952	'600377': login datacenter on PUPrime-Live through DC2 - NY (ping: 203.48 ms)
0	16:16:22.468	'600377': previous successful authorization performed from 152.32.252.153
1	17:26:01.192	'600377': ping failed
1	17:26:01.192	'600377': datacenter connecting failed [6]
0	17:26:02.020	'600377': login on PUPrime-Live through DC4 - HK (ping: 220.98 ms)
0	17:26:03.754	'600377': login datacenter on PUPrime-Live through DC4 - HK (ping: 220.98 ms)
0	17:26:04.426	'600377': previous successful authorization performed from 152.32.252.153
0	17:27:39.379	'600377': auto connecting to a better access point DC2 - NY (ping is 208.43 ms)
0	17:27:40.129	'600377': login on PUPrime-Live through DC2 - NY (ping: 208.43 ms)
0	17:27:41.848	'600377': login datacenter on PUPrime-Live through DC2 - NY (ping: 208.43 ms)
0	17:27:42.723	'600377': previous successful authorization performed from 152.32.252.153
1	20:59:22.058	'600377': ping failed
1	20:59:22.073	'600377': datacenter connecting failed [6]
0	20:59:22.902	'600377': login on PUPrime-Live through DC4 - HK (ping: 221.05 ms)
0	20:59:24.464	'600377': login datacenter on PUPrime-Live through DC4 - HK (ping: 221.05 ms)
0	20:59:25.136	'600377': previous successful authorization performed from 152.32.252.153
0	21:01:00.495	'600377': ping to current access point DC4 - HK is 221.09 ms