hopefully they fix the issue
maybe next week at this point lol they’re really bad at letting people know when they have issues. typical blizzard style
Yeah, at this point I can’t even assume it’s Verizon. While it may be Verizon’s servers, it seems that the issue is only affecting Blizzard games.
Strangely if I VPN to DC which is only an hour away my ping is fine but Im still getting the packet loss icons. Turn off VPN and bam back to high ping
1 Like
Looks like the problem has toned down a bit. I get 30 ms but my ping occasionally spikes to 70 (more often than it happened before)
Hey all,
It looks like there were some routing issues between Verizon and Level3 that was causing this high latency. It was happening before the connection hit the Blizzard network.
Things appear to be better now, if you all want to try connecting again to test it out.
If anyone is still experiencing issues go ahead and post a Looking Glass on this thread.
there is massive amounts of packet loss
It was fine this morning for about an hour. Now its back to the same bad ping/packet loss. Also if I dont VPN to DC it keeps putting me in the sea1 server instead of ord1.
Hi. For I dont know how long I have been experiencing higher ping than normal that goes up to 140s. Usually my ping floats around 30 - 45. Every game Ive been entering now consistantly puts my ping in the 140s. I have been able to play around it by using WTFast and routing through their servers, but when I dont use it I get 140 ping. Its strange. Im using ethernet directly to my router. Overwatch is the only game where this is happening. Any other game I have tried this does not happen.
I was affected by the Verizon issue that happened last night. It was fixed until i played this morning. I was somehow connected to the sae1 server despite living in the US East coast while running the WinMTR test, but still entered 24.105.62.129 as the host as Jambrix ordered.
|------------------------------------------------------------------------------------------|
| WinMTR statistics |
| Host - % | Sent | Recv | Best | Avrg | Wrst | Last |
|---|---|---|---|---|---|---|
| 192.168.0.1 - 1 | 398 | 397 | 1 | 4 | 329 | 1 |
| Fios_Quantum_Gateway.fios-router.home - 0 | 402 | 402 | 1 | 3 | 300 | 3 |
| 24.105.62.129 - 0 | 402 | 402 | 6 | 16 | 356 | 7 |
| ________________________________________________ | ______ | ______ | ______ | ______ | ______ | ______ |
WinMTR v0.92 GPL V2 by Appnor MSP - Fully Managed Hosting & Cloud Provider
EDIT: I joined my friend’s custom game, which was on the ord1 server, and ran another test
|------------------------------------------------------------------------------------------|
| WinMTR statistics |
| Host - % | Sent | Recv | Best | Avrg | Wrst | Last |
|---|---|---|---|---|---|---|
| 192.168.0.1 - 0 | 312 | 312 | 1 | 2 | 246 | 1 |
| Fios_Quantum_Gateway.fios-router.home - 0 | 312 | 312 | 1 | 3 | 246 | 1 |
| 24.105.44.87 - 0 | 312 | 312 | 5 | 14 | 228 | 14 |
| ________________________________________________ | ______ | ______ | ______ | ______ | ______ | ______ |
WinMTR v0.92 GPL V2 by Appnor MSP - Fully Managed Hosting & Cloud Provider
Same here, issues starting appearing about a week ago. Normally get around 30-50 ping on Version na east, now im getting 160
1 Like
I cant even get on the ord1 server anymore without using VPN. Im on the east coast but every game puts me on sea1
1 Like
Same issues here. Normally 30-40 ping, this morning it’s 170+ and putting me in a multitude of different servers seemingly at random. NA East is my location.
Edit: Using VPN to DC worked for me, currently back at 40 ping.
2 Likes
Same here
Also where do I send WinMTR to 24.105.62.129
Here’s my WinMTR results from Americas servers. I have Verizon Fios. I get 160ms when I launch with “Americas” selected, and, 110ms when I launch choosing “Europe”. Seems like it would be wise for Blizzard to contact Verizon, rather than to expect every Verizon customer to individually contact Verizon to resolve this.
|------------------------------------------------------------------------------------------|
| WinMTR statistics |
| Host - % | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
| Wireless_Broadband_Router.home - 0 | 617 | 617 | 0 | 0 | 2 | 0 |
| 24.105.62.129 - 0 | 617 | 617 | 3 | 7 | 70 | 4 |
|____________|||||||
WinMTR v0.92 GPL V2 by Appnor MSP - Fully Managed Hosting & Cloud Provider
1 Like
|------------------------------------------------------------------------------------------|
| WinMTR statistics |
| Host - % | Sent | Recv | Best | Avrg | Wrst | Last |
|---|---|---|---|---|---|---|
| G3100.myfiosgateway.c0m - 0 | 363 | 363 | 0 | 1 | 51 | 1 |
| 24.105.62.129 - 0 | 363 | 363 | 1 | 6 | 77 | 3 |
| ________________________________________________ | ______ | ______ | ______ | ______ | ______ | ______ |
WinMTR v0.92 GPL V2 by Appnor MSP - Fully Managed Hosting & Cloud Provider
Same issue here. My ping is around 175 on VZ Fios because I seem to get connected to Brazilian servers instead of US East
Yeah, there’s something wrong with the Level 3 Servers/Verizon that are connected to Blizzard. Or something along those corners
Hey there,
It looks like due to the way FIOS has their network setup, the winMTR test we normally request may not work. Could we get a Looking Glass test instead?
Please also put three ~ marks above and below the test. It should look something like this before posting:
~~~
Test results
~~~
After posting it will look like this:
Test results
Thank you for working with us on this. We look forward to hearing from you.
Hi Kaldraydis,
This is what I got:
TRACEROUTE:
traceroute to 173.72.148.173 (173.72.148.173), 15 hops max, 60 byte packets
1 Blizzard Blizzard 0.901 ms 0.899 ms 0.900 ms
2 24.105.18.2 (24.105.18.2) 1.583 ms 1.613 ms 1.650 ms
3 137.221.105.10 (137.221.105.10) 1.613 ms 1.615 ms 1.621 ms
4 137.221.66.20 (137.221.66.20) 1.504 ms 1.526 ms 1.530 ms
5 137.221.83.84 (137.221.83.84) 119.958 ms 119.962 ms 344.055 ms
6 * * *
7 137.221.68.32 (137.221.68.32) 5.930 ms 6.012 ms 6.023 ms
8 4-1-3.ear3.LosAngeles1.Level3.net (4.71.135.105) 5.399 ms 5.513 ms 5.491 ms
9 ae-2-3601.edge7.LosAngeles1.Level3.net (4.69.219.45) 5.688 ms 5.608 ms 5.674 ms
10 TWC-level3-40G.Miami.Level3.net (4.68.62.182) 5.607 ms 5.593 ms 5.591 ms
11 ae199-21.CLPPVA-VFTTP-304.verizon-gni.net (100.41.24.133) 168.411 ms 168.436 ms 168.435 ms
12 * * *
13 * * *
14 * * *
15 * * *
26/08/2020 20:36:53 UTC
--------------------
PING:
PING 173.72.148.173 (173.72.148.173) 56(84) bytes of data.
--- 173.72.148.173 ping statistics ---
4 packets transmitted, 0 received, 100% packet loss, time 2998ms
26/08/2020 20:36:53 UTC
--------------------
MTR:
Start: Wed Aug 26 20:36:53 2020 Blizzard 1.|-- Blizzard 0.0% 10 0.3 0.4 0.3 1.1 0.0
2.|-- 24.105.18.2 0.0% 10 0.6 0.6 0.5 0.8 0.0
3.|-- 137.221.105.10 0.0% 10 1.0 0.9 0.8 1.1 0.0
4.|-- 137.221.66.20 0.0% 10 0.6 0.5 0.4 0.6 0.0
5.|-- 137.221.83.84 0.0% 10 503.8 697.0 108.6 1416. 512.3
6.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0
7.|-- 137.221.68.32 0.0% 10 5.9 10.5 5.9 28.1 9.1
8.|-- 4-1-3.ear3.LosAngeles1.Level3.net 0.0% 10 5.5 5.5 5.4 5.7 0.0
9.|-- ae-2-3601.edge7.LosAngeles1.Level3.net 0.0% 10 5.7 7.7 5.7 15.9 3.7
10.|-- TWC-level3-40G.Miami.Level3.net 0.0% 10 5.8 9.0 5.7 38.2 10.2
11.|-- ae199-21.CLPPVA-VFTTP-304.verizon-gni.net 0.0% 10 168.5 168.8 168.3 170.9 0.7
12.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0
26/08/2020 20:36:53 UTC
--------------------
For reference, I have Fios in Virginia.
Thanks,
Drgn