The scan was stopped after the disconnect. The scan had 0% packet loss until the disconnect. All packets lost were back to back in a short cluster causing the disconnect.
No, I do not. The disconnection was on both my PC and my Laptop (wife) at the same time and multiple times throughout the afternoon, always both, never separate.
Neither of us use any networking tools, she does have RoG Laptop software which has something similar but I checked and it was not active.
My hunch is that if it is 2 machines at the same time on the same network, there is something going on with your network. Can you post a winMTR report?
This is likely related to the Telus network Canada issue that we are receiving contacts about for multiple games. This is affecting multiple Canadian ISP’s, including your own.
Also, for the duration of it, in between hop 5-6 there was a “No Response from Host” that had a 100 Packet loss that disappeared after I stopped. I also used 137.221.69.72 is my destination. What it looks like to me is something internally withing your servers is flipping me the bird.
This was a pretty short duration test, but it’s definitely possible there’s a peering issue going on there. Have you happened to try on that VPN you were talking about just yet? Any luck that way?
Edit: Also, to be clear, the hops you see at the end there aren’t actually our ‘servers’ - our server lives at the end after the no response from host. There are some ISPs we do peering with which get stamped with our name. They aren’t technically ‘owned’ by us, but if there’s a problem there we do get a bit more pull to fix the problem if we get enough reports of issues.
Started this after my 1st dc of the day. Which I did catch but wasn’t able to copy, had the results as the one I posted above this. Trying to go without the VPN but if It becomes more consistent, i most defiantly will.
That was a super long test and if I’m reading this right - you didn’t catch a disconnection while it was running did you? We need you to have it running the moment of a disconnection of the information isn’t super useful unfortunately. It also has way too much information - this looks like it was run for about an hour and a half. Try restarting it every 10-15 minutes so there isn’t as much data in the test. If we have a test that goes this long, it’s so much data that we can’t tell what’s really a problem and what’s just a hiccup.