Page 1 of 1

Fluffy's tracert help...

Posted: March 1st, 2015, 8:47 pm
by fluffy
So I have been seeing lots higher pings and constant in game skipping issues...Don't know what else to call it..Seems to been going on for at least the last month...Here is the tracert ..do not know what it means..

Thanks in advance....



tracert 8.12.64.130

Tracing route to 8.12.64.130 over a maximum of 30 hops

1 <1 ms <1 ms <1 ms Cisco77123 [10.105.43.123]
2 * * * Request timed out.
3 10 ms 8 ms 9 ms crr21ftwotx-tge-0-3-1-3.ftwo.tx.charter.com [96.
34.114.77]
4 30 ms 15 ms 15 ms crr02ftwotx-bue-4.ftwo.tx.charter.com [96.34.112
.70]
5 25 ms 14 ms 15 ms bbr02dllstx-bue-1.dlls.tx.charter.com [96.34.2.3
4]
6 21 ms 15 ms 15 ms bbr01dllstx-bue-3.dlls.tx.charter.com [96.34.0.1
8]
7 54 ms 56 ms 54 ms bbr01rvsdca-bue-6.rvsd.ca.charter.com [96.34.0.2
1]
8 53 ms 54 ms 53 ms prr01lsanca-bue-5.lsan.ca.charter.com [96.34.3.7
]
9 * 55 ms 55 ms ae2.ar1.lax1.us.as4436.gtt.net [69.31.127.49]
10 82 ms 52 ms 53 ms ae0-110g.cr1.lax1.us.as4436.gtt.net [69.31.127.1
37]
11 59 ms 58 ms 58 ms ae11-69.lax21.ip4.gtt.net [173.241.130.21]
12 68 ms 64 ms * xe-2-3-0.dal33.ip4.gtt.net [141.136.111.94]
13 52 ms 54 ms 62 ms ae10-69.cr1.dfw1.ip4.gtt.net [46.33.80.2]
14 52 ms 53 ms 53 ms as20473.xe-5-1-2.cr1.dfw1.us.as4436.gtt.net [69.
31.63.238]
15 52 ms 57 ms 57 ms 8.12.64.130

Trace complete.

Re: Fluffy's tracert help...

Posted: March 2nd, 2015, 4:21 am
by Trench
fluffy wrote: 1 <1 ms <1 ms <1 ms Cisco77123 [10.105.43.123]
2 * * * Request timed out.
3 10 ms 8 ms 9 ms crr21ftwotx-tge-0-3-1-3.ftwo.tx.charter.com [96.34.114.77]
4 30 ms 15 ms 15 ms crr02ftwotx-bue-4.ftwo.tx.charter.com [96.34.112.70]
5 25 ms 14 ms 15 ms bbr02dllstx-bue-1.dlls.tx.charter.com [96.34.2.34]
6 21 ms 15 ms 15 ms bbr01dllstx-bue-3.dlls.tx.charter.com [96.34.0.18]
7 54 ms 56 ms 54 ms bbr01rvsdca-bue-6.rvsd.ca.charter.com [96.34.0.21]
8 53 ms 54 ms 53 ms prr01lsanca-bue-5.lsan.ca.charter.com [96.34.3.7]
9 * 55 ms 55 ms ae2.ar1.lax1.us.as4436.gtt.net [69.31.127.49]
10 82 ms 52 ms 53 ms ae0-110g.cr1.lax1.us.as4436.gtt.net [69.31.127.137]
11 59 ms 58 ms 58 ms ae11-69.lax21.ip4.gtt.net [173.241.130.21]
12 68 ms 64 ms * xe-2-3-0.dal33.ip4.gtt.net [141.136.111.94]
13 52 ms 54 ms 62 ms ae10-69.cr1.dfw1.ip4.gtt.net [46.33.80.2]
14 52 ms 53 ms 53 ms as20473.xe-5-1-2.cr1.dfw1.us.as4436.gtt.net [69.31.63.238]
15 52 ms 57 ms 57 ms 8.12.64.130
Hmm. Starting at that hop that first jumps you by +30ms, both the DNS names used by Charter and the DNS names used by GTT make it seem like your traffic is being sent from Dallas to Dallas by way of California?

Regardless of whether those DNS names really are suggesting California or not, the bottom line is that your ping starts to go south while still within Charter's network, so talking to them about "why is this Dallas to Dallas traffic so slow" is your first and best option.

Don't expect that the front line support is going to give you any answer other than "it's not our fault, there is nothing we can do about that." That might ultimately be the real answer, but it's something only one of their actual network engineers could investigate and determine.

-Trench

Re: Fluffy's tracert help...

Posted: March 4th, 2015, 9:39 pm
by pantyshield
Hi Fluffy:

Sorry it took me a while to respond.

Don't see anything pointing to a cause from the traceroute. Each hop is tried 3x (numbers in ms).

Go to http://www.pingtest.net/ and run the test against a nearby server. See if you've got packet loss.

Might also try http://www.speedtest.net to see if your ISP is giving you what you're paying for.

Is the latency only in DC or BF42? Are you having issues within other apps or games?

Trying to narrow down if the issue is on your side or ISP. I have noticed some frequent lag in game but most of the time it's pretty good.

Help if I can.

Re: Fluffy's tracert help...

Posted: March 4th, 2015, 9:48 pm
by Trench
pantyshield wrote:Don't see anything pointing to a cause from the traceroute.
The premise here is that Fluffy's ping is usually only ~14ms total, since he's going from Dallas to Dallas to reach this server. Which is why hop 7 and on are unusual / the problem.

-Trench