Since the latest update, I can't seem to stay connected after about 3 or 4 PM EST. Any help would be appreciated. Thanks.
Tracert:
Tracing route to patchserver.crypticstudios.com [208.95.185.41]
over a maximum of 30 hops:
1 25 ms 16 ms 26 ms cpe-075-184-016-001.nc.res.rr.com [75.184.16.1]
2 15 ms 12 ms 12 ms gig0-0-6.fyvlncr-rtr1.nc.rr.com [24.88.225.201]
3 17 ms 19 ms 18 ms xe-7-1-3.rlghncpop-rtr1.southeast.rr.com [24.93.
64.46]
4 21 ms 23 ms 22 ms ae-3-0.cr0.dca10.tbone.rr.com [66.109.6.80]
5 22 ms 21 ms 21 ms ae-0-0.pr0.dca20.tbone.rr.com [66.109.6.183]
6 27 ms 28 ms 29 ms te0-11-0-23.ccr41.iad02.atlas.cogentco.com [154.
54.10.193]
7 27 ms 28 ms 28 ms be2176.ccr21.dca01.atlas.cogentco.com [154.54.41
.54]
8 33 ms 56 ms 34 ms be2148.ccr21.jfk02.atlas.cogentco.com [154.54.31
.118]
9 41 ms 40 ms 40 ms be2096.ccr22.bos01.atlas.cogentco.com [154.54.30
.42]
10 39 ms 41 ms 38 ms te4-4.ccr01.bos06.atlas.cogentco.com [66.28.4.42
]
11 48 ms 34 ms 35 ms 38.111.40.114
12 34 ms 35 ms 33 ms patchserver2.crypticstudios.com [208.95.185.41]
Since the latest update, I can't seem to stay connected after about 3 or 4 PM EST. Any help would be appreciated. Thanks.
...
Now both your 'Trace Route' and 'Net Test' diagnostics are showing excellent results... So it may not be a network path related issue...
You could try using the 'pathping' command, which has the same syntax as the 'tracert' command to see if you're suffering from silently dropped packets, but if this was the case, this would usually show up in the 'Net Test' results...
Well I went and replaced my modem because I was experiencing 77% packet loss plus it was about 2 years old. Played fine for a couple of hours last night but this morning I'm right back to lagging. Logged in and DC'd right away.
Comments
Now both your 'Trace Route' and 'Net Test' diagnostics are showing excellent results... So it may not be a network path related issue...
You could try using the 'pathping' command, which has the same syntax as the 'tracert' command to see if you're suffering from silently dropped packets, but if this was the case, this would usually show up in the 'Net Test' results...