Got moved out from The Onslaught League after a disconnection
" That's fine, all the IP's will be different, we're just looking for the last one mentioned prior to your death. There is a point in checking the results, this way we can see if its your computer/modem that is causing the issue, your provider or our servers. Depending on which part of the chain is experiencing the problem, we can offer tips to improve the connection. Though I understand if you don't want to, as you may not have frequent disconnections. |
|
|
here it is:
|------------------------------------------------------------------------------------------| | WinMTR statistics | | Host - % | Sent | Recv | Best | Avrg | Wrst | Last | |------------------------------------------------|------|------|------|------|------|------| | Dlink-Router.Dlink - 0 | 3 | 3 | 0 | 0 | 1 | 0 | | 172-16-250-134.avk-wellcom.com - 0 | 3 | 3 | 1 | 2 | 4 | 1 | | NAT-35.avk-wellcom.ru - 0 | 3 | 3 | 2 | 2 | 4 | 2 | | 93.157.175.1 - 0 | 3 | 3 | 1 | 2 | 4 | 1 | | No response from host - 100 | 1 | 0 | 0 | 0 | 0 | 0 | | bbr01.xn01.fra01.networklayer.com - 0 | 3 | 3 | 46 | 46 | 47 | 47 | | ae7.bbr02.xn01.fra01.networklayer.com - 0 | 3 | 3 | 49 | 49 | 51 | 49 | | ae1.bbr01.eq01.ams02.networklayer.com - 0 | 3 | 3 | 46 | 47 | 48 | 46 | | ae5.dar01.sr01.ams01.networklayer.com - 0 | 3 | 3 | 48 | 70 | 82 | 81 | | po1.fcr01.sr01.ams01.networklayer.com - 0 | 3 | 3 | 47 | 47 | 48 | 48 | |37.58.67.236-static.reverse.softlayer.com - 0 | 3 | 3 | 47 | 47 | 48 | 47 | |________________________________________________|______|______|______|______|______|______| WinMTR v0.92 GPL V2 by Appnor MSP - Fully Managed Hosting & Cloud Provider |
|
" Thank you for posting that, but can you do another one and let it run for a minute or so? The longer it runs, the more packets it sends, the more information we can gather :D |
|
|
|------------------------------------------------------------------------------------------|
| WinMTR statistics | | Host - % | Sent | Recv | Best | Avrg | Wrst | Last | |------------------------------------------------|------|------|------|------|------|------| | Dlink-Router.Dlink - 0 | 76 | 76 | 0 | 0 | 2 | 0 | | 172-16-250-134.avk-wellcom.com - 0 | 76 | 76 | 0 | 0 | 4 | 1 | | NAT-35.avk-wellcom.ru - 0 | 76 | 76 | 0 | 1 | 4 | 0 | | 93.157.175.1 - 0 | 76 | 76 | 0 | 1 | 4 | 1 | | atlant.naukanet.ru - 0 | 76 | 76 | 1 | 3 | 47 | 2 | | bbr01.xn01.fra01.networklayer.com - 0 | 76 | 76 | 45 | 47 | 101 | 47 | | ae7.bbr02.xn01.fra01.networklayer.com - 0 | 76 | 76 | 49 | 57 | 78 | 49 | | ae1.bbr01.eq01.ams02.networklayer.com - 0 | 76 | 76 | 46 | 48 | 97 | 47 | | ae5.dar01.sr01.ams01.networklayer.com - 0 | 76 | 76 | 46 | 48 | 87 | 46 | | po1.fcr01.sr01.ams01.networklayer.com - 2 | 73 | 72 | 46 | 55 | 144 | 47 | |37.58.67.236-static.reverse.softlayer.com - 0 | 76 | 76 | 46 | 47 | 49 | 47 | |________________________________________________|______|______|______|______|______|______| WinMTR v0.92 GPL V2 by Appnor MSP - Fully Managed Hosting & Cloud Provider |
|
" Cheers for that. The only real issue I can see is: atlant.naukanet.ru - 0 | 76 | 76 | 1 | 3 | 47 | 2 | This is showing latency spikes from 1-3ms to 40-47ms. Although this is minor, it means there could be issues with it intermittently which cause higher latency spikes, which result in a disconnect. At this stage, I'd recommend playing the game again and the next time you run into a disconnect problem, grab the server IP from your client.txt file and run a trace route. If we can capture one of these points/hops displaying packet loss/latency spikes, we'll be closer to identifying the root cause. |
|
