Raid time again and yet another spike in latency for another week. Started when I logged in 3 mins ago.
Man, this is almost unplayable for WPVP…
WinMTR StatisticsWinMTR statistics
Host | % | Sent | Recv | Best | Avrg | Wrst | Last |
modem.Home | 0 | 196 | 196 | 0 | 0 | 3 | 0 |
phn4-dsl-gw03.phn4.qwest.net | 0 | 196 | 196 | 14 | 20 | 78 | 18 |
phn4-agw1.inet.qwest.net | 0 | 196 | 196 | 15 | 22 | 93 | 18 |
209.181.128.2 | 2 | 185 | 182 | 15 | 60 | 934 | 18 |
No response from host | 100 | 39 | 0 | 0 | 0 | 0 | 0 |
BLIZZARD-EN.ear3.LosAngeles1.Level3.net | 0 | 196 | 196 | 25 | 33 | 183 | 25 |
ae1-br01-eqla1.as57976.net | 2 | 188 | 186 | 213 | 259 | 477 | 240 |
et-0-0-2-br01-swlv10.as57976.net | 2 | 188 | 186 | 205 | 252 | 310 | 246 |
137.221.65.133 | 0 | 196 | 196 | 222 | 273 | 1103 | 251 |
be1-pe2-eqch2.as57976.net | 0 | 196 | 196 | 226 | 251 | 296 | 250 |
24.105.62.129 | 0 | 196 | 196 | 227 | 251 | 297 | 251 |
and a few minutes later, it gets worse…
WinMTR StatisticsWinMTR statistics
Host | % | Sent | Recv | Best | Avrg | Wrst | Last |
modem.Home | 0 | 423 | 423 | 0 | 0 | 5 | 2 |
phn4-dsl-gw03.phn4.qwest.net | 0 | 423 | 423 | 14 | 19 | 78 | 15 |
phn4-agw1.inet.qwest.net | 0 | 423 | 423 | 14 | 21 | 93 | 31 |
209.181.128.2 | 5 | 352 | 335 | 15 | 49 | 934 | 19 |
No response from host | 100 | 84 | 0 | 0 | 0 | 0 | 0 |
BLIZZARD-EN.ear3.LosAngeles1.Level3.net | 0 | 423 | 423 | 25 | 32 | 183 | 31 |
ae1-br01-eqla1.as57976.net | 1 | 415 | 413 | 200 | 256 | 724 | 369 |
et-0-0-2-br01-swlv10.as57976.net | 1 | 415 | 413 | 198 | 246 | 315 | 239 |
137.221.65.133 | 1 | 417 | 416 | 203 | 285 | 2251 | 247 |
be1-pe2-eqch2.as57976.net | 0 | 423 | 423 | 201 | 245 | 296 | 261 |
24.105.62.129 | 0 | 423 | 423 | 200 | 246 | 297 | 258 |
Same deal again, only change was a dip for about 15-20 minutes at about 7:45. Bad hop did change to the Hop after Level3 with the change from Chicago to LA
| WinMTR statistics |
| Host - % | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
| Local - 0 | 3061 | 3061 | 0 | 0 | 9 | 0 |
| rb4-bras.wnvl.centurytel .net - 1 | 3023 | 3013 | 1 | 8 | 215 | 4 |
| clma-agw1.inet.qwest .net - 1 | 3027 | 3018 | 2 | 10 | 178 | 9 |
| dvr3-brdr-01.inet.qwest .net - 1 | 3023 | 3013 | 15 | 24 | 227 | 19 |
| No response from host - 100 | 612 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 612 | 0 | 0 | 0 | 0 | 0 |
| BLIZZARD-EN.ear3.LosAngeles1.Level3 .net - 1 | 3031 | 3023 | 45 | 56 | 329 | 51 |
| ae1-br01-eqla1.as57976 .net - 1 | 2949 | 2921 | 90 | 237 | 1529 | 226 |
| et-0-0-2-br01-swlv10.as57976 .net - 2 | 2928 | 2894 | 88 | 230 | 1180 | 233 |
| 137.221.65.133 - 1 | 2979 | 2960 | 89 | 250 | 2498 | 241 |
| be1-pe2-eqch2.as57976 .net - 2 | 2939 | 2908 | 88 | 225 | 464 | 227 |
| 24.105.62.129 - 2 | 2919 | 2883 | 89 | 227 | 529 | 232 |
Same issue still occurring but it appears the route was slightly changed
5 21 ms 21 ms 21 ms 63-235-41-90.dia.static.qwest. net
6 * * * Request timed out.
7 50 ms 50 ms 50 ms BLIZZARD-EN.ear3.LosAngeles1.Level3. net [4.71.135.106]
8 271 ms 301 ms 234 ms ae1-br01-eqla1.as57976. net [137.221.68.33]
9 236 ms 237 ms 239 ms et-0-0-2-br01-swlv10.as57976. net [137.221.65.69]
10 233 ms 233 ms 248 ms 137.221.65.133
11 237 ms 219 ms 215 ms be1-pe2-eqch2.as57976. net [137.221.69.69]
12 220 ms 231 ms 224 ms chi-eqch2-ia-bons-04.as57976. net [137.221.66.15]
13 224 ms 229 ms 237 ms 24.105.62.129
Was doing fine earlier, but started going up like an hour ago.
|------------------------------------------------------------------------------------------|
| WinMTR statistics |
| Host - % | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
| PK5001Z.PK5001Z - 0 | 228 | 228 | 1 | 14 | 97 | 7 |
| stpl-dsl-gw12.stpl.qwest.net - 1 | 224 | 223 | 19 | 38 | 112 | 69 |
| stpl-agw1.inet.qwest.net - 1 | 224 | 223 | 19 | 42 | 101 | 52 |
| 216-160-19-2.mpls.qwest.net - 1 | 224 | 223 | 20 | 39 | 114 | 50 |
| No response from host - 100 | 46 | 0 | 0 | 0 | 0 | 0 |
| BLIZZARD-EN.ear3.LosAngeles1.Level3.net - 0 | 228 | 228 | 68 | 94 | 273 | 94 |
| ae1-br01-eqla1.as57976.net - 0 | 228 | 228 | 215 | 274 | 461 | 295 |
| et-0-0-2-br01-swlv10.as57976.net - 1 | 220 | 218 | 216 | 265 | 343 | 310 |
| 137.221.65.133 - 1 | 224 | 223 | 214 | 288 | 1092 | 270 |
| be1-pe1-eqch2.as57976.net - 0 | 228 | 228 | 212 | 268 | 377 | 277 |
| chi-eqch2-ia-bons-02.as57976.net - 1 | 224 | 223 | 221 | 268 | 334 | 323 |
| 24.105.62.129 - 1 | 221 | 219 | 219 | 270 | 352 | 266 |
|________________________________________________|______|______|______|______|______|______|
WinMTR v0.92 GPL V2 by Appnor MSP - Fully Managed Hosting & Cloud Provider
I waited until tonight to post this as I wanted to be sure it would improve or remedy the latency. Also wanted a baseline with the new network changes (Rerouting through LA vice Chicago):
TLDR: Enabling and using IPv6 improves latency.
My Latencies:
Normal: 13ms
Evening (IPv4): 220ms
Evening (IPv6): 60ms
This is a 4 step process, every step must be complete before you will see results. If any step is not performed you will continue to connect using IPv4 and not see any change. Remove spaces in below referenced URLS.
NOTE: If you are not comfortable making these changes please contact CenturyLink support. I’m not responsible for you breaking your internet connection.
-
Enable IPv6 on your CenturyLink router:
URL: https:// www.centurylink .com/home/help/internet/modems-and-routers/zyxel-c3000z/enable-ipv6.html
Note: By default IPv6 is Disabled on your router however, CenturyLink’s network does support IPv6 in some but not all areas. If you have a different model modem, please search for the appropriate steps to enable IPv6 on your specific model.
Note: Your router will reboot after changes are made and you will loose internet connectivity briefly. -
Enable IPv6 on your Gaming Machine’s Network Configuration:
MAC: https:// support.apple .com/guide/mac-help/use-ipv6-on-mac-mchlp2499/mac
Windows: https:// support.microsoft .com/en-us/help/929852/guidance-for-configuring-ipv6-in-windows-for-advanced-usersNote: I used “Configure IPv6” set to “Automatically” on my iMac.
-
Turn Off and Turn On your Gaming Machine’s Network Interface:
Note: This will allow the Network Interface Card (NIC) to reset and grab an IPv6 address. If you dont know how to do this step in Settings you may simply reboot your Gaming Machine.
-
Test to ensure your Router and Gaming Machine are configured correctly for IPv6:
URL: https:// ipv6-test .com/
Note: You should see an IPv4 & IPv6 address listed and a green “Supported” box. If no IPv6 address is shown, either an above step was not performed or your CenturyLink Modem or CenturyLink Service Area do not support IPv6.
-
Enable IPV6 on WoW Network Settings:
In the WoW client goto: System >> Network >> Enable IPv6 when available.
Hope this helps until the underlying issue is resolved. Cheers!
Thank you, everyone, for the new tests! Our network team is continuing to monitor reports and this has been relayed!
Thank you for your patience on this. It’s a frustrating situation, especially for those with raids tonight. Hopefully, we’ll have more information to share soon. In the mean time, while it’s not supported, a VPN or hotspot should workaround the issue if this may be an alternative available.
[Edit] Thanks for sharing this, Bins! Anyone else tried this and having success with this?
The longer i have been on the worse it gets
WinMTR StatisticsWinMTR statistics
Host | % | Sent | Recv | Best | Avrg | Wrst | Last |
modem.Home | 0 | 2914 | 2914 | 0 | 0 | 6 | 0 |
phn4-dsl-gw03.phn4.qwest.net | 1 | 2910 | 2909 | 14 | 18 | 93 | 15 |
phn4-agw1.inet.qwest.net | 0 | 2914 | 2914 | 14 | 22 | 101 | 34 |
209.181.128.2 | 15 | 1842 | 1573 | 15 | 45 | 934 | 16 |
No response from host | 100 | 583 | 0 | 0 | 0 | 0 | 0 |
BLIZZARD-EN.ear3.LosAngeles1.Level3.net | 0 | 2914 | 2914 | 24 | 31 | 308 | 27 |
ae1-br01-eqla1.as57976.net | 1 | 2836 | 2816 | 189 | 267 | 1332 | 259 |
et-0-0-2-br01-swlv10.as57976.net | 1 | 2811 | 2787 | 198 | 266 | 4598 | 250 |
137.221.65.133 | 1 | 2784 | 2759 | 203 | 312 | 4748 | 250 |
be1-pe2-eqch2.as57976.net | 1 | 2840 | 2821 | 194 | 253 | 296 | 263 |
24.105.62.129 | 1 | 2845 | 2827 | 200 | 254 | 297 | 252 |
I’m a CenturyLink customer and have been having the exact same problem. When I connect to a vpn, my latency is fine, but otherwise im sitting at 400 ms
Just did this, can confirm it helps. Went from 800ms to 53ms.
TY
Very nice improvement there, glad its helping!
I also just switched to ipv6 and it 100% fixed the issue. Went from 275ms to 61ms
WinMTR statistics
Host | % | Sent | Recv | Best | Avrg | Wrst | Last |
192.168.0.1 | 0 | 6265 | 6265 | 0 | 0 | 22 | 0 |
184-96-48-254.hlrn.qwest.net | 0 | 6265 | 6265 | 1 | 6 | 100 | 12 |
63-225-124-105.hlrn.qwest.net | 0 | 6265 | 6265 | 1 | 5 | 61 | 4 |
dvr3-brdr-01.inet.qwest.net | 1 | 6261 | 6260 | 1 | 5 | 69 | 18 |
63-235-41-90.dia.static.qwest.net | 1 | 6259 | 6258 | 2 | 5 | 3435 | 4 |
No response from host | 100 | 1255 | 0 | 0 | 0 | 0 | 0 |
BLIZZARD-EN.ear3.LosAngeles1.Level3.net | 0 | 6265 | 6265 | 30 | 36 | 336 | 34 |
ae1-br01-eqla1.as57976.net | 1 | 6188 | 6168 | 50 | 240 | 1342 | 68 |
et-0-0-2-br01-swlv10.as57976.net | 1 | 6149 | 6122 | 50 | 238 | 3072 | 74 |
137.221.65.133 | 1 | 6125 | 6100 | 50 | 269 | 4739 | 88 |
be1-pe1-eqch2.as57976.net | 1 | 6191 | 6172 | 50 | 229 | 277 | 74 |
24.105.62.129 | 1 | 6181 | 6159 | 51 | 230 | 277 | 72 |
The issue was just as bad as ever tonight, however normally during the non spike times I average 25ms, today I was at 50ms the entire day. I spiked up to 400ms during MC tonight.
Yea I went ahead any got a vpn Network seems like there Is not E.T.A. on this issue any time soon, this has been on going for the last 3 Ish weeks happens every time during raid hrs It goes up for an Hr and half then goes back down after raid and returns to normal extremely frustrating been just trying to fight through It and deal with It but can not take It anymore so went with the vpn network for now.
Hey all,
I’m seeing some pretty good improvements on our internal reporting. How are things looking for y’all?
Let us know. Thanks!
Honestly haven’t checked, I had to buy a VPN to actually raid and I’m having issues with that sometimes with lag aswell.
Just logged in and its already bad, which is new. Latency was up while at the Great Seal, which it normally was only an issue with latency in raid at night for me after 7est. Not looking like I will be able to do mythic progression with my team AGAIN tonight. 143ms home and 287ms world. Normal is 65-70 home and 55-72ms world. Multiple bnet updates but none for the better. I was shocked latency was so high already today which is why I stopped by the forum.
Recommend trying the steps I posted yesterday enabling IPv6. Many people who have done the changes have seen dramatic results.
Running a winMTR right now and it is dropping at the LA peering node.
will that mess with others who use the internet in my house?