Consistent lag and trace route timeouts

Shreds711

Hello all,

I am running a Minecraft server on a personal home server not to far from where I live now (<10 miles), recently I've been noticing lag spikes upwards of 6000ms when playing. Others on the server, who live on the other side of the country do not experience these spikes and high pings. Below are the trace routes I have run, the first one is to the server. The second one is to www.google.com, run as a base line.

————————————————————————————————————————————
Tracing route to duckyserver.xyz [99.118.36.208]
over a maximum of 30 hops:

1 2 ms 1 ms 1 ms SAX2V1S.lan [192.168.1.1]
2 11 ms 25 ms 20 ms syn-173-175-108-001.res.spectrum.com [173.175.108.1]
3 49 ms 33 ms 43 ms lag-62.sgintxcj02h.netops.charter.com [24.28.130.58]
4 25 ms 19 ms 13 ms lag-18.hcr01sgintxcj.netops.charter.com [24.26.193.110]
5 23 ms 35 ms 13 ms lag-13.lvoktxad01r.netops.charter.com [24.26.193.108]
6 27 ms 35 ms 19 ms lag-21.mcr11snavtxuu.netops.charter.com [24.175.32.144]
7 16 ms 19 ms * lag-23.rcr01hstqtx02.netops.charter.com [24.175.32.156]
8 * * * Request timed out.
9 * * * Request timed out.
10 28 ms 23 ms 23 ms lag-0.pr3.dfw10.netops.charter.com [66.109.5.121]
11 * * * Request timed out.
12 * * * Request timed out.
13 * * * Request timed out.
14 * * * Request timed out.
15 * * * Request timed out.
16 * * * Request timed out.
17 63 ms 53 ms 65 ms 99-118-36-208.lightspeed.snantx.sbcglobal.net [99.118.36.208]

Trace complete.
———————————————————————————————————————————-
Tracing route to www.google.com [2607:f8b0:4023:100b::67]
over a maximum of 30 hops:

1 5 ms 17 ms 3 ms syn-2603-8081-2d00-342e-0000-0000-0000-0001.res6.spectrum.com [2603:8081:2d00:342e::1]
2 * 71 ms * 2603-90c5-0003-018c-0000-0000-0000-0001.inf6.spectrum.com [2603:90c5:3:18c::1]
3 24 ms 21 ms 23 ms lag-62.sgintxcj01h.netops.charter.com [2605:6000:0:4::e:43a4]
4 * * * Request timed out.
5 * * * Request timed out.
6 13 ms 13 ms 17 ms lag-21.mcr11snavtxuu.netops.charter.com [2605:6000:0:4::4:10]
7 20 ms 24 ms 18 ms lag-23.rcr01hstqtx02.netops.charter.com [2605:6000:0:4::34]
8 30 ms 29 ms 29 ms 2607:f8b0:8562:180::1
9 29 ms 54 ms 33 ms 2607:f8b0:8562:180::1
10 42 ms 35 ms 36 ms 2001:4860:0:1::29c
11 33 ms 34 ms 38 ms 2001:4860:0:1::9d00
12 43 ms 39 ms 39 ms 2001:4860::c:4004:a2fb
13 41 ms * * 2001:4860::c:4003:79cb
14 38 ms 45 ms 40 ms 2001:4860::cc:4003:79ce
15 * 34 ms 37 ms 2001:4860:0:1::9569
16 * * * Request timed out.
17 * * * Request timed out.
18 * * * Request timed out.
19 * * * Request timed out.
20 * * * Request timed out.
21 * * * Request timed out.
22 * * * Request timed out.
23 41 ms * 35 ms lcdfwe-in-f103.1e100.net [2607:f8b0:4023:100b::67]

Trace complete.
————————————————————————————————————————————

I come to you in this time of need. Any help would be appreciated.

Thanks for your time!

Edward_T

Hello @Shreds711;

Welcome to the Community Forums. I can understand the frustration of high ping times when gaming. I reviewed the trace routes you provided and they are not showing a problem. The results you are seeing are due to ICMP Filtering on network routers. This is a security feature to prevent DDOS attacks. You will see time outs or random spikes in the results when this happens. If it was truly a problem, you would see the same or higher result on each server after that. The results in your trace routes show they go lower after the high results.

I analyzed your modem and I am seeing the cable signals going to poor levels. This is likely affecting the quality of the internet connection. We can send a technician out to investigate the cable signals. When would you be available for a technician to come out?

RAIST515O

Could be taking a hit from IPv6 recursion as well. Resolving it can get tricky... setting static routes and all that. May sidestep it slightly with local host entry(s) on your clients, who knows.

Personally, I am still not running IPv6 locally. It is still hit and miss. Every time I have tested in the past, it provided no perceivable benefit--has even resulted in slightly more latency at times. Dual stack and recursives (even with google) can have weird side effects sometimes--especially with playstations.