185.60.112.157 WinMTR
185.60.112.158 WinMTR
185.60.114.159 WinMTR
its always ae1-br01-eqam1.as57976.net (137.221.78.33) where the issue is present.
The issue has appeared within last week.
I’ve been experiencing same problem at similar hop for a couple weeks now, usually happens during evening or weekend’s afternoons which I presume are peaks.
B.net looking glass - https://pastebin.com/kvtDgNjt
WinMTR:
1 Like
Sorry to hear that you have been seeing disconnections and thank you for including the tests that you have done so far. Your particular tests do not show any issues with the quality of the connection you have. You will be disconnecting for another reason outside of quality.
I can understand why you are concerned by the higher recorded latency spike on the as57976 nodes so let me clear that up. This is simply part of some the security precautions we have on our nodes and as a result it will delay or dissuade some packets on these connection tests. If this was true latency, you would see this affecting every node following the spike. As you can see in all of your tests, this is not the case.
For yourself, you are seeing disconnections for different reasons than connection quality and I would highly recommend working through the following guide.
If the issue persists, please upload your system files to pastebin.com and reply with the links to the files using the preformatted text option to encapsulate the links.
Your test results actually do show issues with the quality of connection unlike Supremedruid. In your case, there is minor packet loss occurring from the following node:
| ae3-4.RT.EQX.FKT.DE.retn.net - 3 | 2940 | 2862 | 24 | 27 | 74 | 25 |
Unlike how I described our a57976 node, this is true and persistent packet loss as it affects every node after. None the less, it could still be worthwhile working through the connection guide and reaching out to your ISP for further assistance here
If you do still have issues, gather your files and create a thread of your own so we can help you out!