My VPN seemed to clear thing sup and make it playable while also streaming to twitch and discord.
Wow is literally the only game/service I am having problems with. Cableone Mississippi.
1 Like
Another weird issue. Since this started happening, I can use the Wow forums just fine but I can’t open forums on Bnet or Hearthstone. Tried both in Chrome and Explorer and I am seeing the same thing. The browser sees the address but then just sits there and lags out trying to open the page.
3 Likes
I’m looking into it. It’s causing me grief as well. And when I made sure inbound to me didn’t come though Dallas now I have no idea where Bliz is sending traffic back to me but Hurricane is picking it up in Frankfurt sending it to Paris and back… So now I have a two fronted issue.
I’m getting ready to make some phone calls, I’m just getting my ducks lined up.
2 Likes
I’m surprised we haven’t had an update in 18 hours… The game is totally unplayable and has been for a week now. Not sure why i’m still paying for it.
7 Likes
Same here. Only a VPN/static IP allows me on Bnet related pages.
1 Like
I’m Nextlink in Benbrook, so I feel your pain. I called them and they are aware of it but it’s out of their hands they said…
1 Like
I’m reading folks are using VPNs to get around this. Does anyone have any recommendations for VPNs to use?
2 Likes
I would also like to know if anyone has any recommendations for VPNs. Also, just FYI, the @BlizzardCS twitter seems to be telling everyone to try a VPN as a fix for anyone reporting similar lag spike issues.
1 Like
Well they are wrong. VPN does not fix it for me and several people I know. It makes it SLIGHTLY better out of peak hours, and allows access to bnet pages, that’s it. Private internet access is what we use. Not the fastest out there, there are gaming ones, but relatively cheap and reliable.
1 Like
Same thing is going on for me. I’m in Mississippi and I have Cable One as my ISP. It’s been going on for about 2 weeks now. It started as stuttering and minor lag, but now the game is almost unplayable.
4 Likes
PIA works fine for me, are you using the “Connect Auto” function? Because that will connect you to their Texas exit node if you’re in Texas, instead you want to select “Connect to ->” then Las Vegas, Seattle, Chicago, etc - anywhere outside the south
1 Like
I use NordVPN and it has worked over the past few days. Just selecting some other location in the U.S. seems to keep it steady around 80/80 instead of 50/4500 lol
1 Like
Of course. I have tried every node. Chicago, Vegas etc. It stops the 14,000 ping spikes but it still stays from 150 to 500 and has those stalls like the cable has been unplugged for 5-10 seconds. During the early morning it works fine, but in peak hours, even with VPN, it is useless.
3 Likes
Hudson Oaks TX, unplayable for a week.
4 Likes
The connection is so slow, blue hasn’t even seen all these posts yet. Only explanation as to the lack of response.
3 Likes
Huh, I’m just outside Austin and get a steady 60ms to 70ms world using the Denver node which is the best I’ve found, clears up the rubberbanding and spikes nicely. I’m with Grande Comm though so I guess you’d have a slightly different routing
1 Like
3 Likes
TRACEROUTE:
traceroute to 52.128.56.140 (52.128.56.140), 15 hops max, 60 byte packets
1 Blizzard Blizzard 0.291 ms 0.272 ms 0.270 ms Blizzard(24.105.18.2) 0.577 ms 0.637 ms 0.759 ms
3 137.221.105.10 (137.221.105.10) 0.571 ms 0.628 ms 0.736 ms
4 137.221.66.16 (137.221.66.16) 9.922 ms 9.928 ms 10.004 ms
5 137.221.83.70 (137.221.83.70) 25.757 ms 25.760 ms 25.759 ms
6 137.221.65.66 (137.221.65.66) 25.601 ms 25.554 ms 25.526 ms
7 137.221.74.32 (137.221.74.32) 25.488 ms * 25.324 ms
8 eqix-da1. nextlinkbroadband-2. com (206.223.118.192) 25.696 ms 25.709 ms 25.802 ms
9 * * *
10 * * *
11 * * *
12 * * *
13 * * *
14 * * *
15 * * *
07/12/2018 21:04:10 UTC
PING:
PING 52.128.56.140 (52.128.56.140) 56(84) bytes of data.
— 52.128.56.140 ping statistics —
4 packets transmitted, 0 received, 100% packet loss, time 2998ms
07/12/2018 21:04:10 UTC
MTR:
Start: Fri Dec 7 21:04:10 2018 Blizzard 1.|-- Blizzard 0.0% 10 0.4 0.3 0.2 0.4 0.0
2.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0
07/12/2018 21:04:10 UTC
1 Like
TRACEROUTE:
traceroute to 52.128.56.140 (52.128.56.140), 15 hops max, 60 byte packets
1 Blizzard Blizzard 0.511 ms 0.505 ms 0.506 ms Blizzard(24.105.18.2) 0.772 ms 1.017 ms 1.038 ms
3 137.221.105.10 (137.221.105.10) 0.720 ms 1.021 ms 1.028 ms
4 137.221.66.16 (137.221.66.16) 1.216 ms 1.242 ms 1.243 ms
5 137.221.83.70 (137.221.83.70) 34.365 ms 34.386 ms 34.395 ms
6 137.221.65.66 (137.221.65.66) 25.753 ms 31.468 ms 31.443 ms
7 137.221.74.32 (137.221.74.32) 31.578 ms 31.579 ms 31.119 ms
8 eqix-da1.nextlinkbroadband-2. com (206.223.118.192) 30.898 ms 30.886 ms *
9 * * *
10 * * *
11 * * *
12 * * *
13 * * *
14 * * *
15 * * *
07/12/2018 21:07:05 UTC
TRACEROUTE:
traceroute to 52.128.56.140 (52.128.56.140), 15 hops max, 60 byte packets
1 Blizzard Blizzard 0.369 ms 0.362 ms 0.363 ms Blizzard(24.105.18.2) 0.743 ms 0.877 ms 0.961 ms
3 137.221.105.10 (137.221.105.10) 0.719 ms 0.843 ms 0.893 ms
4 137.221.66.16 (137.221.66.16) 0.679 ms 0.856 ms 0.873 ms
5 137.221.83.70 (137.221.83.70) 25.832 ms 25.835 ms 25.837 ms
6 137.221.65.66 (137.221.65.66) 25.780 ms 25.735 ms 25.711 ms
7 137.221.74.32 (137.221.74.32) 25.502 ms 25.515 ms 25.588 ms
8 eqix-da1.nextlinkbroadband-2. com (206.223.118.192) 26.034 ms 26.030 ms 26.025 ms
9 * * *
10 * * *
11 * * *
12 * * *
13 * * *
14 * * *
15 * * *
07/12/2018 21:07:05 UTC
PING:
PING 52.128.56.140 (52.128.56.140) 56(84) bytes of data.
— 52.128.56.140 ping statistics —
4 packets transmitted, 0 received, 100% packet loss, time 2998ms
07/12/2018 21:07:05 UTC
PING:
PING 52.128.56.140 (52.128.56.140) 56(84) bytes of data.
— 52.128.56.140 ping statistics —
4 packets transmitted, 0 received, 100% packet loss, time 3008ms
07/12/2018 21:07:05 UTC
TRACEROUTE:
traceroute to 52.128.56.140 (52.128.56.140), 15 hops max, 60 byte packets
1 Blizzard Blizzard 0.262 ms 0.300 ms 0.317 ms Blizzard(24.105.18.2) 1.078 ms 1.193 ms 1.299 ms
3 137.221.105.10 (137.221.105.10) 1.204 ms 1.306 ms 1.320 ms
4 137.221.66.16 (137.221.66.16) 1.147 ms 1.232 ms 1.248 ms
5 137.221.83.70 (137.221.83.70) 44.606 ms 44.662 ms 44.693 ms
6 137.221.65.66 (137.221.65.66) 25.625 ms 61.085 ms 61.134 ms
7 137.221.74.32 (137.221.74.32) 25.552 ms 25.634 ms 25.671 ms
8 eqix-da1.nextlinkbroadband-2. com (206.223.118.192) 25.922 ms 26.009 ms 26.025 ms
9 * * *
10 * * *
11 * * *
12 * * *
13 * * *
14 * * *
15 * * *
07/12/2018 21:07:09 UTC
PING:
PING 52.128.56.140 (52.128.56.140) 56(84) bytes of data.
— 52.128.56.140 ping statistics —
4 packets transmitted, 0 received, 100% packet loss, time 3005ms
07/12/2018 21:07:10 UTC
TRACEROUTE:
traceroute to 52.128.56.140 (52.128.56.140), 15 hops max, 60 byte packets
1 Blizzard Blizzard 0.306 ms 0.293 ms 0.305 ms Blizzard(24.105.18.2) 0.850 ms 0.927 ms 1.111 ms
3 137.221.105.10 (137.221.105.10) 0.529 ms 0.666 ms 0.698 ms
4 137.221.66.16 (137.221.66.16) 0.859 ms 0.872 ms 0.883 ms
5 137.221.83.70 (137.221.83.70) 25.725 ms 25.761 ms 25.772 ms
6 137.221.65.66 (137.221.65.66) 25.524 ms 25.812 ms 25.797 ms
7 137.221.74.32 (137.221.74.32) 25.487 ms 25.806 ms 25.804 ms
8 * eqix-da1.nextlinkbroadband-2. com (206.223.118.192) 25.897 ms 25.941 ms
9 * * *
10 * * *
11 * * *
12 * * *
13 * * *
14 * * *
15 * * *
07/12/2018 21:07:13 UTC
PING:
PING 52.128.56.140 (52.128.56.140) 56(84) bytes of data.
— 52.128.56.140 ping statistics —
4 packets transmitted, 0 received, 100% packet loss, time 2998ms
07/12/2018 21:07:15 UTC
MTR:
Start: Fri Dec 7 21:07:05 2018 Blizzard 1.|-- Blizzard 0.0% 10 0.5 0.5 0.3 1.1 0.0 Blizzard 0.0% 10 0.8 0.7 0.5 1.1 0.0
3.|-- 137.221.105.10 0.0% 10 0.8 0.8 0.6 0.9 0.0
4.|-- 137.221.66.16 0.0% 10 0.9 0.7 0.5 0.9 0.0
5.|-- 137.221.83.70 0.0% 10 25.8 25.7 25.5 25.9 0.0
6.|-- 137.221.65.66 0.0% 10 25.9 25.7 25.5 26.0 0.0
7.|-- 137.221.74.32 20.0% 10 26.5 25.9 25.5 26.5 0.0
8.|-- eqix-da1.nextlinkbroadband-2. com 10.0% 10 26.1 26.0 25.5 27.8 0.5
9.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0
07/12/2018 21:07:05 UTC
MTR:
Start: Fri Dec 7 21:07:05 2018 Blizzard 1.|-- Blizzard 0.0% 10 0.4 0.4 0.3 0.5 0.0 Blizzard 0.0% 10 0.6 0.7 0.6 1.0 0.0
3.|-- 137.221.105.10 0.0% 10 0.7 0.7 0.5 1.0 0.0
4.|-- 137.221.66.16 0.0% 10 0.8 0.7 0.6 0.8 0.0
5.|-- 137.221.83.70 0.0% 10 25.6 29.5 25.5 54.1 8.9
6.|-- 137.221.65.66 0.0% 10 25.9 25.8 25.6 26.0 0.0
7.|-- 137.221.74.32 10.0% 10 25.9 25.6 25.4 25.9 0.0
8.|-- eqix-da1.nextlinkbroadband-2. com 10.0% 10 25.8 25.9 25.6 26.7 0.0
9.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0
07/12/2018 21:07:05 UTC
MTR:
Start: Fri Dec 7 21:07:09 2018 Blizzard 1.|-- Blizzard 0.0% 10 0.4 0.3 0.2 0.5 0.0 Blizzard 0.0% 10 0.6 0.7 0.5 1.0 0.0
3.|-- 137.221.105.10 0.0% 10 0.6 0.6 0.5 0.8 0.0
4.|-- 137.221.66.16 0.0% 10 0.7 1.0 0.6 4.2 0.9
5.|-- 137.221.83.70 0.0% 10 25.8 34.6 25.6 92.0 20.7
6.|-- 137.221.65.66 0.0% 10 25.5 35.0 25.5 119.3 29.6
7.|-- 137.221.74.32 0.0% 10 27.0 25.8 25.3 27.0 0.5
8.|-- eqix-da1.nextlinkbroadband-2. com 0.0% 10 25.8 25.9 25.7 26.8 0.0
9.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0
07/12/2018 21:07:09 UTC
MTR:
Start: Fri Dec 7 21:07:10 2018 Blizzard 1.|-- Blizzard 0.0% 10 0.3 0.5 0.3 1.3 0.0 Blizzard 0.0% 10 0.8 0.7 0.5 1.0 0.0
3.|-- 137.221.105.10 0.0% 10 0.6 0.8 0.6 1.2 0.0
4.|-- 137.221.66.16 0.0% 10 0.7 0.7 0.5 0.9 0.0
5.|-- 137.221.83.70 0.0% 10 32.4 30.8 25.7 60.9 10.9
6.|-- 137.221.65.66 0.0% 10 25.7 26.0 25.5 26.9 0.0
7.|-- 137.221.74.32 20.0% 10 25.5 25.6 25.4 25.8 0.0
8.|-- eqix-da1.nextlinkbroadband-2. com 10.0% 10 25.7 25.8 25.6 26.0 0.0
9.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0
07/12/2018 21:07:10 UTC
1 Like
Same, Cableone Mississippi. Unplayable.
I would also like to add that the latency will “settle” then as soon as anything remotely intense happens - bam 21,000ms … yeah… 5,000ms is now small fries. It goes that high. I’ve seen it.
The WinMTRs repeatedly show Dallas or something with the name “Dallas” being a monstrous hiccup in latency, but not the to point of DC, just 21,000ms.
2 Likes