ever since I patched today, my ping has been through the roof. Another thing that makes no sense to me is that I live in California and my ping on the western US server is usually 20ms. Today, it’s 180-200+ms and is almost unplayable 
. For some reason, it says my ping on central is 63ms which is lower than western! makes no sense. I tried scan and repair, and reinstalled the game, restarted my modem and router, updated windows, bios is up to date, flushed dns cache, ip release, ip renew, and the game still lags badly.
Howdy!
That is a sign there is a routing issue between your network and our servers, this could be ISP related due to a local area issue or another ISP down the line. I would recommend to run a WinMTR when this issue is at it’s worst for 10 minutes and post the results back here. Make sure the IP address you use is to the west server: 24.105.30.129
1 Like
Thank you for your response. I wonder if it’s a local area issue because it’s only happening on my windows 10 computer that’s connected via ethernet. The MacBook pro and imac I patched on are both getting the normal 20ms western us ping, but my wired ethernet pc is getting 180ms, the opposite of what you would expect. How would a patch affect only one computer on a network basis? I will try and run a winMTR test
Im having the same issue ! I’ve done all of that as well and cant seem to get rid of that insanely high ping . hopefully they hot fix that
It happened right after I downloaded the patch . the very next game it skyrocketed to over 200 ping
Here is a pastebin: https:// pastebin. com/GmiXJZ7A with the results of the WinMTR running for 5 minutes (remove spaces in URL - we should be able to include links lol). As the game started, the ping went front around 100 to 180 and fluxuated. Right before the patch it was around 20, I think the patch did something that messed it up. The only thing I can think of that caused it would be more people on since the patch came out, but that can’t be a thing because it’s only on the computer I have connected directly to the router, not the computers over wifi (the comps over wifi get 20ms and the comp connected over ethernet gets 180ms, that makes no sense to me lol).
sounds like we are having the exact problem . mines doing the exact same thing
How are you guys able to check your ping for the game? Ctrl+Alt+F no longer shows your ping.
Hi I am experiencing the same issue. you said post the WinMTR and that was posted so what is the result? what should we do? @Zuvykreee
facepalm I just deleted the post with it linked…
anyhow, you can link using the “`” key.
https://pastebin.com/GmiXJZ7A
Using the preformatted text option, you can directly put larger things into the post seamlessly also:
|------------------------------------------------------------------------------------------|
| WinMTR statistics |
| Host - % | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
| 192.168.1.1 - 0 | 593 | 593 | 0 | 0 | 12 | 0 |
| No response from host - 100 | 119 | 0 | 0 | 0 | 0 | 0 |
| 96-34-135-93.static.unas.mo.charter.com - 0 | 593 | 593 | 8 | 13 | 36 | 10 |
| crr01lnbhca-bue-290.lnbh.ca.charter.com - 0 | 593 | 593 | 9 | 13 | 36 | 10 |
|bbr01aldlmi-tge-0-0-0-3.aldl.mi.charter.com - 0 | 593 | 593 | 9 | 16 | 42 | 17 |
|bbr01ashbva-tge-0-1-0-1.ashb.va.charter.com - 0 | 593 | 593 | 10 | 15 | 35 | 13 |
| eqix-ix-la1.blizzard.com - 0 | 593 | 593 | 10 | 16 | 50 | 16 |
| ae1-br01-eqla1.as57976.net - 0 | 593 | 593 | 13 | 44 | 791 | 15 |
| be1-pe02-eqla1.as57976.net - 0 | 593 | 593 | 165 | 169 | 193 | 169 |
| 24.105.30.129 - 1 | 589 | 588 | 0 | 164 | 180 | 168 |
|________________________________________________|______|______|______|______|______|______|
WinMTR v0.92 GPL V2 by Appnor MSP - Fully Managed Hosting & Cloud ProviderSimilar issue with high ping after patch. I’m in eastcoast and getting connected to US Central with 130 ms ping. I usually get 20ms.
resolved for me today.
what did you do to fix it?
im still experiencing the same thing so if anyone has any ideas on how to fix it or more info if its on blizzards end ( which im pretty sure it is) , please let me know ! thank you !
I literally did nothing it just fixed itself. My ping went from 180ms to 15ms again.
Unreal lags and disconnects only with your bugged game
Thanks for the WinMTR! There isn’t a consistent trend with regions and ISPs, and we’re not seeing high spikes overall within the last 7 days, which may point to a specific peering node that each of the connections are running into or individual system and local network concerns.
Are you all still experiencing the high latency spikes? The reports died down 2 days ago. If so, let’s try the following:
- Reset the local network devices and flush the DNS
- Bypass the router, if you have a separate modem and router.
- Try a different connection or Virtual Private Network (VPN). This is not supported, but a VPN can help reroute the connection, while a different connection tackles both the local network and route. This can help isolate the problem.
@Dordi, the local network and connection is appearing normal, but near the end of the test, the latency spikes and there’s a 1% packet loss on the server.
If it continues, please provide us with a WinMTR test while running the game for 10-15 minutes while the latency spikes are occuring and let’s gather a Looking Glass test - For EU, looking glass test here.
Gathering more tests from everyone who is impacted gives us more data to check for comparisons, if there may be something our network team can look into.
FanHOTS here. I have the same problem. Played in HGC for 2 years with very consistent 15 ping to US West, live in Irvine next to blizz HQ, and after this most recent patch my ping to US West suddenly jumped to 170+
Hope a solution to this can be found. Here is my Looking Glass test taken during a game with 170 ping the entire time:
TRACEROUTE:
traceroute to 68.4.255.110 (68.4.255.110), 15 hops max, 60 byte packets
1 Blizzard Blizzard 0.291 ms 0.279 ms 0.281 ms
2 24.105.18.131 (24.105.18.131) 0.667 ms 1.013 ms 1.247 ms
3 137.221.105.12 (137.221.105.12) 0.722 ms 0.751 ms 0.806 ms
4 137.221.66.20 (137.221.66.20) 0.717 ms 0.729 ms 0.773 ms
5 137.221.83.68 (137.221.83.68) 6.893 ms 6.908 ms 6.910 ms
6 137.221.65.68 (137.221.65.68) 22.104 ms 19.780 ms 19.757 ms
7 137.221.68.32 (137.221.68.32) 11.113 ms 10.656 ms 10.636 ms
8 langbbrj02-ae1.301.r2.la. cox. net (68.105.30.129) 10.593 ms 10.594 ms 10.579 ms
9 68.1.1.60 (68.1.1.60) 7.120 ms 7.117 ms 7.107 ms
10 * * *
11 * * *
12 * * *
13 * * *
14 * * *
15 * * *
31/03/2019 01:48:18 UTC
PING:
PING 68.4.255.110 (68.4.255.110) 56(84) bytes of data.
— 68.4.255.110 ping statistics —
4 packets transmitted, 0 received, 100% packet loss, time 2998ms
31/03/2019 01:48:18 UTC
MTR:
Start: Sun Mar 31 01:48:18 2019 Blizzard 1.|-- Blizzard 0.0% 10 0.3 0.3 0.2 0.5 0.0
2.|-- 24.105.18.131 0.0% 10 0.6 0.6 0.5 0.7 0.0
3.|-- 137.221.105.12 0.0% 10 0.6 0.7 0.6 0.8 0.0
4.|-- 137.221.66.20 0.0% 10 0.6 0.7 0.6 0.8 0.0
5.|-- 137.221.83.68 0.0% 10 5.8 7.5 5.7 22.2 5.1
6.|-- 137.221.65.68 0.0% 10 5.7 11.6 5.7 35.5 10.3
7.|-- 137.221.68.32 0.0% 10 5.7 6.0 5.6 8.5 0.8
8.|-- langbbrj02-ae1.301.r2.la.cox. net 0.0% 10 5.5 5.8 5.4 8.2 0.7
9.|-- 68.1.1.60 0.0% 10 10.4 13.2 6.9 39.7 10.2
10.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0