Frequent DC/lag issues recently

Support Technical Support
1

I have been frequent disconnects from WoW for the past week or so. I have flushed my DNS, renewed my IP address, run cable diagnostics through my ethernet properties window… everything I could think of. Everything seems to check out fine.

When running the “Looking Glass” tool, there is a huge lag spike at about the 5th hop. Part of me wants to think it could possibly be my ISP since the connection issues also seem to be affecting other devices on our home network, but I figured I’d try here first just so I’d have some info to present to Cox.

I’ll attach the Looking Glass results below to one of the servers I’ve been playing on the most recently, but please let me know if there is any other information I can provide and I’ll respond as soon as I’m able.

TRACEROUTE:
traceroute to 70.176.64.36 (70.176.64.36), 15 hops max, 60 byte packets
1 Blizzard Blizzard 0.707 ms 0.700 ms 0.703 ms
2 24.105.18.130 (24.105.18.130) 2.639 ms 2.667 ms 2.672 ms
3 137.221.105.14 (137.221.105.14) 2.673 ms 2.675 ms 2.678 ms
4 137.221.66.18 (137.221.66.18) 2.654 ms 2.664 ms 2.666 ms
5 137.221.83.82 (137.221.83.82) 1682.129 ms 1682.166 ms 1682.175 ms
6 * * *
7 137.221.68.32 (137.221.68.32) 6.128 ms 42.012 ms 42.021 ms
8 langbbrj02-ae1.301.r2.la.cox. net (68.105.30.129) 5.534 ms 5.469 ms 5.469 ms
9 mcdldsrj01-ae1.0.rd.ph.cox. net (68.1.3.115) 16.738 ms 16.741 ms 16.785 ms
10 * * *
11 * * *
12 * * *
13 * * *
14 * * *
15 * * *

13/08/2020 03:28:18 UTC

TRACEROUTE:
traceroute to 70.176.64.36 (70.176.64.36), 15 hops max, 60 byte packets
1 Blizzard Blizzard 0.451 ms 0.471 ms 0.480 ms
2 24.105.18.130 (24.105.18.130) 0.692 ms 1.139 ms 1.342 ms
3 137.221.105.14 (137.221.105.14) 1.069 ms 1.092 ms 1.104 ms
4 137.221.66.18 (137.221.66.18) 0.802 ms 0.843 ms 0.859 ms
5 137.221.83.82 (137.221.83.82) 1825.946 ms 1825.979 ms 1825.990 ms
6 * * *
7 137.221.68.32 (137.221.68.32) 5.891 ms 5.868 ms 5.878 ms
8 langbbrj02-ae1.301.r2.la.cox. net (68.105.30.129) 6.327 ms 6.353 ms 6.372 ms
9 mcdldsrj01-ae1.0.rd.ph.cox. net (68.1.3.115) 16.598 ms 16.628 ms 16.630 ms
10 * * *
11 * * *
12 * * *
13 * * *
14 * * *
15 * * *

13/08/2020 03:28:18 UTC

PING:
PING 70.176.64.36 (70.176.64.36) 56(84) bytes of data.

— 70.176.64.36 ping statistics —
4 packets transmitted, 0 received, 100% packet loss, time 3000ms

13/08/2020 03:28:18 UTC

PING:
PING 70.176.64.36 (70.176.64.36) 56(84) bytes of data.

— 70.176.64.36 ping statistics —
4 packets transmitted, 0 received, 100% packet loss, time 3001ms

13/08/2020 03:28:19 UTC

TRACEROUTE:
traceroute to 70.176.64.36 (70.176.64.36), 15 hops max, 60 byte packets
1 Blizzard Blizzard 0.845 ms 0.836 ms 0.952 ms
2 24.105.18.130 (24.105.18.130) 1.425 ms 1.738 ms 1.835 ms
3 137.221.105.14 (137.221.105.14) 1.269 ms 1.549 ms 1.578 ms
4 137.221.66.18 (137.221.66.18) 3.105 ms 3.120 ms 3.130 ms
5 137.221.83.82 (137.221.83.82) 1368.968 ms 1368.982 ms 1368.988 ms
6 * * *
7 137.221.68.32 (137.221.68.32) 5.905 ms 5.903 ms 6.077 ms
8 langbbrj02-ae1.301.r2.la.cox. net (68.105.30.129) 5.480 ms 5.508 ms 5.533 ms
9 mcdldsrj01-ae1.0.rd.ph.cox. net (68.1.3.115) 16.678 ms 17.285 ms 17.235 ms
10 * * *
11 * * *
12 * * *
13 * * *
14 * * *
15 * * *

13/08/2020 03:28:23 UTC

PING:
PING 70.176.64.36 (70.176.64.36) 56(84) bytes of data.

— 70.176.64.36 ping statistics —
4 packets transmitted, 0 received, 100% packet loss, time 2998ms

13/08/2020 03:28:24 UTC

TRACEROUTE:
traceroute to 70.176.64.36 (70.176.64.36), 15 hops max, 60 byte packets
1 Blizzard Blizzard 0.308 ms 0.981 ms 1.002 ms
2 37.244.23.3 (37.244.23.3) 0.670 ms 0.683 ms 0.749 ms
3 24.105.62.152 (24.105.62.152) 1.026 ms 1.078 ms 1.126 ms
4 137.221.66.10 (137.221.66.10) 5.050 ms 5.050 ms 5.051 ms
5 * * *
6 137.221.69.32 (137.221.69.32) 37.736 ms 35.782 ms 35.864 ms
7 CHGOBBRJ01GE030100.r2.ch.cox. net (68.105.30.217) 2.186 ms 2.198 ms 2.155 ms
8 chnddsrj01-ae1.0.rd.ph.cox. net (68.1.5.211) 50.499 ms 50.395 ms 50.458 ms
9 * * *
10 * * *
11 * * *
12 * * *
13 * * *
14 * * *
15 * * *

13/08/2020 03:28:27 UTC

PING:
PING 70.176.64.36 (70.176.64.36) 56(84) bytes of data.

— 70.176.64.36 ping statistics —
4 packets transmitted, 0 received, 100% packet loss, time 2998ms

13/08/2020 03:28:29 UTC

MTR:
Start: Thu Aug 13 03:28:19 2020 Blizzard 1.|-- Blizzard 0.0% 10 0.5 1.8 0.4 6.1 2.1
2.|-- 24.105.18.130 0.0% 10 3.6 1.0 0.5 3.6 0.9
3.|-- 137.221.105.14 0.0% 10 0.7 0.9 0.6 1.4 0.0
4.|-- 137.221.66.18 0.0% 10 0.9 4.2 0.4 35.7 11.1
5.|-- 137.221.83.82 0.0% 10 2168. 1500. 1054. 2168. 373.1
6.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0
7.|-- 137.221.68.32 0.0% 10 6.4 14.6 6.1 50.1 17.3
8.|-- langbbrj02-ae1.301.r2.la.cox. net 0.0% 10 5.4 6.4 5.4 13.1 2.2
9.|-- mcdldsrj01-ae1.0.rd.ph.cox. net 0.0% 10 16.6 17.2 16.6 19.6 0.7
10.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0

13/08/2020 03:28:18 UTC

MTR:
Start: Thu Aug 13 03:28:19 2020 Blizzard 1.|-- Blizzard 0.0% 10 0.7 1.0 0.3 5.1 1.3
2.|-- 24.105.18.130 0.0% 10 5.2 1.3 0.6 5.2 1.3
3.|-- 137.221.105.14 0.0% 10 0.8 0.9 0.7 1.1 0.0
4.|-- 137.221.66.18 0.0% 10 0.6 4.2 0.4 35.9 11.2
5.|-- 137.221.83.82 0.0% 10 2165. 1476. 1053. 2165. 353.6
6.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0
7.|-- 137.221.68.32 0.0% 10 6.0 13.3 5.8 43.1 14.8
8.|-- langbbrj02-ae1.301.r2.la.cox. net 0.0% 10 5.4 6.4 5.4 13.1 2.3
9.|-- mcdldsrj01-ae1.0.rd.ph.cox. net 0.0% 10 16.9 17.6 16.7 23.6 2.0
10.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0

13/08/2020 03:28:18 UTC

TRACEROUTE:
traceroute to 70.176.64.36 (70.176.64.36), 15 hops max, 60 byte packets
1 Blizzard Blizzard 0.284 ms 0.278 ms 0.278 ms
2 37.244.23.3 (37.244.23.3) 0.629 ms 0.737 ms 0.838 ms
3 24.105.62.152 (24.105.62.152) 1.252 ms 1.333 ms 1.409 ms
4 137.221.66.10 (137.221.66.10) 2.625 ms 2.642 ms 2.645 ms
5 * * *
6 137.221.69.32 (137.221.69.32) 2.632 ms 2.502 ms 2.496 ms
7 CHGOBBRJ01GE030100.r2.ch.cox. net (68.105.30.217) 3.051 ms 2.569 ms 2.626 ms
8 chnddsrj01-ae1.0.rd.ph.cox. net (68.1.5.211) 50.346 ms 50.438 ms 50.430 ms
9 * * *
10 * * *
11 * * *
12 * * *
13 * * *
14 * * *
15 * * *

13/08/2020 03:28:34 UTC

MTR:
Start: Thu Aug 13 03:28:23 2020 Blizzard 1.|-- Blizzard 0.0% 10 0.3 0.3 0.2 0.4 0.0
2.|-- 24.105.18.130 0.0% 10 0.7 0.7 0.5 1.0 0.0
3.|-- 137.221.105.14 0.0% 10 0.9 1.2 0.8 3.5 0.7
4.|-- 137.221.66.18 0.0% 10 0.7 6.7 0.4 61.8 19.3
5.|-- 137.221.83.82 0.0% 10 1408. 1465. 757.9 2229. 455.8
6.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0
7.|-- 137.221.68.32 0.0% 10 6.0 11.8 5.9 60.4 17.1
8.|-- langbbrj02-ae1.301.r2.la.cox. net 0.0% 10 6.4 5.6 5.4 6.4 0.0
9.|-- mcdldsrj01-ae1.0.rd.ph.cox. net 0.0% 10 16.8 18.3 16.6 27.0 3.2
10.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0

13/08/2020 03:28:23 UTC

MTR:
Start: Thu Aug 13 03:28:24 2020 Blizzard 1.|-- Blizzard 0.0% 10 0.3 0.3 0.2 0.5 0.0
2.|-- 37.244.23.3 0.0% 10 0.5 0.5 0.5 0.6 0.0
3.|-- 24.105.62.152 0.0% 10 12.8 2.6 0.7 12.8 3.6
4.|-- 137.221.66.10 0.0% 10 2.0 3.0 1.9 11.0 2.7
5.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0
6.|-- 137.221.69.32 0.0% 10 6.9 17.3 2.4 76.5 23.6
7.|-- CHGOBBRJ01GE030100.r2.ch.cox. net 0.0% 10 12.3 5.6 2.0 12.3 3.8
8.|-- chnddsrj01-ae1.0.rd.ph.cox. net 0.0% 10 50.8 55.2 50.5 84.0 10.5
9.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0

13/08/2020 03:28:24 UTC

PING:
PING 70.176.64.36 (70.176.64.36) 56(84) bytes of data.

— 70.176.64.36 ping statistics —
4 packets transmitted, 0 received, 100% packet loss, time 2999ms

13/08/2020 03:28:35 UTC

TRACEROUTE:
traceroute to 70.176.64.36 (70.176.64.36), 15 hops max, 60 byte packets
1 Blizzard Blizzard 0.342 ms 0.344 ms 0.501 ms
2 37.244.23.3 (37.244.23.3) 1.124 ms 1.146 ms 1.151 ms
3 24.105.62.152 (24.105.62.152) 1.327 ms 1.428 ms 1.504 ms
4 137.221.66.10 (137.221.66.10) 1.971 ms 2.095 ms 2.112 ms
5 * * *
6 137.221.69.32 (137.221.69.32) 2.597 ms 2.538 ms 2.530 ms
7 CHGOBBRJ01GE030100.r2.ch.cox. net (68.105.30.217) 1.966 ms 2.244 ms 2.246 ms
8 chnddsrj01-ae1.0.rd.ph.cox. net (68.1.5.211) 50.629 ms 50.600 ms 50.597 ms
9 * * *
10 * * *
11 * * *
12 * * *
13 * * *
14 * * *
15 * * *

13/08/2020 03:28:38 UTC

PING:
PING 70.176.64.36 (70.176.64.36) 56(84) bytes of data.

— 70.176.64.36 ping statistics —
4 packets transmitted, 0 received, 100% packet loss, time 2998ms

13/08/2020 03:28:39 UTC

MTR:
Start: Thu Aug 13 03:28:32 2020 Blizzard 1.|-- Blizzard 0.0% 10 0.2 0.3 0.2 0.7 0.0
2.|-- 37.244.23.3 0.0% 10 0.5 0.6 0.4 0.7 0.0
3.|-- 24.105.62.152 0.0% 10 0.9 3.3 0.8 12.4 4.4
4.|-- 137.221.66.10 0.0% 10 2.0 6.7 2.0 37.1 11.3
5.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0
6.|-- 137.221.69.32 0.0% 10 2.9 3.7 2.5 6.7 1.2
7.|-- CHGOBBRJ01GE030100.r2.ch.cox. net 0.0% 10 3.2 3.9 2.1 12.2 3.0
8.|-- chnddsrj01-ae1.0.rd.ph.cox. net 0.0% 10 50.4 57.2 50.4 115.8 20.6
9.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0

13/08/2020 03:28:32 UTC

MTR:
Start: Thu Aug 13 03:28:35 2020 Blizzard 1.|-- Blizzard 0.0% 10 0.3 0.3 0.2 0.5 0.0
2.|-- 37.244.23.3 0.0% 10 0.5 0.6 0.5 0.7 0.0
3.|-- 24.105.62.152 0.0% 10 1.1 1.0 0.9 1.2 0.0
4.|-- 137.221.66.10 0.0% 10 2.2 3.8 1.9 7.6 2.2
5.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0
6.|-- 137.221.69.32 0.0% 10 32.5 6.1 2.5 32.5 9.3
7.|-- CHGOBBRJ01GE030100.r2.ch.cox. net 0.0% 10 2.1 2.4 2.0 4.8 0.6
8.|-- chnddsrj01-ae1.0.rd.ph.cox. net 0.0% 10 50.3 51.1 50.3 53.5 0.9
9.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0

13/08/2020 03:28:35 UTC

1 Like
2

Howdy Majima,

I didn’t notice any problems in that Looking Glass test but this is just a one way test from the servers to your location. If you can provide a WinMTR test that would help as it shows what’s happening from your location to the servers which can be different:
Would you be able to provide a WinMTR test so we can gather more details?

  1. Download WinMTR
  2. Unzip the file to your desktop
  3. Run the WinMTR as Admin
  4. Type 137.221.105.2 in “host”.
  5. Click “Start” and open the game. Let the MTR test run for at least 10 minutes to capture this issue occurring.
  6. Click “Copy text to clipboard”
  7. Type two sets of four squiggly lines and then paste the contents of the WinMTR test between: ~~~~ Paste WinMTR Test Results Here ~~~~

Note: If it’s not letting you post, break links by adding a space before .com/.net, so you can post them. You can also upload the MTR contents through Pastebin and post the link (ex: Pastebin (dot) com/123456).

1 Like
3 
|------------------------------------------------------------------------------------------|
|                                      WinMTR statistics                                   |
|                       Host              -   %  | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
|                         router.asus.com -    0 |  587 |  587 |    0 |    0 |   28 |    0 |
|                               10.85.0.1 -    2 |  551 |  542 |    6 |   10 |   59 |    9 |
|                          100.127.76.146 -    2 |  551 |  542 |    7 |   11 |   52 |   11 |
|                          100.120.100.34 -    2 |  551 |  542 |    7 |   13 |  107 |    8 |
|                              68.1.4.252 -    2 |  547 |  537 |   18 |   25 |   91 |   23 |
|                           68.105.30.130 -    2 |  547 |  537 |   19 |   27 |  108 |   20 |
|              ae1-br01-eqla1.as57976.net -    2 |  547 |  537 |   27 |  223 | 1288 |  172 |
|                   No response from host -  100 |  118 |    0 |    0 |    0 |    0 |    0 |
|        et-0-0-0-pe02-swlv10.as57976.net -    2 |  547 |  537 |   22 |   29 |  117 |   25 |
|       las-swlv10-ia-bons-02.as57976.net -    3 |  539 |  527 |   24 |   28 |   49 |   27 |
|                           137.221.105.2 -    2 |  551 |  542 |   24 |   28 |   67 |   30 |
|________________________________________________|______|______|______|______|______|______|
   WinMTR v0.92 GPL V2 by Appnor MSP - Fully Managed Hosting & Cloud Provider ~~~~
4

As it so happened, I had a d/c almost immediately after logging in (around 6:23 local time), and then a pretty solid lag spike around 6:26. Those numbers don’t look bad either, so I only have a few guesses left if you don’t see anything out of the ordinary still. :frowning_face:

Edit: I still D/C connected directly to the modem as well. Numbers aren’t much different while running the MTR, but I’m happy to post the short run I did get if you’d like.

5

Hey there,

It looks like the router is connected to a separate private IP. This is normally a modem or similar device. It’s between the router and this other device that there is a bit of packet loss which may be resulting in the disconnects.

If you’re able, try running a wired connection directly to the modem to see if that helps to resolve the issue. This will help verify if the problem is the modem itself, or is instead related to the router or cabling between the other devices.

I do hope this information helps. Cheers!

6

I did try connecting directly to modem (all I have is my pc > router > modem > internet) at some point, and it still d/c’d. I spoke to Cox tech support, and after a few transfers they decided to schedule a tech to come and visit, which won’t be until the 19th. I’m glad you mentioned the cabling, though, because that what I’m now leaning towards as well.

I’ll try to keep an eye on things between now and the 19th and I can update this thread.

Thank you so much for the help Kaldraydis. :+1:

7

It’s not your ISP Im on Google Fiber and the same thing is happening. This is on Blizz’s side and they dont have it figured out yet so they are telling us to jump through hoops.

2 Likes
8

Sounds like a good plan! Another thing to check on while you’re waiting for the technician would be running that same winMTR test while connected directly to the modem. You’d basically want to check if there is still that same 2% loss happening whenever you disconnect.

Doing something called a Factory Reset on the device may also help, but you’d want to check with the ISP to ensure there is no special setup required after doing so. Some require an “Activation” of the device or similar.

Let us know how things go!

1 Like
9

I am having the same issues. I have had my ISP out they changed out lines and router but i am still having huge lag spikes and disconnects. The game is basically unplayable for me at the moment. Been happening for about a week. I have tried everything on the suggested post of what to do to fix it and nothing has worked.

10

i would start a new thread and post a winmtr

1 Like
11

Kaldraydis: I believe I tried running a winMTR when connected to the modem and saved the file. It only lasted about 2 minutes before I disconnected again, but I’ll take a look when I’m on my desktop.

I’ll definitely do a backup and factory reset on my ASUS router, but if the address starting with 10 right before my public facing IP address is an issue, I’m curious about that. Seems to be a Cox thing, but… :man_shrugging:

I’ll certainly let you know though!

Others: I appreciate the input. For now I’ll assume it’s on my ISP’s end, but I hope my info will help you out either way.

12

This issue has nothing to do with your internet. This is Blizzards end. Every single person i know that is playing is having this issue we cant even finish two bosses in a dungeon before we get disc or booted.

Stop blaming your crap network skills on peoples internet blizzard and fix the issue since we all pay 15 a month to play this game after its been out for 16 years maybe you would think you could have this game run without hiccups finally

3 Likes
14

That’s pretty much it Dakay. Although I don’t fault them for having issues it is a complex endeavor. However, making us jump through hoops is annoying. This just magically started happening a few days ago after a solid 3 months of play since I came back to Classic. I can play any other game just fine online and I have reinstalled the game, cleared all addons, cycled my routers… basically the whole nine yards and nothing works. It’s Blizz. I’m on Google Fiber for crying out loud. It’s not my internet or hardware.

Guess Ill go play something else and hope that Tuesday’s restart fixes the issue.

15

If either of you would like to post a winmtr, it should just take you a few minutes to run, and then if it shows no problems with your internet connection, we can move on to blaming blizzard

2 Likes
16

Everyone, go create another thread. Please? My issues seem to be affecting my connection to more than just Blizzard games.

1 Like
17

As promised, here’s my update so far:

Apparently the box outside my apartment building has jitter ranging as high at 60 to 70 ms, and packet loss around 6 to 8%. That’s according to the technician who just came by. They said repairs may take about a week or so, so I guess I’ll hold out until then.

If anything else comes up, should I reply to this post or create a new one?

1 Like
18

Either would be alright, but I think you’d be fine to continue in this thread.

2 Likes
19

Definitely reply here, since the staff is already responding to your thread :slight_smile:

1 Like