High latency - centurylink! Mainthread

Support Technical Support
11

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.

13

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 =)

14

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
15

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.
16

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

17

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
18

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.

19

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.

20

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 |

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

22

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 |

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

23

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.

24

I also have found other servers that have no latency issues during the time that mine is unusable. Also run close to 50MS on those servers.

25

This issue is starting up again about 5-10 mins ago. Trace routes showing the same thing.

6 * 54 ms 53 ms ae-1-3508.ear7.Chicago2.Level3. net [4.69.142.174]
7 211 ms 225 ms 212 ms BLIZZARD-EN.ear7.Chicago2.Level3. net [4.7.196.134]
8 207 ms 211 ms 206 ms ae1-br01-eqch2.as57976. net [137.221.69.33]
9 206 ms 205 ms 205 ms be1-pe01-eqch2.as57976 .net [137.221.69.67]
10 205 ms 201 ms 208 ms 24.105.62.129

Sadly before it was just an occasional thing. It is now becoming nightly right at 6 pm.

26

Started at about 6:50pm CST for me this evening. Here’s the MTR:
|------------------------------------------------------------------------------------------|
| WinMTR statistics |

Host - % Sent Recv Best Avrg Wrst Last
Address Hidden - 0 1001 1001 0 0 2 0
rb4-bras .wnvl.centurytel.net - 1 997 996 1 5 126 3
clma -agw1.inet.qwest.net - 0 1001 1001 2 9 129 5
dvr3-brdr -01.inet.qwest.net - 0 1001 1001 16 22 139 18
No response from host - 100 200 0 0 0 0 0
No response from host - 100 200 0 0 0 0 0
BLIZZARD-EN .ear7.Chicago2.Level3.net - 1 997 996 178 242 634 239
ae1-br01 -eqch2.as57976.net - 6 787 742 0 340 4478 584
be1-pe02 -eqch2.as57976.net - 0 1000 1000 179 238 375 275
24.105.62.129 - 1 993 991 181 239 321 249
________________________________________________ ______ ______ ______ ______ ______ ______

WinMTR v0.92 GPL V2 by Appnor MSP - Fully Managed Hosting & Cloud Provider

27

Problem has returned right as I am posting this.

28

it’s back

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 4 ms 4 ms 4 ms 67-4-0-254.sxfl.qwest [67.4.0.254]
3 4 ms 4 ms 4 ms stpl-agw1.inet.qwest [207.109.3.137]
4 4 ms 5 ms 4 ms 216-160-19-2.mpls.qwest [216.160.19.2]
5 * * * Request timed out.
6 218 ms 226 ms 239 ms BLIZZARD-EN.ear7.Chicago2.Level3[4.7.196.134]
7 240 ms 238 ms 218 ms ae1-br02-eqch2.as57976 [137.221.69.35]
8 214 ms 227 ms 239 ms be2-pe01-eqch2.as57976 [137.221.69.71]
9 240 ms 240 ms 217 ms chi-eqch2-ia-bons-02.as57976 [137.221.66.11]
10 216 ms 217 ms 240 ms 24.105.62.129

Trace complete.

29

yep same issue for me again as well…seems to be about the same time every day for the last several days.

30

This is driving me crazy… How are we supposed to be raiding in mythic with freaking 300-700ms?! It’s been like this for almost a week and still not solved… Is this why we have been paying 15$ per month for 15 years?

1 Like
31

And again tonight:

US CENTRAL

Blockquote
Last login: Tue Oct 15 08:55:26 on console
$ 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) 1.606 ms 1.529 ms 1.114 ms
2 stpl-dsl-gw20.stpl.qwest. net (207.109.2.20) 4.434 ms 4.777 ms 4.965 ms
3 stpl-agw1.inet.qwest. net (207.109.3.153) 22.034 ms 5.209 ms 4.265 ms
4 216-160-19-2.mpls.qwest. net (216.160.19.2) 5.681 ms 4.990 ms 5.416 ms
5 ae-1-3508.ear7.chicago2.level3. net (4.69.142.174) 12.334 ms 13.113 ms 12.628 ms
6 blizzard-en.ear7.chicago2.level3. net (4.7.196.134) 285.876 ms 210.732 ms 224.336 ms
7 ae1-br02-eqch2.as57976. net (137.221.69.35) 233.851 ms 237.298 ms 232.783 ms
8 be2-pe02-eqch2.as57976. net (137.221.69.73) 214.045 ms 236.119 ms 236.561 ms
9 24.105.62.129 (24.105.62.129) 226.808 ms 213.924 ms 234.766 ms

US WEST

Blockquote
traceroute -P ICMP 137.221.105.2
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.898 ms 1.108 ms 1.052 ms
2 stpl-dsl-gw20.stpl.qwest. net (207.109.2.20) 4.621 ms 4.277 ms 4.289 ms
3 stpl-agw1.inet.qwest. net (207.109.3.153) 5.476 ms 4.497 ms 5.175 ms
4 216-160-19-2.mpls.qwest. net (216.160.19.2) 5.185 ms 4.653 ms 4.732 ms
5 * ae-1-3508.ear7.chicago2.level3. net (4.69.142.174) 12.927 ms 14.157 ms
6 blizzard-en.ear7.chicago2.level3. net (4.7.196.134) 209.093 ms 229.451 ms 237.334 ms
7 ae1-br01-eqch2.as57976. net (137.221.69.33) 53.871 ms 53.268 ms 52.297 ms
8 137.221.65.132 (137.221.65.132) 64.294 ms 100.688 ms 63.267 ms
9 et-0-0-31-pe02-swlv10.as57976. net (137.221.83.69) 53.760 ms 53.715 ms 52.880 ms
10 las-swlv10-ia-bons-04.as57976. net (137.221.66.23) 52.094 ms 58.789 ms 59.050 ms
11 137.221.105.2 (137.221.105.2) 52.035 ms 53.289 ms 52.382 ms

32
WinMTR Statistics

WinMTR statistics

Host % Sent Recv Best Avrg Wrst Last
192.168.0.1 0 829 829 0 0 6 0
rb2-bras.ka.centurytel.net 0 829 829 28 30 99 30
No response from host 100 166 0 0 0 0 0
bb-klslmtxc-jx4-01-ae0.core.centurytel.net 0 829 829 29 33 100 31
bb-sttlwawb-jx4-01-ae1-0.core.centurytel.net 0 829 829 46 50 132 47
bb-sttlwawb-jx4-02-ae0.core.centurytel.net 0 829 829 46 51 145 48
bb-dnvtc056-jx4-01-ae2.core.centurytel.net 0 829 829 76 80 168 77
bb-dnvtc056-jx4-02-ae0.core.centurytel.net 1 825 824 76 81 165 76
No response from host 100 166 0 0 0 0 0
dvr3-brdr-01.inet.qwest.net 0 829 829 63 70 162 65
No response from host 100 166 0 0 0 0 0
No response from host 100 166 0 0 0 0 0
BLIZZARD-EN.ear7.Chicago2.Level3.net 2 786 775 264 301 383 283
ae1-br02-eqch2.as57976.net 2 782 770 262 299 534 283
be2-pe01-eqch2.as57976.net 2 790 780 262 297 421 284
chi-eqch2-ia-bons-02.as57976.net 2 774 760 264 298 357 293
24.105.62.129 3 759 742 267 298 384 315