A new episode began this morning. Latency was still reasonably low but the standard deviation of latency increased significantly.I tested whether the Arcadyan gateway had changed towers since the baseline low-latency measurement on Jan 8, and I found it had.I tested whether a re-boot would have it seek a different tower (gateway had been up over 90 days) and it did, and latency significantly improved immediately following the reboot.Below is a comparison, l-r, of the baseline, the high-latency-stdev, and post-reboot. Post reboot, the gateway sought a third tower/antenna different from the baseline low latency and different from the increased latency tower/antenna, and on the third tower, latency returned to a low level and low stdev:Latency graph showing effect of reboot that switched towers 1-hour scale:Latency continues now to remain very low:So apparently I can rectify the issue when it occurs with a gateway reboot, but this is far from optimal.Question: why does the gateway switch
Thanks; found both on the app. Next will be to figure out how to map CGI to actual towers and confirm I’m connected to what I think I’m connected to.
Thanks; that’s an interesting idea. I’ll record current signal information and compare when the upset happens again. I’m not sure I know how to tell what tower the gateway is connecting with. If this turns out to be a factor, that would be great, except I still have little idea how to reach someone competent at T-Mobile with the information.The service’s latency is outstanding when it’s not having an episode and it’s better than CenturyLink DSL, but that’s a really, really low bar to clear.
Already have an account? Login
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.
Sorry, we're still checking this file's contents to make sure it's safe to download. Please try again in a few minutes.
Sorry, our virus scanner detected that this file isn't safe to download.