Was dumped right into the ocean of tears (was taking boat) from this bug. At best, this issue is really frustrating to deal with.
Could the devs please acknowledge that they are aware of this? I posted the link to this thread when bringing it up to Nilbog in Sirken's stream yesterday but have no idea if he took it seriously. He did respond that its a known issue with satellite internet, but I promptly let him know that my connection has always been very a stable wired connection.
Code:
|------------------------------------------------------------------------------------------|
| WinMTR statistics |
| Host - % | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
| lolwat - 0 | 176 | 176 | 0 | 0 | 1 | 0 |
| cpe-65-31-128-1.wi.res.rr.com - 0 | 176 | 176 | 10 | 249 | 616 | 28 |
| tge7-1.brfdwifb02h.midwest.rr.com - 0 | 176 | 176 | 8 | 222 | 614 | 9 |
| tge1-6-0-9.gnfdwibb01r.midwest.rr.com - 0 | 176 | 176 | 12 | 219 | 582 | 25 |
|bu-ether16.chcgildt87w-bcr00.tbone.rr.com - 0 | 176 | 176 | 14 | 220 | 644 | 22 |
| 0.ae1.pr1.chi10.tbone.rr.com - 2 | 176 | 174 | 14 | 222 | 644 | 18 |
| 216.1.94.145 - 0 | 176 | 176 | 14 | 216 | 581 | 65 |
| 207.88.15.90.ptr.us.xo.net - 1 | 176 | 175 | 14 | 213 | 618 | 16 |
| 206.111.2.65.ptr.us.xo.net - 0 | 176 | 176 | 14 | 218 | 553 | 18 |
| ae-7.r20.chcgil09.us.bb.gin.ntt.net - 0 | 176 | 176 | 14 | 208 | 636 | 18 |
| ae-5.r23.nycmny01.us.bb.gin.ntt.net - 15 | 176 | 151 | 36 | 224 | 635 | 45 |
| ae-1.r06.nycmny01.us.bb.gin.ntt.net - 0 | 176 | 176 | 36 | 237 | 629 | 46 |
| ae-1.choopa.nycmny01.us.bb.gin.ntt.net - 4 | 176 | 170 | 38 | 237 | 643 | 41 |
| 108.61.244.50 - 4 | 176 | 169 | 38 | 234 | 630 | 45 |
| No response from host - 100 | 176 | 0 | 5000 | 0 | 0 | 0 |
|________________________________________________|______|______|______|______|______|______|
WinMTR v0.91 GPL V2 by Appnor MSP - Fully Managed Hosting & Cloud Provider
Getting some packet loss with the TWC and NTT tier1 networks. If the client doesn't try to connect more than once to the zone server, this might explain the issue.