0	00:18:03.202	'3001658': login on BroadmanVictory-Live through DC HK2 (ping: 2.15 ms)
0	00:18:03.577	'3001658': login datacenter on BroadmanVictory-Live through DC HK2 (ping: 2.15 ms)
0	00:18:03.702	'3001658': previous successful authorization performed from 152.32.128.46
0	00:18:03.780	'3001658': auto connecting to a better access point DC HK3 (ping is 1.93 ms)
0	00:18:04.077	'3001658': login on BroadmanVictory-Live through DC HK3 (ping: 1.93 ms)
0	00:18:04.452	'3001658': login datacenter on BroadmanVictory-Live through DC HK3 (ping: 1.93 ms)
0	00:18:04.561	'3001658': previous successful authorization performed from 152.32.128.46
0	00:19:20.515	'3001658': login on BroadmanVictory-Live through DC HK4 (ping: 2.77 ms)
0	00:19:20.593	'3001658': login datacenter on BroadmanVictory-Live through DC HK4 (ping: 2.77 ms)
0	00:19:20.687	'3001658': previous successful authorization performed from 152.32.128.46
1	00:57:54.725	'3001658': datacenter connecting failed [6]
0	00:58:16.085	'3001658': login on BroadmanVictory-Live through DC HK3 (ping: 1.93 ms)
0	00:58:16.444	'3001658': login datacenter on BroadmanVictory-Live through DC HK3 (ping: 1.93 ms)
0	00:58:16.585	'3001658': previous successful authorization performed from 152.32.128.46
1	01:37:58.676	'3001658': ping failed
0	01:37:59.035	'3001658': login on BroadmanVictory-Live through DC HK3 (ping: 1.93 ms)
0	01:37:59.441	'3001658': login datacenter on BroadmanVictory-Live through DC HK3 (ping: 1.93 ms)
0	01:37:59.582	'3001658': previous successful authorization performed from 152.32.128.46
0	01:37:59.786	'3001658': ping to current access point DC HK3 is 1.88 ms
0	02:18:57.918	'3001658': login on BroadmanVictory-Live through DC HK3 (ping: 1.88 ms)
0	02:18:58.309	'3001658': login datacenter on BroadmanVictory-Live through DC HK3 (ping: 1.88 ms)
0	02:18:58.418	'3001658': previous successful authorization performed from 152.32.128.46
1	02:57:20.439	'3001658': ping failed
0	02:57:20.470	'3001658': login datacenter on BroadmanVictory-Live
1	02:57:20.470	'3001658': ping failed
0	02:57:20.798	'3001658': login on BroadmanVictory-Live through DC HK2 (ping: 2.77 ms)
0	02:57:21.157	'3001658': login datacenter on BroadmanVictory-Live through DC HK2 (ping: 2.77 ms)
0	02:57:21.298	'3001658': previous successful authorization performed from 152.32.128.46
0	02:57:21.361	'3001658': auto connecting to a better access point DC HK3 (ping is 1.96 ms)
0	02:57:21.704	'3001658': login on BroadmanVictory-Live through DC HK3 (ping: 1.96 ms)
0	02:57:22.079	'3001658': login datacenter on BroadmanVictory-Live through DC HK3 (ping: 1.96 ms)
0	02:57:22.220	'3001658': previous successful authorization performed from 152.32.128.46
0	03:02:45.347	'3001658': login on BroadmanVictory-Live through DC HK3 (ping: 1.96 ms)
0	03:02:45.722	'3001658': login datacenter on BroadmanVictory-Live through DC HK3 (ping: 1.96 ms)
0	03:02:45.863	'3001658': previous successful authorization performed from 152.32.128.46
1	04:16:49.594	'3001658': ping failed
1	04:16:49.609	'3001658': datacenter connecting failed [6]
0	04:16:49.922	'3001658': login on BroadmanVictory-Live through DC HK2 (ping: 2.12 ms)
0	04:16:50.312	'3001658': login datacenter on BroadmanVictory-Live through DC HK2 (ping: 2.12 ms)
0	04:16:50.453	'3001658': previous successful authorization performed from 152.32.128.46
0	04:16:50.515	'3001658': ping to current access point DC HK2 is 2.08 ms
0	05:07:16.051	'3001658': login on BroadmanVictory-Live through DC HK2 (ping: 2.08 ms)
0	05:07:16.426	'3001658': login datacenter on BroadmanVictory-Live through DC HK2 (ping: 2.08 ms)
0	05:07:16.566	'3001658': previous successful authorization performed from 152.32.128.46
1	05:45:18.238	'3001658': ping failed
1	05:45:18.238	'3001658': datacenter connecting failed [6]
0	05:45:18.566	'3001658': login on BroadmanVictory-Live through DC HK3 (ping: 2.02 ms)
0	05:45:18.941	'3001658': login datacenter on BroadmanVictory-Live through DC HK3 (ping: 2.02 ms)
0	05:45:19.082	'3001658': previous successful authorization performed from 152.32.128.46
0	05:45:19.097	'3001658': auto connecting to a better access point DC HK2 (ping is 2.76 ms)
0	05:45:19.488	'3001658': login on BroadmanVictory-Live through DC HK2 (ping: 2.76 ms)
0	05:45:19.800	'3001658': login datacenter on BroadmanVictory-Live through DC HK2 (ping: 2.76 ms)
0	05:45:19.941	'3001658': previous successful authorization performed from 152.32.128.46
0	06:21:08.549	'3001658': login on BroadmanVictory-Live through DC HK2 (ping: 2.76 ms)
0	06:21:08.924	'3001658': login datacenter on BroadmanVictory-Live through DC HK2 (ping: 2.76 ms)
0	06:21:09.064	'3001658': previous successful authorization performed from 152.32.128.46
1	06:26:29.441	'3001658': ping failed
0	06:26:35.910	'3001658': login on BroadmanVictory-Live through DC HK2 (ping: 2.76 ms)
0	06:26:45.269	'3001658': login datacenter on BroadmanVictory-Live through DC HK2 (ping: 2.76 ms)
0	06:26:45.394	'3001658': previous successful authorization performed from 152.32.128.46
1	06:59:47.096	'3001658': ping failed
1	06:59:47.111	'3001658': datacenter connecting failed [6]
0	06:59:47.439	'3001658': login on BroadmanVictory-Live through DC HK3 (ping: 2.61 ms)
0	06:59:47.799	'3001658': login datacenter on BroadmanVictory-Live through DC HK3 (ping: 2.61 ms)
0	06:59:47.939	'3001658': previous successful authorization performed from 152.32.128.46
0	06:59:48.127	'3001658': auto connecting to a better access point DC HK2 (ping is 2.80 ms)
0	06:59:48.471	'3001658': login on BroadmanVictory-Live through DC HK2 (ping: 2.80 ms)
0	06:59:48.830	'3001658': login datacenter on BroadmanVictory-Live through DC HK2 (ping: 2.80 ms)
0	06:59:48.971	'3001658': previous successful authorization performed from 152.32.128.46
1	07:04:42.769	'3001658': datacenter connecting failed [6]
0	07:04:43.176	'3001658': login on BroadmanVictory-Live through DC HK2 (ping: 2.80 ms)
0	07:04:43.535	'3001658': login datacenter on BroadmanVictory-Live through DC HK2 (ping: 2.80 ms)
0	07:04:43.676	'3001658': previous successful authorization performed from 152.32.128.46
0	07:37:34.653	'3001658': login on BroadmanVictory-Live through DC HK3 (ping: 2.39 ms)
0	07:37:35.044	'3001658': login datacenter on BroadmanVictory-Live through DC HK3 (ping: 2.39 ms)
0	07:37:35.169	'3001658': previous successful authorization performed from 152.32.128.46
1	08:14:51.378	'3001658': ping failed
0	08:14:51.393	'3001658': login datacenter on BroadmanVictory-Live
0	08:14:51.878	'3001658': login on BroadmanVictory-Live through DC HK2 (ping: 2.80 ms)
0	08:14:52.221	'3001658': login datacenter on BroadmanVictory-Live through DC HK2 (ping: 2.80 ms)
0	08:14:52.362	'3001658': previous successful authorization performed from 152.32.128.46
0	08:14:52.409	'3001658': auto connecting to a better access point DC HK3 (ping is 1.93 ms)
0	08:14:52.784	'3001658': login on BroadmanVictory-Live through DC HK3 (ping: 1.93 ms)
0	08:14:53.112	'3001658': login datacenter on BroadmanVictory-Live through DC HK3 (ping: 1.93 ms)
0	08:14:53.253	'3001658': previous successful authorization performed from 152.32.128.46
1	08:51:34.830	'3001658': ping failed
0	08:51:34.846	'3001658': login datacenter on BroadmanVictory-Live
0	08:51:35.221	'3001658': login on BroadmanVictory-Live through DC HK2 (ping: 2.78 ms)
0	08:51:35.565	'3001658': login datacenter on BroadmanVictory-Live through DC HK2 (ping: 2.78 ms)
0	08:51:35.705	'3001658': previous successful authorization performed from 152.32.128.46
1	09:08:56.378	'3001658': ping failed
0	09:08:56.378	'3001658': login datacenter on BroadmanVictory-Live
0	09:08:56.675	'3001658': login on BroadmanVictory-Live through DC HK4 (ping: 2.37 ms)
0	09:08:56.784	'3001658': login datacenter on BroadmanVictory-Live through DC HK4 (ping: 2.37 ms)
0	09:08:56.878	'3001658': previous successful authorization performed from 152.32.128.46
0	09:44:36.887	'3001658': login on BroadmanVictory-Live through DC HK4 (ping: 2.37 ms)
0	09:44:36.965	'3001658': login datacenter on BroadmanVictory-Live through DC HK4 (ping: 2.37 ms)
0	09:44:37.043	'3001658': previous successful authorization performed from 152.32.128.46
0	09:44:37.137	'3001658': auto connecting to a better access point DC HK2 (ping is 2.04 ms)
0	09:44:37.465	'3001658': login on BroadmanVictory-Live through DC HK2 (ping: 2.04 ms)
0	09:44:37.824	'3001658': login datacenter on BroadmanVictory-Live through DC HK2 (ping: 2.04 ms)
0	09:44:37.965	'3001658': previous successful authorization performed from 152.32.128.46