Been browsing the forums here to see if anything can resolve my current issue, but it seems many people are having the same problem as me. Constant ping spike and disconnect issues even though internet/PC is working perfectly fine.
There is a common issue that ties us all together. We all are based around NY and have Verizon.
I know from experience this has happened multiple times in different games where certain regions/state have networking issues based off of certain ISP and regions.
If anyone is having the same problem, please post your ISP and region/state so we can identify the underlying issue.
I am also in NYC and using Verizon, and I’ve been experiencing the same issues in the past two days. Pretty regular ping of 200+ with the occasional spike to just under 1000. Totally not the norm, and has been consistently bad over the past couple of days.
Thank you for your reports! I went ahead and adjusted the title here to see if we can get a bit more traction on this issue! I’ve seen a few other reports with our other games, so there may be some common issue causing the latency and disconnections.
We may be limited since Verizon’s has a different structure limiting what we can see in the connection route. We may be able to pick some details up from a test to check the connection from the Blizzard server to you. Could you provide a Looking Glass test to check out?
Unfortunately testing Warcraft 3 is not available through the Looking Glass tool, is there a different server I should select to run the test?
I think I can help here a bit. I’ve been experiencing constant issues with disconnects for few months. I’m using Verizon and am located in Boston.
After some troubleshooting with mtr, I’ve noticed some packet loss and hence tried same tests with Mobile Hotspot and VPN (neither use Verizon) and have seen better performance.
Note: I’m playing wc3 on MacOS, and hence I’m not using WinMTR.
I’ve tried running mtr now, but see no packet loss, so can’t provide exact details (I’ll try again within next couple of days).
However, few days ago, when I was experiencing increased number of disconnects, I was running mtr in the background. In general, running mtr by sending ICMP ECHO packets showed no issues. However, as soon as I ran mtr for tcp or udp packets, I immediately saw 40%-50% packet loss at variants of 0.ae3.br2.nyc4.alter.net and ip addresses with range 32.130.248.0 - 32.130.248.255. This doesn’t always mean those points on the path are bad, but it was interesting to see packet loss so high and not see anything like that on mobile hotspot / vpn.
A couple important distinctions I’d like to make here that seem common between the five users I’ve talked to with the exact same symptoms (AfterDawn, Arold, huttnnn, myself, and dRyAd):
-
This definitely only started happening in the past week. This has not been a recurring issue. I have been playing nearly daily for several months with no issues of this nature. It’s possible there have been longer term issues with Verizon, but this specific issue is definitely something recently introduced.
-
The nature of the problem is consistent and happens very frequently, but not every single game. It’s often enough that I don’t consider my connection currently reliable enough to play at all as I risk disconnecting a high percentage of the time.
-
I am trying connecting via VPN today and did experience one instance of the ping spikes without disconnecting in the one game I played. I’ll update on how the VPN experiment goes.
I’ve run mtr now and I’ve gotten similar results to what I would see when I would get disconnect/desync.
mtr sending ICMP ECHO packets:
Keys: Help Display mode Restart statistics Order of fields quit
Packets Pings
Host Loss% Snt Last Avg Best Wrst StDev
3. b3341.bstnma-lcr-21.verizon-gni. 0.0% 254 11.6 11.8 7.0 51.4 3.0
4. (waiting for reply)
5. (waiting for reply)
6. (waiting for reply)
7. 0.ae2.br2.nyc4.alter.net 0.0% 253 15.6 16.4 13.7 59.6 4.6
8. 192.205.34.49 0.0% 253 15.4 18.2 14.1 50.3 2.8
9. cr1.n54ny.ip.att.net 0.0% 253 36.3 36.2 31.2 63.3 2.5
10. cgcil22crs.ip.att.net 0.0% 253 37.3 38.0 31.6 62.3 3.0
11. cr81.cgcil.ip.att.net 0.0% 253 35.8 35.3 31.1 62.9 2.2
12. 32.130.248.134 0.0% 253 35.7 35.7 32.7 63.7 2.0
13. 32.130.248.147 0.4% 253 35.1 34.4 30.9 46.1 1.7
14. (waiting for reply)
mtr sending tcp packets:
Keys: Help Display mode Restart statistics Order of fields quit
Packets Pings
Host Loss% Snt Last Avg Best Wrst StDev
3. b3341.bstnma-lcr-22.verizon-gni. 0.0% 428 10.2 12.4 8.0 53.9 2.7
b3341.bstnma-lcr-21.verizon-gni.net
4. (waiting for reply)
5. (waiting for reply)
6. 0.ae2.br2.nyc4.alter.net 49.9% 428 14.4 16.9 14.1 58.2 4.0
7. 192.205.34.49 0.0% 428 17.9 17.9 13.7 83.5 4.9
0.ae2.br2.nyc4.alter.net
8. 192.205.34.49 0.0% 428 14.3 28.2 14.2 66.6 9.6
cr1.n54ny.ip.att.net
9. cgcil22crs.ip.att.net 0.0% 428 36.9 37.8 31.8 72.0 3.2
cr1.n54ny.ip.att.net
199.108.55.59
10. cr81.cgcil.ip.att.net 0.0% 428 35.2 36.9 32.1 62.7 2.7
cgcil22crs.ip.att.net
199.108.55.59
11. cr81.cgcil.ip.att.net 0.0% 428 36.1 35.6 32.0 63.3 1.9
32.130.248.134
32.130.248.136
199.108.55.59
12. 32.130.248.134 0.0% 428 35.7 35.1 31.3 39.5 1.5
32.130.248.147
32.130.248.165
32.130.248.136
13. 32.130.248.147 52.1% 428 33.1 33.9 31.4 38.1 1.4
32.130.248.165
14. (waiting for reply)
mtr sending udp packets:
Keys: Help Display mode Restart statistics Order of fields quit
Packets Pings
Host Loss% Snt Last Avg Best Wrst StDev
3. b3341.bstnma-lcr-22.verizon-gni. 0.0% 383 14.6 12.4 7.4 45.9 2.5
b3341.bstnma-lcr-21.verizon-gni.net
4. (waiting for reply)
5. (waiting for reply)
6. 0.ae2.br2.nyc4.alter.net 48.4% 383 16.4 17.3 13.8 58.3 4.4
7. 0.ae2.br2.nyc4.alter.net 0.0% 383 17.5 17.8 13.7 61.6 3.5
192.205.34.49
8. 192.205.34.49 0.0% 383 16.9 27.9 13.5 83.6 10.0
cr1.n54ny.ip.att.net
9. cr1.n54ny.ip.att.net 0.0% 383 42.1 38.0 32.2 79.2 3.2
cgcil22crs.ip.att.net
10. cgcil22crs.ip.att.net 0.0% 383 37.2 37.0 31.3 69.7 3.0
cr81.cgcil.ip.att.net
11. cr81.cgcil.ip.att.net 0.0% 383 36.4 35.8 31.9 62.6 1.9
32.130.248.134
32.130.248.136
12. 32.130.248.134 0.0% 383 36.0 35.2 31.6 66.0 2.3
32.130.248.147
32.130.248.165
32.130.248.136
13. 32.130.248.165 53.4% 383 37.1 34.1 31.5 41.8 1.6
32.130.248.147
14. (waiting for reply)
Thanks for the details here! I’m getting this added to our tracking and we’re gathering reports from our other games reporting similar issues. Just the Battle.net Authication should do for our purposes. Please continue to provide Looking Glass Tests
For everyone having issues with Verizon, is anyone not from New York? An overwhelming amount of reports that I’m seeing is from New York at the moment!
Like I already wrote in the comment above, I’m from Boston. But, based on mtr test, my connection to Blizzard servers goes through nyc.
Here are my test results for Battle.net Authentication - though I feel compelled to point out that I also play a lot of Starcraft 2 and have had zero issues in those games, so I don’t believe my issue is affecting all Blizzard servers.
TRACEROUTE:
traceroute to 71.105.150.14 (71.105.150.14), 15 hops max, 60 byte packets
1 Blizzard Blizzard 1.922 ms 1.893 ms 1.890 ms
2 24.105.18.2 (24.105.18.2) 2.756 ms 2.754 ms 2.752 ms
3 137.221.105.10 (137.221.105.10) 2.749 ms 2.745 ms 2.744 ms
4 137.221.66.16 (137.221.66.16) 2.704 ms 2.710 ms 2.708 ms
5 137.221.83.80 (137.221.83.80) 3.094 ms 3.097 ms 3.096 ms
6 137.221.65.68 (137.221.65.68) 7.338 ms 6.271 ms 6.236 ms
7 137.221.68.32 (137.221.68.32) 6.223 ms 6.216 ms 6.213 ms
8 las-b21-link.telia.net (62.115.178.200) 5.576 ms 7.535 ms 7.517 ms
9 157.130.245.25 (157.130.245.25) 21.076 ms 14.766 ms 14.780 ms
10 * * *
11 ae203-0.NYCMNY-VFTTP-347.verizon-gni.net (130.81.171.229) 61.977 ms 61.587 ms 61.583 ms
12 pool-71-105-150-14.nycmny.fios.verizon.net (71.105.150.14) 68.763 ms 68.758 ms 66.556 ms
16/06/2020 03:52:55 UTC
--------------------
PING:
PING 71.105.150.14 (71.105.150.14) 56(84) bytes of data.
64 bytes from 71.105.150.14: icmp_seq=1 ttl=48 time=68.3 ms
64 bytes from 71.105.150.14: icmp_seq=2 ttl=48 time=67.2 ms
64 bytes from 71.105.150.14: icmp_seq=3 ttl=48 time=66.9 ms
64 bytes from 71.105.150.14: icmp_seq=4 ttl=48 time=66.8 ms
--- 71.105.150.14 ping statistics ---
4 packets transmitted, 4 received, 0% packet loss, time 2999ms
rtt min/avg/max/mdev = 66.833/67.342/68.363/0.661 ms
16/06/2020 03:52:55 UTC
--------------------
MTR:
Start: Tue Jun 16 03:52:55 2020 Blizzard 1.|-- Blizzard 0.0% 10 0.3 0.3 0.2 0.5 0.0
2.|-- 24.105.18.2 0.0% 10 0.6 0.7 0.5 1.2 0.0
3.|-- 137.221.105.10 0.0% 10 0.9 0.9 0.7 1.0 0.0
4.|-- 137.221.66.16 0.0% 10 0.4 0.5 0.4 0.7 0.0
5.|-- 137.221.83.80 0.0% 10 7.4 4.5 1.3 7.9 2.5
6.|-- 137.221.65.68 0.0% 10 5.7 8.8 5.7 26.9 7.0
7.|-- 137.221.68.32 0.0% 10 5.9 7.5 5.8 21.2 4.8
8.|-- las-b21-link.telia.net 0.0% 10 5.9 5.8 5.6 6.0 0.0
9.|-- 157.130.245.25 0.0% 10 5.8 6.6 5.5 11.9 1.8
10.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0
11.|-- ae203-0.NYCMNY-VFTTP-347.verizon-gni.net 0.0% 10 61.7 62.0 61.5 65.4 1.1
12.|-- pool-71-105-150-14.nycmny.fios.verizon.net 0.0% 10 67.0 67.5 65.2 69.1 1.0
16/06/2020 03:52:55 UTC
--------------------
@LeaveItsGG, I do see that it’s routing through NY. I’ve seen a few in PA, but a large majority have been in NY. I haven’t seen any other reports from Boston just yet, but I’ll keep a look out for additional reports from around there!
@Pokebunny, thanks for the details! I’m getting this added to our tracking. We’re still trying to find where the problem is happening, but we’ve only seen this reported with WoW and WC3 so far.
The main issue is that Verizon has made some changes to the backbone making ipv4 tests only show the home network and the server, so we’re pretty limited with what tests we can recommend and the looking glass being our main source due to the backbone concerns. I’m curious to how the looking glass test would compare with the WoW looking glass (since we’re seeing issues with this game as well) or SC1/SC:R (since it should be using similar servers to WC3).
Thanks for providing details here, both of you 
I’m back in PA and I’m still disconnecting every few games. What is it we’re able to do to fix this? Anything? Or is this in Blizzards hands?
Any explanation would be helpful here. Thanks.
It’s worth mentioning that in PA at my parents house I’m using Comcast Xfinity and I’m having the exact same problems as I did on Verizon FiOS in NYC. So I don’t see how this is solely a Verizon problem - it has to be a Blizzard problem if it’s happening on multiple ISPs.
Very interesting, first report I’ve heard from someone not on Verizon, sounds like it would make the issue much harder to track down
I’ve reinstalled the game and so far I haven’t had an issue. And I’ve played about 7 or 8 games.
I tried reinstalling immediately when I had this issue the first couple times and it didn’t seem to improve the issue, though it appears to have gotten slightly less frequent in the past 1-2 days.
Pokebunny I am up to ~20 games and no issues thus far. Fingers crossed…
Added you on discord btw.
Might have deleted the request because I didn’t recognize it, so feel free to send again.
Glad to hear it, I’ve played a few games today and not yet a disconnect though sitll had a couple heavy ping spikes where I feared I would disconnect. Playing 3 games for a tournament tonight so praying those go off without a hitch lol.
same here at NYC, i have WOW classic with first account have no problem and 2nd account just lag out in town(chat is fine but i cant move or cast anything). is this have something to do with verizon only or its happen to everyone.
Well I spoke too soon, I just disconnected without warning.
@Blizzard are you guys doing anything about this? It’s clearly on your end and NOT the end of the ISP. Since I am playing on a different ISP than I was in NYC and still disconnecting.