High latency - centurylink! Mainthread

Hello for the past month. I have random high latency in the afternoons into evenings. There is unfortunately not much consistency on when it occurs. I have done numerous Trace-route tests though and can see a clear spot where it occurs. The connection is through Century link.

When the route gets to the step where it hits BLIZZARD-EN.ear7.Chicago2.Level3. net that is where the latency jumps up significantly

6 49 ms 47 ms 48 ms ae-1-3508.ear7.Chicago2.Level3. net [4.69.142.174]
7 238 ms 247 ms 258 ms BLIZZARD-EN.ear7.Chicago2.Level3. net [4.7.196.134]
8 247 ms 256 ms 259 ms ae1-br02-eqch2.as57976. net [137.221.69.35]
9 258 ms 233 ms 224 ms be2-pe01-eqch2.as57976. net [137.221.69.71]
10 237 ms 243 ms 255 ms 24.105.62.129

Everything before step 6 is normal and fine. So I am unsure of what is causing this issue. I have contacted my ISP to which they have no clue on how to address an issues where 1 game is having this kind of latency issue. They keep telling me to reboot the router or replace the modem or schedule a tech visit. And I keep informing them that isn’t going to help. I am unsure of what else I can do to resolve this issue as it gets quite frustrating having multiple hours blocked out play wise because of this. I also have no clue if this is an issue with the ISP or with Blizzard, and if the issue is with the ISP how to even approach them with how to fix it.

3 Likes

I am also a CenturyLink user and have been experiencing higher than normal latency lately. After reading this post, I decided to run a trace-route myself.

Tracing route to 24.105.62.129 over a maximum of 30 hops

1 3 ms 3 ms 3 ms 192.168.1.1
2 4 ms 3 ms 3 ms 192.168.0.1
3 18 ms 18 ms 17 ms rb4-bras.wnvl.centurytel. net [71.33.3.11]
4 19 ms 18 ms 18 ms clma-agw1.inet.qwest. net [71.33.2.81]
5 33 ms 32 ms 32 ms dvr3-brdr-01.inet.qwest. net [208.168.152.134]
6 * 37 ms 32 ms 63-235-41-90.dia.static.qwest. net [63.235.41.90]
7 75 ms 74 ms 75 ms ae-1-3508.ear7.Chicago2.Level3. net [4.69.142.174]
8 263 ms 236 ms 257 ms BLIZZARD-EN.ear7.Chicago2.Level3. net [4.7.196.134]
9 253 ms 262 ms 253 ms ae1-br01-eqch2.as57976. net [137.221.69.33]
10 247 ms 242 ms 265 ms be1-pe02-eqch2.as57976. net [137.221.69.69]
11 266 ms 264 ms 244 ms 24.105.62.129

1 Like

Same Issue. just started another thread…

Hi Blizzard TS Support - experiencing high latency with CenturyLink. Problem appears to be a the Level 3 backbone, suggestions?

Trace Route:

Tracing route to 24.105.62.129 over a maximum of 30 hops

1 <1 ms <1 ms <1 ms 192.168.1.1
2 8 ms 6 ms 7 ms 67-4-0-254.sxfl.qwest [67.4.0.254]
3 4 ms 4 ms 5 ms stpl-agw1.inet.qwest [207.109.3.137]
4 15 ms 15 ms 16 ms 216-160-19-2.mpls.qwest [216.160.19.2]
5 13 ms 13 ms 15 ms ae-1-3508.ear7.Chicago2.Level3 [4.69.142.174]
6 205 ms 208 ms 247 ms BLIZZARD-EN.ear7.Chicago2.Level3 [4.7.196.134]
7 230 ms 228 ms 218 ms ae1-br02-eqch2.as57976 [137.221.69.35]
8 202 ms 203 ms 229 ms be2-pe01-eqch2.as57976 [137.221.69.71]
9 228 ms 229 ms 218 ms chi-eqch2-ia-bons-02.as57976 [137.221.66.11]
10 228 ms 202 ms 205 ms 24.105.62.129

Trace complete.

Howdy!

We would like to collect more information about this issue. It seems to be getting better but wanted your input on if it has or if it continues to occur? What your average latency in game now?

Thank you!

Hello Zuvykree,

It does look like the issue is better my average in game latency is 47-50. My only concern is that this is just random and it will happen again. Last time it was Monday from like 7-11 pm where it was the same thing with the latency at the same point in the server hops.

Is this an issue on the ISP side or Blizzards side? And if the ISP how do we inform them on how to look into because every time I’ve contacted them they have been very unhelpful and have no clue what im talking about.

If this issue occurs again how should we go about reporting it?

Thank you for your assistance.

1 Like

Hi Zuvykree

I appear to be back to normal; 14-15ms latency on Illidan. I do so love Gig Fiber! Speed is important as you run the Emerald Palace to meet the Queen, she dislikes it when you are late! :slight_smile: Thanks for the quick turn around!

Hello again.

I am having the same issue again. And it seems like the issue is happening at the same spot again. Is there any clarification on where this is occurring?

Tracing route to 24.105.62.129 over a maximum of 30 hops

1 <1 ms <1 ms <1 ms
2 28 ms 28 ms 26 ms
3 29 ms 28 ms 26 ms
4 30 ms 27 ms 28 ms
5 28 ms 28 ms 29 ms 63-235-41-90.dia.static.qwest. net [63.235.41.90]
6 53 ms 52 ms 53 ms ae-1-3508.ear7.Chicago2.Level3. net [4.69.142.174]
7 234 ms 214 ms 223 ms BLIZZARD-EN.ear7.Chicago2.Level3. net [4.7.196.134]
8 226 ms 295 ms 276 ms ae1-br01-eqch2.as57976. net [137.221.69.33]
9 240 ms 243 ms 232 ms be1-pe01-eqch2.as57976. net [137.221.69.67]
10 235 ms 218 ms 225 ms 24.105.62.129

Trace complete.

1 Like

Same problem here, I have Century Link as well… I was okay ever since I got Century Link 2 years ago and now, nothing works tonight…

From the test we’ve received so far, there is concerns with the Level 3 Chicago peering node. starting here that we’ll want to look into:

7 234 ms 214 ms 223 ms BLIZZARD-EN.ear7.Chicago2.Level3. net [4.7.196.134]
8 226 ms 295 ms 276 ms ae1-br01-eqch2.as57976. net [137.221.69.33]

These peering issues can take some time to resolve, but we appreciate your patience and reports on the high latency issues in World of WarCraft. We’re getting everything gathered and inputted on our end that you all have provided so far.

If those impacted by the issue, could you include a WinMTR test while running the game for 10-15 minutes? This is a more detailed test to show us details about the latency and packet loss occurring to our servers.

Hopefully, we’ll have more information on this soon :slight_smile: Thanks for your continued reports!

The issue started up again this evening right around 6 PM (the usual time). Ran a traceroute again

6 59 ms 61 ms 61 ms ae-1-3508.ear7.Chicago2.Level3. net [4.69.142.174]
7 211 ms 221 ms 254 ms BLIZZARD-EN.ear7.Chicago2.Level3 .net [4.7.196.134]
8 221 ms 222 ms 221 ms ae1-br02-eqch2.as57976. net [137.221.69.35]
9 236 ms 229 ms 227 ms be2-pe01-eqch2.as57976. net [137.221.69.71]
10 237 ms 233 ms 233 ms 24.105.62.129

Where the same issue occurred again.

This time I also ran a WinRTM

WinMTR statistics |

| Host - % | Sent | Recv | Best | Avrg | Wrst | Last |

|------------------------------------------------|------|------|------|------|------|------|

| - 0 | 748 | 748 | 0 | 0 | 10 | 0 |

| - 0 | 748 | 748 | 33 | 38 | 119 | 39 |

| - 0 | 748 | 748 | 33 | 39 | 116 | 34 |

| - 0 | 748 | 748 | 34 | 38 | 114 | 35 |

| - 0 | 748 | 748 | 34 | 39 | 544 | 38 |

| ae-1-3508.ear7.Chicago2.Level3. net - 99 | 152 | 2 | 0 | 60 | 61 | 61 |

| BLIZZARD-EN.ear7.Chicago2.Level3. net - 1 | 733 | 729 | 220 | 266 | 702 | 280 |

| ae1-br02-eqch2.as57976. net - 1 | 721 | 714 | 223 | 263 | 362 | 283 |

| be2-pe01-eqch2.as57976. net - 1 | 737 | 734 | 227 | 262 | 328 | 257 |

| 24.105.62.129 - 2 | 717 | 709 | 223 | 262 | 324 | 257 |

|________________________________________________|______|______|______|______|______|______|

I Hope this helps figure out what is going on, I unfortunately do not know what I’m looking for aside from the fact that there is a large amount of packet loss in that 6th step, but I still am unsure if this is a communication issue between blizzard and Century link or just an issue with Century link. Anything you can advise would be appreciated.

We have Century Link Business Class Fiber 1GB Up & Down. Currently in game Latency shows 250ms when we normally have 13-15 ms.

US CENTRAL

Blockquote
command traceroute -P ICMP 24.105.62.129
traceroute to 24.105.62.129 (24.105.62.129), 64 hops max, 72 byte packets
1 192.168.0.1 (192.168.0.1) 2.553 ms 1.299 ms 1.102 ms
2 stpl-dsl-gw20.stpl.qwest. net (207.109.2.20) 4.344 ms 3.145 ms 3.091 ms
3 stpl-agw1.inet.qwest. net (207.109.3.153) 3.861 ms 4.970 ms 3.681 ms
4 216-160-19-2.mpls.qwest. net (216.160.19.2) 3.696 ms 4.824 ms 3.594 ms
5 * * *
6 blizzard-en.ear7.chicago2.level3. net (4.7.196.134) 310.452 ms 256.874 ms 238.187 ms
7 ae1-br02-eqch2.as57976. net (137.221.69.35) 237.829 ms 230.189 ms 232.413 ms
8 be2-pe02-eqch2.as57976. net (137.221.69.73) 237.477 ms 239.855 ms 227.573 ms
9 24.105.62.129 (24.105.62.129) 222.204 ms 290.926 ms *

US WEST

Blockquote
traceroute to 137.221.105.2 (137.221.105.2), 64 hops max, 72 byte packets
1 192.168.0.1 (192.168.0.1) 1.766 ms 1.443 ms 2.476 ms
2 stpl-dsl-gw20.stpl.qwest. net (207.109.2.20) 4.549 ms 3.123 ms 3.717 ms
3 stpl-agw1.inet.qwest. net (207.109.3.153) 11.341 ms 3.336 ms 3.738 ms
4 216-160-19-2.mpls.qwest. net (216.160.19.2) 3.740 ms 4.611 ms 3.451 ms
5 * * *
6 blizzard-en.ear7.chicago2.level3. net (4.7.196.134) 238.261 ms * 237.255 ms
7 ae1-br01-eqch2.as57976. net (137.221.69.33) 52.802 ms 55.030 ms 51.963 ms
8 137.221.65.132 (137.221.65.132) 52.101 ms 52.526 ms 52.549 ms
9 et-0-0-31-pe02-swlv10.as57976. net (137.221.83.69) 52.656 ms 53.316 ms 66.202 ms
10 las-swlv10-ia-bons-04.as57976. net (137.221.66.23) 53.656 ms 53.061 ms 52.374 ms
11 137.221.105.2 (137.221.105.2) 52.396 ms 52.381 ms 54.379 ms

Hope this helps solve this annoyance =)

Currently work for CenturyLink in Denver. Going to dig deeper into this with some engineer coworkers, maybe get in touch with Chicago and see what we can do.

PS Having same issues

2 Likes

Having ping issues as well, they’ve been a bit intermittent. Pathping below. Will look into running a WinMTR as well.

Tracing route to 24.105.62.129 over a maximum of 30 hops

  0  PROJECT-J [192.168.0.71] 
  1  router.lan [192.168.0.1] 
  2  mo-184-6-96-1.dhcp.embarqhsd.net [184.6.96.1] 
  3  wrbg-agw1.inet.qwest.net [71.33.4.49] 
  4  dvr3-brdr-01.inet.qwest.net [208.168.152.134] 
  5     *        *     63-235-41-90.dia.static.qwest.net [63.235.41.90] 
  6  ae-1-3508.ear7.chicago2.level3.net [4.69.142.174] 
  7  blizzard-en.ear7.chicago2.level3.net [4.7.196.134] 
  8  ae1-br02-eqch2.as57976.net [137.221.69.35] 
  9  be2-pe02-eqch2.as57976.net [137.221.69.73] 
 10  24.105.62.129 

Computing statistics for 250 seconds...
        Source to Here   This Node/Link
Hop  RTT    Lost/Sent = Pct  Lost/Sent = Pct  Address
  0                                           PROJECT-J [192.168.0.71] 
                            0/ 100 =  0%   |
  1    0ms     0/ 100 =  0%     0/ 100 =  0%  router.lan [192.168.0.1] 
                            0/ 100 =  0%   |
  2    4ms     0/ 100 =  0%     0/ 100 =  0%  mo-184-6-96-1.dhcp.embarqhsd.net [184.6.96.1] 
                            0/ 100 =  0%   |
  3    5ms     0/ 100 =  0%     0/ 100 =  0%  wrbg-agw1.inet.qwest.net [71.33.4.49] 
                            0/ 100 =  0%   |
  4   19ms     0/ 100 =  0%     0/ 100 =  0%  dvr3-brdr-01.inet.qwest.net [208.168.152.134] 
                            0/ 100 =  0%   |
  5   19ms     0/ 100 =  0%     0/ 100 =  0%  63-235-41-90.dia.static.qwest.net [63.235.41.90] 
                            0/ 100 =  0%   |
  6   62ms     0/ 100 =  0%     0/ 100 =  0%  ae-1-3508.ear7.chicago2.level3.net [4.69.142.174] 
                            0/ 100 =  0%   |
  7  249ms     0/ 100 =  0%     0/ 100 =  0%  blizzard-en.ear7.chicago2.level3.net [4.7.196.134] 
                            1/ 100 =  1%   |
  8  247ms     1/ 100 =  1%     0/ 100 =  0%  ae1-br02-eqch2.as57976.net [137.221.69.35] 
                            1/ 100 =  1%   |
  9  245ms     2/ 100 =  2%     0/ 100 =  0%  be2-pe02-eqch2.as57976.net [137.221.69.73] 
                            2/ 100 =  2%   |
 10  246ms     4/ 100 =  4%     0/ 100 =  0%  24.105.62.129 

Trace complete.

just switched to century link and having the same issue. 18 home and 500 world

Hey folks, I really appreciate all the connection tests! We are seeing clear latency spikes this evening on our end. This has been able to get this escalated so our network engineers to look into this further and hopefully reach out to Level 3 or the appropriate parties needed.

I’ll continue to update as we have more information available and hopefully, tame these daily evening latency spikes! Thank you all, again :blush:

3 Likes

I have century link as well and i’m 294 and higher home and 443 and higher world. not sure how to do the trace, or what server i would trace to.

I am using centurylink and having a similar connection issue to the retail server (US-Thrall) I am on. It tends to be slow around 7PM MST to about 9PM MST randomly for the last week.

It tends to sit around 300-700MS I am able to connect to the wow classic server US-Bigglesworth with little to no latency the connection is consistent with 50ms.

Same issue century Link

-----------------------------------------------------------------------------------------|

| WinMTR statistics |

| Host - % | Sent | Recv | Best | Avrg | Wrst | Last |

|------------------------------------------------|------|------|------|------|------|------|

| ip address hidden - 0 | 338 | 338 | 0 | 0 | 7 | 0 |

| boid-dsl-gw13.boid.qwest. net - 0 | 338 | 338 | 18 | 20 | 84 | 18 |

| 184-99-65-97.boid.qwest. net - 0 | 338 | 338 | 18 | 19 | 66 | 21 |

| sea-brdr-03.inet.qwest. net - 0 | 338 | 338 | 28 | 30 | 79 | 30 |

| No response from host - 100 | 67 | 0 | 0 | 0 | 0 | 0 |

| No response from host - 100 | 67 | 0 | 0 | 0 | 0 | 0 |

| BLIZZARD-EN.ear3.LosAngeles1.Level3. net - 0 | 338 | 338 | 46 | 51 | 112 | 46 |

| ae1-br01-eqla1.as57976. net - 3 | 310 | 303 | 264 | 296 | 405 | 306 |

| et-0-0-2-br01-swlv10.as57976. net - 3 | 310 | 303 | 264 | 292 | 416 | 315 |

| 137.221.65.133 - 5 | 282 | 270 | 266 | 379 | 3515 | 447 |

| be1-pe02-eqch2.as57976. net - 2 | 322 | 318 | 261 | 289 | 311 | 300 |

| 24.105.62.129 - 1 | 326 | 323 | 264 | 291 | 335 | 293 |

|________________________________________________|______|______|______|______|______|______|

Been experiencing the same latency issues on Mal’Ganis, winMTR results below

|------------------------------------------------------------------------------------------|

| WinMTR statistics |

| Host - % | Sent | Recv | Best | Avrg | Wrst | Last |

|------------------------------------------------|------|------|------|------|------|------|

| 192.168.0.1 - 0 | 532 | 532 | 0 | 0 | 29 | 0 |

| boid-dsl-gw14.boid.qwest. net - 1 | 528 | 527 | 18 | 20 | 72 | 19 |

| boid-agw1.inet.qwest. net - 0 | 532 | 532 | 19 | 19 | 48 | 19 |

| sea-brdr-02.inet.qwest. net - 1 | 528 | 527 | 29 | 30 | 50 | 30 |

| 63.146.27.78 - 1 | 528 | 527 | 30 | 32 | 59 | 34 |

| st0wa81crs.ip.att. net - 0 | 532 | 532 | 64 | 66 | 78 | 66 |

| st6wa22crs.ip.att. net - 0 | 532 | 532 | 64 | 68 | 87 | 66 |

| cgcil22crs.ip.att. net - 0 | 532 | 532 | 64 | 68 | 85 | 70 |

| cr81.cgcil.ip.att. net - 0 | 532 | 532 | 64 | 65 | 95 | 65 |

| 32.130.248.136 - 0 | 532 | 532 | 64 | 65 | 88 | 66 |

| 32.130.248.163 - 0 | 532 | 532 | 64 | 65 | 91 | 65 |

| No response from host - 100 | 107 | 0 | 0 | 0 | 0 | 0 |

| No response from host - 100 | 107 | 0 | 0 | 0 | 0 | 0 |

| No response from host - 100 | 107 | 0 | 0 | 0 | 0 | 0 |

| No response from host - 100 | 107 | 0 | 0 | 0 | 0 | 0 |

| No response from host - 100 | 107 | 0 | 0 | 0 | 0 | 0 |

| No response from host - 100 | 107 | 0 | 0 | 0 | 0 | 0 |

| No response from host - 100 | 107 | 0 | 0 | 0 | 0 | 0 |

| No response from host - 100 | 107 | 0 | 0 | 0 | 0 | 0 |

| No response from host - 100 | 107 | 0 | 0 | 0 | 0 | 0 |

| No response from host - 100 | 107 | 0 | 0 | 0 | 0 | 0 |

| No response from host - 100 | 107 | 0 | 0 | 0 | 0 | 0 |

| No response from host - 100 | 107 | 0 | 0 | 0 | 0 | 0 |

| No response from host - 100 | 107 | 0 | 0 | 0 | 0 | 0 |

| No response from host - 100 | 107 | 0 | 0 | 0 | 0 | 0 |

| No response from host - 100 | 107 | 0 | 0 | 0 | 0 | 0 |

| No response from host - 100 | 107 | 0 | 0 | 0 | 0 | 0 |

| No response from host - 100 | 107 | 0 | 0 | 0 | 0 | 0 |

| No response from host - 100 | 107 | 0 | 0 | 0 | 0 | 0 |

| No response from host - 100 | 107 | 0 | 0 | 0 | 0 | 0 |

|________________________________________________|______|______|______|______|______|______|

I had to add some characters to prevent it from being a link for some reason. but this is where my centurylink service is jamming up. I live in NM, and we had balloon fiest this week, I assumed the poor latency issue was from all the people uploading pictures. Now that it is over, the issue remains. The game is not worth playing once the latency is over 300.

8 53 ms 53 ms 54 ms 'BLIZZARD-EN.ear3.LosAngeles1.'Level3.‘net[4.71.135.106]
9 250 ms 432 ms 661 ms ae1’-br01-eqla1.as57976.net [137.221.68.33]

Also Centurylink Employee in Santa Fe. This is not within my field of normal work, sorry we are all going through this.