Gaming disconnects, sporadic internet drops, tracert showing weirdness.

Four days ago I started having really bad lag in an MMO, FFXIV. Anywhere from 3-30 seconds or a total disconnect. It's unplayable, pretty much. No general service issues happening with either the MMO or the PlayStation network in the same period.

I tried doing an MRT to the game server, but it fails completely at the cr02.dallas.tx.ibone.comcast.net server from this tracert:

Tracing route to 199.91.189.74 over a maximum of 30 hops

1 1 ms <1 ms <1 ms 66-208-198-226-memphis.hfc.comcastbusiness.net [66.208.198.226]
2 9 ms 9 ms 16 ms 96.120.15.21
3 9 ms 9 ms 10 ms te5-4-ur01.bartlett.tn.malt.comcast.net [68.86.244.241]
4 12 ms 11 ms 12 ms te-9-4-ur01.millingtonrd.tn.malt.comcast.net [68.86.241.114]
5 21 ms 21 ms 22 ms be-22258-cr02.dallas.tx.ibone.comcast.net [68.86.93.93]
6 1708 ms 2068 ms * 50.242.148.30
7 * * 56 ms ae-2-12.bear1.montreal2.level3.net [4.69.203.129]
8 59 ms 56 ms 53 ms ormuco-comm.car2.montreal2.level3.net [4.59.178.74]
9 55 ms 56 ms 54 ms 10.2.0.1
10 55 ms 65 ms 56 ms 192.34.76.2
11 56 ms 59 ms 58 ms 199.91.189.234
12 54 ms 57 ms 54 ms 199.91.189.74

Trace complete.

Google, for comparison:

Tracing route to google.com [216.58.218.206]
over a maximum of 30 hops:

1 1 ms 1 ms 1 ms 66-208-198-226-memphis.hfc.comcastbusiness.net [66.208.198.226]
2 22 ms 8 ms 11 ms 96.120.15.21
3 13 ms 10 ms 8 ms te4-1-ur01.bartlett.tn.malt.comcast.net [68.86.112.245]
4 11 ms 11 ms 12 ms te-9-1-ur01.millingtonrd.tn.malt.comcast.net [68.86.240.73]
5 22 ms 20 ms 23 ms be-22258-cr02.dallas.tx.ibone.comcast.net [68.86.93.93]
6 20 ms 21 ms 20 ms be-12441-pe01.1950stemmons.tx.ibone.comcast.net [68.86.89.206]
7 21 ms 20 ms 29 ms as20115-1-c.600wseventh.ca.ibone.comcast.net [66.208.228.94]
8 22 ms 20 ms 23 ms 108.170.240.65
9 21 ms 20 ms 19 ms 108.170.233.201
10 20 ms 22 ms 15 ms dfw06s47-in-f206.1e100.net [216.58.218.206]

Trace complete.

I've tried resetting the devices pretty much a couple times a day since this started, changed the cables out to see if it was them failing, flushed DNS in desperation. What else can I try?

Responses

xz4gb8

Problem solver

•

117 Messages

8 years ago

dmhare wrote, "I tried doing an MRT to the game server, but it fails completely at the cr02.dallas.tx.ibone.comcast.net server from this tracert:"

The MRT did not fail, the trace reached 199.91.189.74 successfully.

Having said that, hop 6 through 50.242.148.30 indicate a router which is extremely slow to respond to echo request. Looking at the step increase in time from the level3 router on, either 50.242.138.30 is being hammered or one or more of the links connecting that device are slow or congested.

What you can do:

Find another place to originate tests that traverses a different path to level3 in montreal and compare the results. Better response times would be hard data to support an attempt to get attention from Comcast.

Example from the detroit area:

my_system:~ my_login$ traceroute 199.91.189.74
traceroute to 199.91.189.74 (199.91.189.74), 64 hops max, 52 byte packets
1 192.168.1.1 (192.168.1.1) 34.315 ms 1.461 ms 1.280 ms
2 96.120.40.57 (96.120.40.57) 10.396 ms 9.540 ms 10.417 ms
3 68.86.121.237 (68.86.121.237) 10.747 ms 10.467 ms 10.514 ms
4 162.151.127.186 (162.151.127.186) 10.577 ms 9.768 ms 9.434 ms
5 68.87.190.29 (68.87.190.29) 11.954 ms 12.513 ms 11.815 ms
6 ae2.bar1.detroit1.level3.net (4.68.71.33) 12.898 ms 17.560 ms 14.184 ms
7 * ae-2-12.bear1.montreal2.level3.net (4.69.203.129) 36.151 ms 35.755 ms
8 ormuco-comm.car2.montreal2.level3.net (4.59.178.74) 35.418 ms 35.772 ms 36.740 ms
9 10.2.0.1 (10.2.0.1) 42.171 ms 35.836 ms 36.154 ms
10 * * *
11 * * *
12 * * *
13 * * *
14 * * *
15 * * *
16 * * *
17 *^C
my_system:~ my_login$ date
Mon Jan 16 16:32:34 EST 2017

Comments on example:

Now that was a failure if the path to 199.91.189.74 is supposed to go through level 3 in montreal. If that is a proper path, it looks as if level 3 is having a problem right now. I don't have any more data.

0

CCMichael

Gold Problem solver

•

575 Messages

8 years ago

Hello dmhare,

I apologize for the delayed response to your post. I was reviewing your connection to your location and saw a few things that might explain the connection issue. My first thought is to force your modem into an IPv4 only mode to force a different routing path. Beyond that we can send a tech out to see if there is an issue with the line. The process to put your modem in IPv4 only mode can take up to 40 minutes to complete. Would you please message back with a time that works best for you? (AM/PM)

Thank You

0