High Latency

Technical Support
Tracing route to 63.240.104.93 over a maximum of 30 hops

1 997 ms 139 ms 21 ms 10.239.33.1
2 25 ms 49 ms 24 ms tge7-5.austtxa-er02.texas.rr.com [66.68.1.21]
3 16 ms 21 ms 18 ms tge8-5.austtxa-er01.texas.rr.com [24.175.41.246]
4 19 ms 15 ms 15 ms tge0-15-0-1.austtxa-cr02.texas.rr.com [24.175.41.2]
5 16 ms 23 ms 15 ms agg11.austtxrdcsc-cr01.texas.rr.com [24.175.41.206]
6 17 ms 16 ms 14 ms agg10.austtxrdcsc-cr02.texas.rr.com [24.175.41.209]
7 20 ms 23 ms 23 ms agg22.hstntxl3-cr01.texas.rr.com [24.175.41.48]
8 31 ms 23 ms 23 ms ae-2-0.cr0.hou30.tbone.rr.com [66.109.6.108]
9 25 ms 25 ms 57 ms 107.14.17.141
10 1414 ms 81 ms 993 ms ip65-47-204-137.z204-47-65.customer.algx.net [65.47.204.137]
11 34 ms 303 ms 458 ms 192.205.36.101
12 65 ms 68 ms 66 ms cr1.dlstx.ip.att.net [12.123.18.74]
13 65 ms 68 ms 116 ms cr2.nsvtn.ip.att.net [12.122.1.242]
14 649 ms 187 ms 585 ms cr1.cl2oh.ip.att.net [12.122.28.74]
15 175 ms 287 ms 235 ms cr2.cl2oh.ip.att.net [12.122.2.126]
16 68 ms 67 ms 67 ms cr2.phlpa.ip.att.net [12.122.2.210]
17 828 ms 645 ms 1353 ms gar1.pitpa.ip.att.net [12.122.107.85]
18 305 ms 543 ms 218 ms 12.122.251.2
19 1131 ms 213 ms 193 ms mdf001c7613r0003-gig-10-1.nyc3.attens.net [63.240.65.10]
20 * * * Request timed out.
21 * * * Request timed out.
22 * * * Request timed out.
23 * * * Request timed out.
24 * * * Request timed out.
25 * * * Request timed out.
26 * * * Request timed out.
27 * * * Request timed out.
28 * * * Request timed out.
29 * * * Request timed out.
30 * * * Request timed out.

Trace complete.
Seriously?

Tracing route to 63.240.104.93 over a maximum of 30 hops

1 214 ms 20 ms 18 ms 10.239.33.1
2 17 ms 28 ms 17 ms tge7-5.austtxa-er02.texas.rr.com [66.68.1.21]
3 18 ms 18 ms 17 ms tge8-5.austtxa-er01.texas.rr.com [24.175.41.246]
4 17 ms 23 ms 25 ms tge0-15-0-1.austtxa-cr02.texas.rr.com [24.175.41.2]
5 23 ms 24 ms 24 ms agg11.austtxrdcsc-cr01.texas.rr.com [24.175.41.206]
6 24 ms 24 ms 23 ms agg10.austtxrdcsc-cr02.texas.rr.com [24.175.41.209]
7 451 ms 38 ms 37 ms agg22.hstntxl3-cr01.texas.rr.com [24.175.41.48]
8 626 ms 74 ms 1235 ms ae-2-0.cr0.hou30.tbone.rr.com [66.109.6.108]
9 286 ms 464 ms 31 ms 107.14.17.141
10 45 ms 44 ms 47 ms ip65-47-204-137.z204-47-65.customer.algx.net [65.47.204.137]
11 25 ms 27 ms 23 ms 192.205.36.101
12 176 ms 64 ms 67 ms cr1.dlstx.ip.att.net [12.123.18.74]
13 124 ms 132 ms 76 ms cr2.nsvtn.ip.att.net [12.122.1.242]
14 1095 ms 71 ms 63 ms cr1.cl2oh.ip.att.net [12.122.28.74]
15 102 ms 65 ms 65 ms cr2.cl2oh.ip.att.net [12.122.2.126]
16 178 ms 67 ms 66 ms cr2.phlpa.ip.att.net [12.122.2.210]
17 71 ms 66 ms 66 ms gar1.pitpa.ip.att.net [12.122.107.85]
18 250 ms 165 ms 203 ms 12-122-254-242.attens.net [12.122.254.242]
19 75 ms 71 ms 72 ms mdf001c7613r0003-gig-10-1.nyc3.attens.net [63.240.65.10]
20 * * * Request timed out.
21 * * * Request timed out.
22 * * * Request timed out.
23 * * * Request timed out.
24 * * * Request timed out.
25 * * * Request timed out.
26 * * * Request timed out.
27 * * * Request timed out.
28 * * * Request timed out.
29 * * * Request timed out.
30 * * * Request timed out.

Trace complete.
my latency is in the 3000 both wtf
I see mods asking for this information on other posts, so when they finally get to mine I'll have it ready for them.

Wired Connection
Firewall disabled
AVG antivirus
Network card: Realtek PCIe GBE
Router/modem combo: Ubee Docsis 3
Network card: Realtek PCIe GBE
Router/modem combo: Ubee Docsis 3

1 214 ms 20 ms 18 ms 10.239.33.1

1 997 ms 139 ms 21 ms 10.239.33.1

Hey Trottel,

There's something going on between your network card and Ubee modem. Have you unplugged the Ubee modem for a minutes to reset it?
I was at over 3000ms about a week ago. So I did a complete DELETE and REINSTALL of WoW overnight.

Then I was happy because I was at 62/62 ms for a few days.

Logged in today and I am over 1000ms again. Didn't change a thing!

Not Blizzards problem tho , working as intended?

Sending tracert's , pathpings, contacting my ISP, contacting other providers on route to Blizzards servers to no avail. Trying to play WoW is feeling like a part time job, my question is "Is it worth it?"

I have about 25+ games installed on my PC , WoW is the ONLY game that has ever given me problems (scratch that Diablo 3 did also) wonder why.

I honestly am close to saying FORGET IT and giving up. At least I will have the memories.
I haven't yet. But I just ran a tracert to google. And you can see for yourself the difference. I will reboot everything I have instead of hitting refresh on this thread to see if it makes any difference.

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

1 9ms 7 ms 7 ms 10.239.33.1
2 12 ms 11 ms 10 ms tge7-5.austtxa-er02.texas.rr.com [66.68.1.21]
3 16 ms 15 ms 23 ms tge0-15-0-0.austtxa-cr01.texas.rr.com [66.68.2.23]
4 21 ms 15 ms 15 ms agg10.austtxa-cr02.texas.rr.com [24.175.41.205]
5 21 ms 15 ms 15 ms agg11.austtxrdcsc-cr01.texas.rr.com [24.175.41.206]
6 1089 ms 65 ms 29 ms agg10.austtxrdcsc-cr02.texas.rr.com [24.175.41.209]
7 24 ms 24 ms 23 ms agg22.hstntxl3-cr01.texas.rr.com [24.175.41.48]
8 23 ms 31 ms 23 ms ae-2-0.cr0.hou30.tbone.rr.com [66.109.6.108]
9 27 ms 39 ms 23 ms ae-0-0.cr0.dfw10.tbone.rr.com [66.109.6.39]
10 19 ms 190 ms 30 ms 107.14.17.234
11 38 ms 37 ms 40 ms 74.125.48.65
12 20 ms 19 ms 19 ms 72.14.233.67
13 22 ms 37 ms 21 ms 209.85.240.79
14 545 ms 53 ms 52 ms dfw06s27-in-f18.1e100.net [173.194.46.18]

Trace complete.
6 1089 ms 65 ms 29 ms agg10.austtxrdcsc-cr02.texas.rr.com [24.175.41.209]

Hop 6 is showing issues in the last trace, but it looks good in your previous traces.

Can you run a pathping? That will show more detail.
Well, rebooting the modem seems to have done something. My latency is better ingame. Now I'm curious as to why my tracerts between Blizzard servers and google were so far off from each other.
Well, rebooting the modem seems to have done something. My latency is better ingame. Now I'm curious as to why my tracerts between Blizzard servers and google were so far off from each other.

Most likely you just got lucky in the Google trace that their weren't any issues that showed up when you pinged your modem, but if you take a look at hop 6 in the Google trace, you'll notice that the issue was still there. Because other traces showed high latency for the hop to your modem, it's fair to assume that the high latency at hop 6 in the Google trace was also caused by your modem. I don't know how you're connected to it, but looking at the ping times, I'd say that you are connected wirelessly. If that's the case, you're most likely seeing interference on the wireless channel your modem is using, so one thing to try would be going into the configuration of the modem (usually it's a web-based interface) and changing the channel to channel 1 or 11 (I'll assume that you're already on channel 6, since that's the most common).

Edit: I see that you said you were on a wired connection, so ignore the wireless parts above that I mentioned. I'm now slightly confused... If these issues persist, you might need to have your ISP do a line test between them and you.
________________________________________________
Tech Support MVP
"...and, we're back!" -Google

Join the Conversation

Return to Forum