5 30 ms 26 ms 21 ms 63-235-41-90.dia.static.qwest. net
6 * * * Request timed out.
7 181 ms 151 ms 186 ms BLIZZARD-EN.ear7.Chicago2.Level3. net [4.7.196.134]
8 173 ms 180 ms 163 ms ae1-br02-eqch2.as57976. net [137.221.69.35]
9 164 ms 172 ms 168 ms be2-pe2-eqch2.as57976. net [137.221.69.73]
10 146 ms 142 ms 157 ms chi-eqch2-ia-bons-04.as57976. net [137.221.66.15]
11 219 ms 182 ms 173 ms 24.105.62.129
I was having some weird stuff happen on my end too tonight, but you can clearly see the massive packet loss and ping spike at the Level3 node thatās been consistent throughout this thread.
My point is that your connection has some pretty bad latency from the start, which makes it hard to then sort out what the problem is. Youāve essentially got red flags on every hop, so which one is really the issue?
Are you even familiar with this issue? Wannabe forum MVPās are cancer. Take your hot takes elsewhere and let people who actually know about the issue (the blues) handle things.
Issue seems to be getting worse. The lag is lasting longer then last week and is starting way sooner. Its only 5:40 MST PM and Im having the issue already. This is getting frustrating because this is getting up to about 2 months now of this issue occurring. And there is little to no information on progress. Century link is useless in their help.
Still an issue. This is honestly getting ridiculous. It has been like this for over a month.
4 24 ms 31 ms 36 ms dvr3-brdr-01.inet.qwest. net [208.168.152.134]
5 34 ms 31 ms 30 ms 63-235-41-90.dia.static.qwest. net [63.235.41.90]
6 * * * Request timed out.
7 142 ms 130 ms 126 ms blizzard-en.ear7.chicago2.level3. net [4.7.196.134]
8 132 ms 134 ms 131 ms ae1-br02-eqch2.as57976. net [137.221.69.35]
9 144 ms 172 ms 155 ms be2-pe1-eqch2.as57976. net [137.221.69.71]
10 142 ms 169 ms 154 ms 24.105.62.129
I can understand this type of issue taking a while to fix, especially since itās not Blizzardās network. That being said, Iām pretty sure weāve given adequate data that points to a serious problem on the āear7ā level3 backbone in Chicago. The fact itās taking this long to find out what the hell is actually causing the issue, and fix it, is absurd.
Getting high world latency (sort of elevated home latency too but much higher world) combined with lag spikes. Not sure what the deal is, donāt seem to be having internet issues in other games.
|------------------------------------------------------------------------------------------|
| WinMTR statistics |
| Host - % | Sent | Recv | Best | Avrg | Wrst | Last |
As with others above, you have a nearly 4 second latency spike on your modem/router. It continues throughout.
if you look at the wintmtr 2 above yours, it looks more like we expect a functioning connection to look at that hop -
In your case, things seem to start right off the bat at the modem/router. Can you powercycle, and have the ISP check the router? If wireless, can you change bands? Is firmware up to date? Network drivers are up to date?
In Zaarmās case, there isnāt a clear change until the first level3 hop, when he gets packet loss (1%) and an average latency chance from 4 ms to 201 ms.
Realistically, the scope is simple. Anyone playing your game and routing through BLIZZARD-EN.ear7.Chicago2.Level3.net is experiencing latency.
These are the facts (based on my own experience):
This is not an intermittent problem and Iāve had issues for over 2 months now. It began as 10-15 minutes of latency and has morphed into hours of 300+ ms.
High latency occurs every night starting between 7pm-8pm CST on BLIZZARD-EN.ear7.Chicago2.Level3.net.
We had (a few?) nights where Centurylink was routing traffic through LA and had latency on ae1-br01-eqla1.as57976.net - one hop past BLIZZARD-EN.ear3.LosAngeles1.Level3.net.
Iām at a point where I log in twice a week on Tues/Weds for raids and in order to play optimally, I have to pay for a VPN service.
Is this actively being worked on?
Does Centurylink know what is causing the latency?
If yes, is there an ETA for a fix?
If no, why not? This thread has multiple examples and it has been proven, night after night, that latency begins to spike between 7pm-8pm CST. I would like to think Centurylink is more than capable of diagnosing the issue and identifying the root cause.
Everyone in this thread is frustrated. I appreciate the updates from Blizzard but this has been going on for far too long.
What are you even talking about, it doesnāt start at the Router - the 349 is packets sent and received. Average ping is between 4 to 7 before the āNo Response from Hostā.