Thanks for all the help. I hope you guys can get it to work.
Thank you for keeping us updated on this.
I’m with CableOne too like others I’m seeing(what a club…), and VPN is working for me too. Ranges between 60-90ms but seems way more stable at least.
1 Like
Well… can not raid… fine in the world… in a instance or raid… forget it
12k plus latency
But hey… can look at forums just fine…
Must be my end…
1 Like
Made sure all devices and O/S were current with patches. Restarted modem, router, and system. Works fine on OTHER games (you know PoE and those), but when you go into a Warfront or Raid, forget it. The latency gets exponentially worse about every 30 seconds or so, like there’s a loop or issue connecting with the instance server. On a 1 Gb connection with a SSD drive. As stated earlier, I have NO ISSUES with other games.
Someone correct me if I am wrong but:
bad ping caused by bad hopps/bad internet nodes/etc. can be resolved by changing your DNS. I typically use 3.: one provided automatically by my ISP (that is usually my worst connection). 2.: google DNS (8.8.8.8). 3.: cloudflare DNS (1.1.1.1).
At first it seemed like a pain to change as you have to select your ethernet connection, choose properties, select the ipv4 item and once again select properties and then change to the DNS address that you want to try. You can google for the instructions. But once you have done it a few times it is really easy.
I also use a program to rese/wipe the old DNS table (I use minitoolbox) so the new one is used. some times when I have connection issues I just use minitoolbox to just reset the DNS without even changing DNS servers.
In my mind all this has the effect of changing the route of your internet traffic to the game servers. Well not always since it is certanly possible that the new DNS table will use the same bad hop as the old one but in that case I just try another DNS server.
Perhaps some one here could explaine this better. I’m not a computer guy.
I don’t see how changing your DNS will change how your traffic is routed by your ISP. DNS is simply just an domain lookup services that translates domain names to IP addresses.
Well its been lag-dallas.1 or whatever for my MTR tests and I’d hate to have to find another online game to play, because they all work perfectly.
I just bought BFA and two months subscription, now because of random bad connection that magically changed only for WoW, I’m out 100 dollars. Sigh.
1 Like
Same issues here, however my ISP is bluestream
blue stream here in florida here too, someone else on here too and we’re having problems. you are not alone
1 Like
Also Blue Stream South Florida. Same issues, plus see my recent thread about no shop/hearthstone access
1 Like
Good to see I’m not the only one having this problem, have any of you tried contacting them to see if this issue can be solved? I’m tired of having 3000+ world ping in instances
1 Like
guess i just can’t play WoW? i literally lag in every battleground until my character is running in place… I can’t do dungeons or raids… amazing. I’m out of Richmond Texas by the way if this helps at all… if you need more info to help fix this process please ask.
Okay what do i do when they just say its not there issue, so you need to contact the game manufacturer? I am getting now where and this go talk to level 3 crap when it is obliviously something to do with that last patch you sent out. This is a some serious BS Blizz…
Also having this issue.
CableOne - Western Oklahoma
(FWIW I have tried using my TMobile phone as a hotspot and get similar results - higher lag after entering Dallas1.Level3)
Looking Glass results -
TRACEROUTE:
traceroute to 67.61.250.41 (67.61.250.41), 15 hops max, 60 byte packets
1 Blizzard Blizzard 0.307 ms 0.299 ms 0.300 ms Blizzard(24.105.18.2) 0.560 ms 0.611 ms 0.800 ms
3 137.221.105.10 (137.221.105.10) 0.583 ms 0.633 ms 0.770 ms
4 137.221.66.20 (137.221.66.20) 0.581 ms 0.585 ms 0.676 ms
5 * 137.221.83.72 (137.221.83.72) 26.040 ms 26.047 ms
6 137.221.65.66 (137.221.65.66) 25.572 ms 26.493 ms 26.469 ms
7 137.221.74.32 (137.221.74.32) 25.381 ms 25.930 ms 25.950 ms
8 * * *
9 * * *
10 * * *
11 * * *
12 * * *
13 * * *
14 * * *
15 * * *
09/12/2018 02:45:33 UTC
TRACEROUTE:
traceroute to 67.61.250.41 (67.61.250.41), 15 hops max, 60 byte packets
1 Blizzard Blizzard 1.570 ms 1.560 ms 1.550 ms Blizzard(24.105.18.2) 1.899 ms 2.005 ms 2.043 ms
3 137.221.105.10 (137.221.105.10) 1.944 ms 1.978 ms 2.027 ms
4 137.221.66.20 (137.221.66.20) 1.929 ms 1.936 ms 1.982 ms
5 * 137.221.83.72 (137.221.83.72) 26.893 ms *
6 137.221.65.66 (137.221.65.66) 26.918 ms 26.183 ms 45.192 ms
7 137.221.74.32 (137.221.74.32) 25.947 ms 25.625 ms 25.741 ms
8 * * *
9 * * *
10 * * *
11 * * *
12 * * *
13 * * *
14 * * *
15 * * *
09/12/2018 02:45:33 UTC
PING:
PING 67.61.250.41 (67.61.250.41) 56(84) bytes of data.
— 67.61.250.41 ping statistics —
4 packets transmitted, 0 received, 100% packet loss, time 2998ms
09/12/2018 02:45:33 UTC
PING:
PING 67.61.250.41 (67.61.250.41) 56(84) bytes of data.
— 67.61.250.41 ping statistics —
4 packets transmitted, 0 received, 100% packet loss, time 3000ms
09/12/2018 02:45:33 UTC
TRACEROUTE:
traceroute to 67.61.250.41 (67.61.250.41), 15 hops max, 60 byte packets
1 Blizzard Blizzard 0.242 ms 0.246 ms 0.257 ms Blizzard(24.105.18.2) 0.501 ms 0.737 ms 0.793 ms
3 137.221.105.10 (137.221.105.10) 0.699 ms 0.798 ms 1.113 ms
4 137.221.66.20 (137.221.66.20) 0.728 ms 0.738 ms 0.748 ms
5 137.221.83.72 (137.221.83.72) 25.712 ms 25.742 ms 25.752 ms
6 137.221.65.66 (137.221.65.66) 25.527 ms 25.776 ms 25.762 ms
7 137.221.74.32 (137.221.74.32) 25.452 ms 25.519 ms 25.523 ms
8 * * *
9 * * *
10 * * *
11 * * *
12 * * *
13 * * *
14 * * *
15 * * *
09/12/2018 02:45:38 UTC
PING:
PING 67.61.250.41 (67.61.250.41) 56(84) bytes of data.
— 67.61.250.41 ping statistics —
4 packets transmitted, 0 received, 100% packet loss, time 3002ms
09/12/2018 02:45:38 UTC
TRACEROUTE:
traceroute to 67.61.250.41 (67.61.250.41), 15 hops max, 60 byte packets
1 Blizzard Blizzard 0.335 ms 0.340 ms 0.346 ms Blizzard(24.105.18.2) 1.394 ms 1.470 ms 1.528 ms
3 137.221.105.10 (137.221.105.10) 1.426 ms 1.446 ms 1.463 ms
4 137.221.66.20 (137.221.66.20) 1.425 ms 1.450 ms 1.455 ms
5 137.221.83.72 (137.221.83.72) 26.043 ms 26.070 ms 26.078 ms
6 137.221.65.66 (137.221.65.66) 25.625 ms 25.584 ms 25.581 ms
7 137.221.74.32 (137.221.74.32) 25.311 ms 25.509 ms 25.512 ms
8 * * *
9 * * *
10 * * *
11 * * *
12 * * *
13 * * *
14 * * *
15 * * *
09/12/2018 02:45:42 UTC
MTR:
Start: Sun Dec 9 02:45:33 2018 Blizzard 1.|-- Blizzard 0.0% 10 0.3 0.7 0.2 4.5 1.1 Blizzard 0.0% 10 6.8 1.4 0.5 6.8 1.9
3.|-- 137.221.105.10 0.0% 10 0.5 0.7 0.5 0.9 0.0
4.|-- 137.221.66.20 0.0% 10 0.6 0.8 0.6 1.5 0.0
5.|-- 137.221.83.72 0.0% 10 25.7 33.1 25.5 69.9 15.9
6.|-- 137.221.65.66 0.0% 10 25.9 25.8 25.6 26.1 0.0
7.|-- 137.221.74.32 0.0% 10 25.4 25.5 25.3 25.5 0.0
8.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0
09/12/2018 02:45:33 UTC
PING:
PING 67.61.250.41 (67.61.250.41) 56(84) bytes of data.
— 67.61.250.41 ping statistics —
4 packets transmitted, 0 received, 100% packet loss, time 3003ms
09/12/2018 02:45:44 UTC
MTR:
Start: Sun Dec 9 02:45:38 2018 Blizzard 1.|-- Blizzard 0.0% 10 0.3 0.3 0.2 0.3 0.0 Blizzard 0.0% 10 0.5 0.6 0.5 0.9 0.0
3.|-- 137.221.105.10 0.0% 10 0.6 0.6 0.5 0.7 0.0
4.|-- 137.221.66.20 0.0% 10 0.5 0.6 0.5 0.7 0.0
5.|-- 137.221.83.72 10.0% 10 25.6 28.4 25.6 50.5 8.3
6.|-- 137.221.65.66 0.0% 10 25.5 30.4 25.5 70.8 14.2
7.|-- 137.221.74.32 0.0% 10 25.4 25.6 25.3 26.2 0.0
8.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0
09/12/2018 02:45:37 UTC
MTR:
Start: Sun Dec 9 02:45:33 2018 Blizzard 1.|-- Blizzard 0.0% 10 0.3 0.4 0.3 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.8 0.8 0.5 0.9 0.0
4.|-- 137.221.66.20 0.0% 10 0.7 0.7 0.6 0.8 0.0
5.|-- 137.221.83.72 10.0% 10 25.8 28.7 25.6 52.6 8.9
6.|-- 137.221.65.66 0.0% 10 25.8 26.0 25.6 27.5 0.3
7.|-- 137.221.74.32 0.0% 10 25.5 25.5 25.4 25.7 0.0
8.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0
09/12/2018 02:45:33 UTC
MTR:
Start: Sun Dec 9 02:45:39 2018 Blizzard 1.|-- Blizzard 0.0% 10 0.2 0.3 0.2 0.3 0.0 Blizzard 0.0% 10 0.5 2.1 0.5 15.8 4.7
3.|-- 137.221.105.10 0.0% 10 0.6 0.6 0.5 0.7 0.0
4.|-- 137.221.66.20 0.0% 10 0.7 0.6 0.6 0.8 0.0
5.|-- 137.221.83.72 10.0% 10 25.6 25.7 25.6 26.2 0.0
6.|-- 137.221.65.66 0.0% 10 25.6 31.1 25.6 80.3 17.3
7.|-- 137.221.74.32 0.0% 10 26.0 25.5 25.4 26.0 0.0
8.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0
09/12/2018 02:45:38 UTC
|------------------------------------------------------------------------------------------|
| WinMTR statistics |
| Host - % | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
| 192.168.0.1 - 5 | 900 | 859 | 2 | 12 | 32 | 12 |
| 10.112.139.1 - 4 | 927 | 893 | 8 | 12 | 31 | 12 |
| 10.224.252.214 - 7 | 834 | 776 | 20 | 24 | 54 | 24 |
| lag-133.ear1.Dallas1.Level3. net - 11 | 648 | 579 | 21 | 637 | 4955 | 35 |
| No response from host - 100 | 213 | 0 | 0 | 0 | 0 | 0 |
| BLIZZARD-EN.ear3.Dallas1.Level3. net - 8 | 816 | 754 | 21 | 26 | 50 | 25 |
| ae1-br01-eqda6.as57976. net - 27 | 520 | 384 | 41 | 46 | 148 | 43 |
| et-0-0-4-br01-eqch2.as57976. net - 16 | 649 | 549 | 43 | 100 | 4371 | 46 |
| be1-pe01-eqch2.as57976. net - 27 | 515 | 377 | 41 | 45 | 63 | 43 |
| chi-eqch2-ia-bons-02.as57976. net - 50 | 358 | 181 | 47 | 51 | 63 | 50 |
| 24.105.62.129 - 7 | 844 | 789 | 0 | 45 | 84 | 50 |
|________________________________________________|______|______|______|______|______|______|
WinMTR v0.92 GPL V2 by Appnor MSP - Fully Managed Hosting & Cloud Provider
I’m curious, are you guys seeing issues in other Blizz games as well such as Hearthstone, Black Ops 4 and Destiny 2?
Update. After cancliing my sub, my latency seems to have been fixed
4 Likes
All i had to do was restart the game and mine was fixed. Was in Kings Rest and I spiked to 500ms + no idea why. Relogged and it was fixed.
[Edited by Blizzard] This thread has been inactive for some time. Please be mindful of resurrecting older threads. A new or more recent thread can be created to continue the discussion. Locking this thread.