High latency - centurylink! Mainthread

Just like clockwork. Every night, same issue.

Tracing route to 24.105.62.129 over a maximum of 30 hops

  1    <1 ms    <1 ms    <1 ms  Firewall [192.168.117.1]
  2    13 ms    27 ms     4 ms  blng-dsl-gw16.blng.qwest.net [67.42.227.16]
  3    30 ms     8 ms     4 ms  blng-agw1.inet.qwest.net [65.100.79.121]
  4    16 ms    19 ms    16 ms  dvr3-brdr-01.inet.qwest.net [208.168.152.134]
  5     *        *        *     Request timed out.
  6     *        *        *     Request timed out.
  7   224 ms   222 ms   216 ms  BLIZZARD-EN.ear7.Chicago2.Level3.net [4.7.196.134]
  8   212 ms   209 ms   217 ms  ae1-br02-eqch2.as57976.net [137.221.69.35]
  9   226 ms   222 ms   216 ms  be2-pe02-eqch2.as57976.net [137.221.69.73]
 10   236 ms   232 ms   225 ms  24.105.62.129

Trace complete.

It has returned again for the 3rd day in a row.

My ping is still going really high around 9pm EST

Just switched to Centurylink Fiber a few weeks ago and was always at 26ms, now I am over 200. Live in Denver and am playing on an east coast server going right through Chicago.

Tracing route to 24.105.62.129 over a maximum of 30 hops

1 <1 ms <1 ms <1 ms home [192.168.1.1]
2 25 ms 2 ms 2 ms hlrn-dsl-gw08.hlrn.qwest.ne t [207.225.112.8]
3 2 ms 2 ms 2 ms 63-225-124-57.hlrn.qwest.ne t [63.225.124.57]
4 3 ms 3 ms 3 ms dvr3-brdr-01.inet.qwest.ne t [208.168.152.134]
5 3 ms 3 ms 3 ms 63-235-41-90.dia.static.qwest.ne t [63.235.41.90]
6 27 ms 27 ms 27 ms ae-1-3508.ear7.Chicago2.Level3.ne t [4.69.142.174]
7 216 ms 228 ms 217 ms BLIZZARD-EN.ear7.Chicago2.Level3.ne t [4.7.196.134]
8 226 ms 225 ms 225 ms ae1-br02-eqch2.as57976.ne t [137.221.69.35]
9 233 ms 232 ms 215 ms be2-pe01-eqch2.as57976.ne t [137.221.69.71]
10 230 ms 227 ms 223 ms chi-eqch2-ia-bons-02.as57976.ne t [137.221.66.11]
11 226 ms 220 ms 222 ms 24.105.62.129

Trace complete.

Also have Centurylink here. Below is the MTR that was ran with the GM I spoke with over chat.

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

| WinMTR statistics |

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

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

| modem.Home - 0 | 98 | 98 | 0 | 0 | 5 | 0 |

| albq-dsl-gw50.albq.qwest. net - 0 | 98 | 98 | 1 | 4 | 45 | 3 |

| albq-agw1.inet.qwest. net - 0 | 98 | 98 | 1 | 2 | 21 | 2 |

| phn4-edge-03.inet.qwest. net - 0 | 98 | 98 | 13 | 13 | 29 | 13 |

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

| ae-1-51.ear3.LosAngeles1.Level3. net - 95 | 20 | 1 | 0 | 787 | 787 | 787 |

| BLIZZARD-EN.ear3.LosAngeles1.Level3. net - 0 | 98 | 98 | 23 | 31 | 193 | 74 |

| ae1-br01-eqla1.as57976. net - 0 | 98 | 98 | 223 | 253 | 337 | 252 |

| et-0-0-2-br01-swlv10.as57976. net - 0 | 98 | 98 | 222 | 249 | 296 | 257 |

| 137.221.65.133 - 0 | 98 | 98 | 223 | 282 | 840 | 256 |

| be1-pe02-eqch2.as57976. net - 0 | 98 | 98 | 223 | 247 | 260 | 255 |

| chi-eqch2-ia-bons-04.as57976. net - 0 | 98 | 98 | 223 | 248 | 262 | 252 |

| 24.105.62.129 - 0 | 98 | 98 | 223 | 248 | 261 | 251 |

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

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

figured i would post here saying i’m doing good tonight as of 6:07 PM mountain time, my ping is 97 ms home and 88 ms world, if it spikes again i’ll do another MTR post.

Oh its starting again. Its slowly creeping its way up.

3 Likes

Started later than usual for me tonight, too, but I’m back up in the 200-300 ms range now.

Same for me. Running MTR now

I logged on about 30 mins ago and it has slowly crept up from 52 ms, to now 220 ms.

yup I was thinking it may be fixed since I logged on to raid at 50 ms but it has now crept back up to 230ms

yep back up 277ms home 308ms world 7:11pm mountain time

  • Updated -

I just got an update right after saying that! Our network team is in touch with this ISP to help resolve a possible hardware issue along the route. No need for any updated WinMTRs at this time!

No ETA on a fix just yet but they are actively looking into resolving this issue.

2 Likes

Here you go

|-------------------------------------------------------------------------|
| WinMTR statistics |

Host - % Sent Recv Best Avrg Wrst Last
MyRouter-0 578 578 0 0 5 0
67.199.183.1-1 554 549 9 40 3409 15
67.199.160.3-0 578 578 9 16 74 13
slc2-edge-06.inet.qwest.net-0 578 578 10 16 66 15
dvr3-brdr-01.inet.qwest.net-0 578 578 19 23 78 21
No response from host-100 116 0 0 0 0 0
ae-1-3508.ear7.Chicago2.Level3.net-100 117 1 0 50 50 50
BLIZZARD-EN.ear7.Chicago2.Level3.net-0 578 578 166 233 509 236
ae1-br01-eqch2.as57976.net-0 574 574 55 131 1699 64
137.221.65.132-0 578 578 55 64 153 62
et-0-0-31-pe01-swlv10.as57976.net-0 578 578 56 65 155 65
las-swlv10-ia-bons-02.as57976.net-0 578 578 55 61 91 58
137.221.105.2-0 578 578 55 60 85 63
________________________________________________ ______ ______ ______ ______ ______ ______

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

Ty for the response! Would it be possible to let us known when you believe a resolution is done? That way we can check to make sure and that way if a new issue occurs we treat is appropriately?

Yep! We will update this thread once we get word the issue should be retested or jumps to resolved. Either way we will let you all know!

Day 6 of this latency and obviously the issue is happening between

61 ms ae-1-3508.ear7.Chicago2.Level3. net [4.69.142.174] and
254 ms BLIZZARD-EN.ear7.Chicago2.Level3 .net [4.7.196.134]
or with the peering node [4.7.196.134] itself.

What seems to be clear is that this issue is recurring after your network engineers have gone home and therefore nothing is being done.

but not only happens with that ISP because I also have the same problem, so you don’t just have to consider that ISP …

Latency spiked again tonight. It’s been fine for the past 6 days.

Famished… blaming Blizzard on something they have no control over.