New latency problem in WoW

Question

Hello!
I am a longtime customer of Cox, and player of World of Warcraft. I play here in Virginia, but I connect to an Oceanic Server based in Sydney, Australia, due to them being active during my waking hours (which are the middle of the night U.S. time). Roughly a week ago, I began to experience a spike in latency in my game, increasing from the normal 250ms to 360-380ms and staying steady at that level. I contacted the game's Technical Support team and was told to run a traceroute in order to determine the source of the problem. Once I did so, they said that the signal seemed to be experiencing an unusual amount of packet loss at a certain point in the route, and that I should contact my ISP to determine what to do next.
Here is the traceroute (Run throughthe WinMTR program they provided).
|------------------------------------------------------------------------------------------||&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; WinMTR statistics&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; ||&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Host&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; -&nbsp;&nbsp; %&nbsp; | Sent | Recv | Best | Avrg | Wrst | Last ||------------------------------------------------|------|------|------|------|------|------||&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; router.belkin -&nbsp;&nbsp;&nbsp; 0 |&nbsp; 722 |&nbsp; 722 |&nbsp;&nbsp;&nbsp; 0 |&nbsp;&nbsp;&nbsp; 0 |&nbsp;&nbsp;&nbsp; 4 |&nbsp;&nbsp;&nbsp; 0 ||&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 10.65.20.1 -&nbsp;&nbsp;&nbsp; 0 |&nbsp; 722 |&nbsp; 722 |&nbsp;&nbsp;&nbsp; 6 |&nbsp;&nbsp;&nbsp; 9 |&nbsp;&nbsp; 26 |&nbsp;&nbsp;&nbsp; 8 ||&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 98.172.172.194 -&nbsp;&nbsp;&nbsp; 0 |&nbsp; 722 |&nbsp; 722 |&nbsp;&nbsp;&nbsp; 6 |&nbsp;&nbsp; 10 |&nbsp;&nbsp; 45 |&nbsp;&nbsp;&nbsp; 7 ||&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; ashbbprj01-ae3.0.rd.as.cox.net -&nbsp;&nbsp;&nbsp; 0 |&nbsp; 722 |&nbsp; 722 |&nbsp;&nbsp; 13 |&nbsp;&nbsp; 17 |&nbsp;&nbsp; 45 |&nbsp;&nbsp; 15 ||&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; ip70-167-150-2.at.at.cox.net -&nbsp;&nbsp;&nbsp; 0 |&nbsp; 722 |&nbsp; 722 |&nbsp;&nbsp; 14 |&nbsp;&nbsp; 24 |&nbsp;&nbsp; 97 |&nbsp;&nbsp; 27 ||&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 100ge15-1.core1.lax1.he.net -&nbsp;&nbsp;&nbsp; 0 |&nbsp; 722 |&nbsp; 722 |&nbsp;&nbsp; 83 |&nbsp;&nbsp; 88 |&nbsp; 111 |&nbsp;&nbsp; 90 ||&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 10ge1-3.core1.lax2.he.net -&nbsp;&nbsp;&nbsp; 3 |&nbsp; 653 |&nbsp; 636 |&nbsp;&nbsp; 81 |&nbsp; 159 |&nbsp; 211 |&nbsp; 171 ||vocus.10gigabitethernet5-8.core1.lax2.he.net -&nbsp;&nbsp;&nbsp; 3 |&nbsp; 666 |&nbsp; 652 |&nbsp;&nbsp; 82 |&nbsp; 161 |&nbsp; 266 |&nbsp; 169 ||&nbsp;&nbsp;&nbsp;&nbsp; bundle-101.cor02.lax01.ca.VOCUS.net -&nbsp;&nbsp;&nbsp; 3 |&nbsp; 654 |&nbsp; 637 |&nbsp; 247 |&nbsp; 322 |&nbsp; 389 |&nbsp; 333 ||&nbsp;&nbsp;&nbsp;&nbsp; bundle-100.cor01.lax01.ca.VOCUS.net -&nbsp;&nbsp;&nbsp; 6 |&nbsp; 598 |&nbsp; 567 |&nbsp; 252 |&nbsp; 326 |&nbsp; 378 |&nbsp; 342 ||&nbsp;&nbsp;&nbsp;&nbsp; bundle-102.cor01.sjc01.ca.VOCUS.net -&nbsp;&nbsp;&nbsp; 3 |&nbsp; 662 |&nbsp; 647 |&nbsp; 250 |&nbsp; 324 |&nbsp; 372 |&nbsp; 334 ||&nbsp;&nbsp;&nbsp;&nbsp; bundle-100.cor02.sjc01.ca.VOCUS.net -&nbsp;&nbsp;&nbsp; 4 |&nbsp; 638 |&nbsp; 617 |&nbsp; 250 |&nbsp; 325 |&nbsp; 390 |&nbsp; 335 ||ten-0-2-0-2.cor01.syd04.nsw.VOCUS.net.au -&nbsp;&nbsp;&nbsp; 3 |&nbsp; 654 |&nbsp; 637 |&nbsp; 249 |&nbsp; 324 |&nbsp; 387 |&nbsp; 335 ||&nbsp; ten-2-0-0.bdr03.syd04.nsw.VOCUS.net.au -&nbsp;&nbsp;&nbsp; 3 |&nbsp; 646 |&nbsp; 627 |&nbsp; 253 |&nbsp; 327 |&nbsp; 378 |&nbsp; 343 ||as17819.cust.bdr03.syd04.nsw.VOCUS.net.au -&nbsp;&nbsp;&nbsp; 3 |&nbsp; 666 |&nbsp; 652 |&nbsp; 262 |&nbsp; 340 |&nbsp; 467 |&nbsp; 351 ||&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 27.111.251.106 -&nbsp;&nbsp;&nbsp; 5 |&nbsp; 610 |&nbsp; 582 |&nbsp; 271 |&nbsp; 345 |&nbsp; 420 |&nbsp; 355 ||&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 103.4.115.248 -&nbsp;&nbsp;&nbsp; 2 |&nbsp; 670 |&nbsp; 657 |&nbsp; 259 |&nbsp; 332 |&nbsp; 374 |&nbsp; 346 ||________________________________________________|______|______|______|______|______|______|&nbsp;&nbsp; WinMTR v0.92 GPL V2 by Appnor MSP - Fully Managed Hosting &amp; Cloud Provider

They told me to draw your attention to the point at 10ge1-3.core1.lax2.he.net, where a large spike in latency occurs, and to request that Cox look into this provider, as they could find no clear data on that address.

health_edge · Answer

Looks like Vocus has HE doing it's IP transit. If that is correct, then Vocus is paying HE(Hurricane Electric) &nbsp;to route their traffic, Cox isn't paying them. And since Cox isn't their customer, they aren't going to have much pull with HE. I think the correct escalation path would be to have WoW contact their ISP(Vocus) so they can contact HE about the routing problem. If I had to guess, they are going over bandwidth.

lonecandy · Answer

Hello Tiffany!
Yes, the problem is continuing, at roughly the same levels today as it has all week. There were a few times this morning where it even spiked far higher--into the 1500ms range--but I can't tell if that is being caused by the same issue. How would I contact Vocus, or is that something I should get the game's technical support to look into?

Forum Discussion

New latency problem in WoW

2 Replies

Related Content

Uplink Latency/Packet Loss

Internet Performance Poor Latency - Repeat of Prior Problem Resolved

Panoramic WiFi Problems

High latency and terrible upload speeds

Modem problem

Recent Discussions

Welcome to the Archives

Gigablast

Beeping Noise

mic/status led on contour 2 remote

Internet connectivity frustrations