I’m also having a LOT of these errors disconnecting me at random since Sunday afternoon.
In my case, one consistency with Op’s is high packet loss on the as57976 hops. Different in my case is that I do not have the significant packetloss within our country, so our ISP is essentially not to blame here.
|------------------------------------------------------------------------------------------|
| WinMTR statistics |
Host - % |
Sent |
Recv |
Best |
Avrg |
Wrst |
Last |
/ - 0 |
2178 |
2178 |
0 |
0 |
4 |
0 |
/ - 1 |
2167 |
2164 |
6 |
35 |
578 |
54 |
/ - 1 |
2118 |
2102 |
8 |
38 |
437 |
27 |
/ - 1 |
2105 |
2085 |
10 |
39 |
578 |
30 |
/ - 2 |
2070 |
2041 |
8 |
40 |
358 |
39 |
/ - 1 |
2107 |
2088 |
9 |
40 |
437 |
24 |
/ - 2 |
2045 |
2010 |
17 |
55 |
482 |
48 |
/ - 3 |
1988 |
1938 |
17 |
56 |
453 |
56 |
xe-1-0-0.cr-01-cpt.za.as328112 net - 4 |
1948 |
1888 |
17 |
56 |
327 |
37 |
105.22.64.209 - 3 |
1996 |
1948 |
16 |
58 |
342 |
46 |
ce-0-3-0-0.cr-01-cpt.za.seacomnet com - 3 |
2002 |
1955 |
33 |
207 |
563 |
233 |
xe-0-7-0-1.cr-01-lhr.uk.seacomnet com - 4 |
1933 |
1869 |
174 |
214 |
471 |
203 |
ae-4-0.pp-01-lhr.uk.seacomnet com - 3 |
1957 |
1899 |
167 |
208 |
621 |
192 |
195.66.226.234 - 3 |
1973 |
1919 |
173 |
217 |
563 |
219 |
ae1-br01-eqld5.as57976 net - 16 |
1188 |
1005 |
0 |
1074 |
4794 |
3101 |
ae1-br01-eqld5.as57976 net - 99 |
443 |
6 |
0 |
795 |
1524 |
357 |
137.221.78.87 - 4 |
1947 |
1886 |
181 |
222 |
563 |
212 |
137.221.66.45 - 4 |
1924 |
1857 |
176 |
214 |
416 |
205 |
185.60.114.167 - 4 |
1954 |
1895 |
176 |
217 |
571 |
234 |
37.244.54.10 - 3 |
1957 |
1899 |
175 |
211 |
563 |
205 |
________________________________________________ |
______ |
______ |
______ |
______ |
______ |
______ |
WinMTR v0.92 GPL V2 by Appnor MSP - Fully Managed Hosting & Cloud Provider
Those nodes are configured de-prioritize ICMP packets (ie the message type used by ping, WinMTR, etc.). You can simply ignore them because the pings don’t reflect their healthiness.
I doubt that, you got data packet loss and high latency spikes starting from hop 2 and all the way down to the server:
That means something wrong between hop 1 and 2.
Also, a jump (4% loss) at xe-1-0-0.cr-01-cpt.za.as328112.net
. It could be another defect.
As you hide the IP/hostnames, you need to figure out what those hops are yourself. But, I guess from the position, they are either your home network or your ISP.
1 Like
ISP. As for the packetloss, I watched it at the times I was suffering back-to-back disconnects, and there weren’t increases in packetloss on the local hops. It’s worth noting WinMTR reports 1% packetloss even if there is actually less than 0.01% (note the first hop says 1% even though 3/2167 packets were lost, or 0.14%
I also have a constant ping to whichever server I happen to be playing on going via SimplePing, in the centre of my screen, polling every 0.75s. Whenever I suffer the disconnects, I don’t get pings which had timed out; and realistically, I’ve had situations where my game would lag up so hard I’d have no activity for 10s+ /without/ getting disconnected, yet here I am in the middle of combat and everything (including looting) is working 100% then BAM! the error comes up (and the game continues in the background) right until the moment I acknowledge the error, from where it seems to actually insta-DC me.
As I play hardcore this has fortunately meant I haven’t yet lost any characters to the disconnects, as I just acknowledge the error ASAP to get out of harm’s way, but still… I’m not buying the idea that it’s because of packetloss, as in the 7+ years I’ve now been playing this game this is the first time this issue is coming up for me in this fashion, and during that time I’ve had LOADS of ISP issues much worse than what’s being suggested here.
Edit: as for the reference to the latency spikes, while playing I don’t suffer from latency issues preceding the disconnects. Gameplay is perfectly normal right up until the error 1016 message pops up.
I’ve also noticed that every few times I log back in, the game is greeting me as though I only just got Reaper of Souls for whatever reason…
Edit: Okay so, if you skip to 03:40 you’ll see what I meant about the game carrying on after the error 1016 message comes up. Given my current build I can casually run around and complete rifts with ease like this…