Child Item

Site Totals

61498 Questions Answered 271 Categories

Fios and Blizzard Games

I've been playing Blizzard games for as long as I can remember. It wasn't until I recently made the swap to Verizon Fios that I've had nothing but lag problems. I've run a pathping and a WINMTR test, which shows significant packet loss on the Verizon side of things. Has anyone had experience with this, and figured out a way to resolve it? I've disabled IPv6 and have flushed DNS, released and renewed, etc. Still having the same issues. Verizon is telling me that my internet is fine.. my lag is telling me otherwise.

Comments

JustinG1

Hello!

Is your device connected via WiFi or a wired Ethernet connection?

I've never had the slighest issue with the actual FiOS service in regards to lag, but I do know that the newer G1100 Verizon routers do have some shortcomings with their WiFi. But for gaming a wired connection should be a must.

When you say you are seeing loss on the Verizon side, is it after 2 hops after it leaves your house? (See screenshot below). This is normal.

If not, please do post a screenshot of the test and we can better help.

Easife

Hello! I was trying to find a way to attach a picture earlier. I've pasted the tracert below. Please let me know if you cannot read that. I am connected wirelessly, though I've had this issue prior to changing over to Fios.

JustinG1

Your traceroute looks fine, you'll notice the loss and (???) marks once you hit a Level3.net router, this is just how Level3 handles traceroutes (their routers don't respond to requests).

I'd say the problem is most likely on the LAN side (inside the house). Would it be possible to wire your game console temporarily and test if the lag goes away, to test if WiFi is the culprit?

Easife

I can try and do a hard wired connection temporarily. The fact of the matter is this issue only occured once I swapped over to Fios. Wireless hasn't been an issue with my previous ISP.

smith6612

Blizzard provides a looking glass server which can help troubleshoot the problem some more. Besides tracing from your computer to a Blizzard server, also include the traces/MTRs/Ping results seen from this website: https://us-looking-glass.battle.net/

That should help identify if we also have a bad return route.

Capricorn1

@Smith6612 wrote:
Blizzard provides a looking glass server which can help troubleshoot the problem some more. Besides tracing from your computer to a Blizzard server, also include the traces/MTRs/Ping results seen from this website: https://us-looking-glass.battle.net/
That should help identify if we also have a bad return route.

Thanks, @Smith6612. I wonder how long that Looking Glass server has existed? I never knew about it. I played WoW for many years spread through almost a decade, and I thought I knew all the tricks. BTW, the URL is http://us-looking-glass.battle.net/ (that is http, not https). I get a This site can’t be reached error if I use https.

My results from the WoW Bronzebeard server (my old haunt for most of my characters) for the MTR and traceroute tests (which are very similar) are:

TRACEROUTE:
traceroute to 108.44.193.140 (108.44.193.140), 15 hops max, 60 byte packets
 1  24.105.30.3 (24.105.30.3)  0.548 ms  0.678 ms  0.733 ms
 2  * * *
 3  137.221.66.4 (137.221.66.4)  1.271 ms  1.327 ms  1.395 ms
 4  137.221.68.72 (137.221.68.72)  1.260 ms  1.281 ms  1.298 ms
 5  137.221.68.34 (137.221.68.34)  0.915 ms  0.926 ms  1.117 ms
 6  xe-9-3-0.edge2.LosAngeles9.Level3.net (4.53.230.237)  0.827 ms  0.826 ms  0.820 ms
 7  * * *
 8  Verizon-level3-50G.LosAngeles1.Level3.net (4.68.63.246)  0.841 ms  0.842 ms  0.868 ms
 9  * * *
10  ae203-0.CLPPVA-VFTTP-304.verizon-gni.net (130.81.221.133)  61.402 ms  61.440 ms  61.338 ms
11  * * *
12  * * *
13  * * *
14  * * *
15  * * *

07/01/2018 14:01:39 UTC
--------------------

TRACEROUTE:
traceroute to 108.44.193.140 (108.44.193.140), 15 hops max, 60 byte packets
 1  24.105.30.3 (24.105.30.3)  1.054 ms  1.060 ms  1.079 ms
 2  * * *
 3  137.221.66.4 (137.221.66.4)  1.164 ms  1.254 ms  1.330 ms
 4  137.221.68.72 (137.221.68.72)  1.235 ms  1.263 ms  1.288 ms
 5  137.221.68.34 (137.221.68.34)  0.859 ms  1.054 ms  1.068 ms
 6  xe-9-3-0.edge2.LosAngeles9.Level3.net (4.53.230.237)  0.859 ms  0.834 ms  0.831 ms
 7  * * *
 8  Verizon-level3-50G.LosAngeles1.Level3.net (4.68.63.246)  0.838 ms  0.844 ms  0.844 ms
 9  * * *
10  ae203-0.CLPPVA-VFTTP-304.verizon-gni.net (130.81.221.133)  61.381 ms  61.416 ms  61.415 ms
11  * * *
12  * * *
13  * * *
14  * * *
15  * * *


07/01/2018 14:01:39 UTC
--------------------

TRACEROUTE:
traceroute to 108.44.193.140 (108.44.193.140), 15 hops max, 60 byte packets
 1  Blizzard (Blizzard)  0.625 ms  0.726 ms  0.846 ms
 2  * * *
 3  * * *
 4  137.221.69.72 (137.221.69.72)  6.231 ms  6.258 ms  6.279 ms
 5  137.221.69.34 (137.221.69.34)  1.737 ms  1.743 ms  1.839 ms
 6  xe-11-3-0.edge4.Chicago3.Level3.net (4.53.98.45)  6.399 ms  4.485 ms  4.470 ms
 7  MCI-level3-ae.chicago3.level3.net (4.68.110.186)  1.473 ms  1.487 ms  1.497 ms
 8  * * *
 9  ae203-0.CLPPVA-VFTTP-304.verizon-gni.net (130.81.221.133)  21.048 ms  21.081 ms  21.082 ms
10  * * *
11  * * *
12  * * *
13  * * *
14  * * *
15  * * *


07/01/2018 14:01:39 UTC
--------------------

TRACEROUTE:
traceroute to 108.44.193.140 (108.44.193.140), 15 hops max, 60 byte packets
 1  Blizzard (Blizzard)  0.767 ms  0.795 ms  0.848 ms
 2  * * *
 3  * * *
 4  137.221.69.72 (137.221.69.72)  1.921 ms  1.947 ms  1.969 ms
 5  137.221.69.34 (137.221.69.34)  1.750 ms  1.761 ms  1.774 ms
 6  xe-11-3-0.edge4.Chicago3.Level3.net (4.53.98.45)  1.509 ms  1.533 ms  1.515 ms
 7  MCI-level3-ae.chicago3.level3.net (4.68.110.186)  1.439 ms  1.462 ms  1.460 ms
 8  * * *
 9  ae203-0.CLPPVA-VFTTP-304.verizon-gni.net (130.81.221.133)  21.108 ms  21.144 ms  21.060 ms
10  * * *
11  * * *
12  * * *
13  * * *
14  * * *
15  * * *


07/01/2018 14:01:44 UTC
--------------------

MTR:
Start: Sun Jan  7 14:01:39 2018
HOST: Blizzard                Loss%   Snt   Last   Avg  Best  Wrst StDev
  1.|-- 24.105.30.3                                0.0%    10    0.7   0.8   0.5   1.7   0.0
  2.|-- ???                                       100.0    10    0.0   0.0   0.0   0.0   0.0
  3.|-- 137.221.66.4                               0.0%    10    1.3   1.4   1.3   1.5   0.0
  4.|-- 137.221.68.72                              0.0%    10    1.4   1.9   1.2   4.8   1.2
  5.|-- 137.221.68.34                              0.0%    10    1.0   1.0   0.9   1.1   0.0
  6.|-- xe-9-3-0.edge2.LosAngeles9.Level3.net      0.0%    10    1.0   0.9   0.9   1.0   0.0
  7.|-- ???                                       100.0    10    0.0   0.0   0.0   0.0   0.0
  8.|-- Verizon-level3-50G.LosAngeles1.Level3.net  0.0%    10    0.9   2.5   0.9  16.9   5.0
  9.|-- ???                                       100.0    10    0.0   0.0   0.0   0.0   0.0
 10.|-- ae203-0.CLPPVA-VFTTP-304.verizon-gni.net   0.0%    10   61.4  63.4  61.4  80.4   6.0
 11.|-- ???                                       100.0    10    0.0   0.0   0.0   0.0   0.0


07/01/2018 14:01:39 UTC
--------------------

MTR:
Start: Sun Jan  7 14:01:39 2018
HOST: Blizzard                Loss%   Snt   Last   Avg  Best  Wrst StDev
  1.|-- 24.105.30.3                                0.0%    10    0.7   0.8   0.4   1.7   0.0
  2.|-- ???                                       100.0    10    0.0   0.0   0.0   0.0   0.0
  3.|-- 137.221.66.4                               0.0%    10    1.3   1.3   1.1   1.6   0.0
  4.|-- 137.221.68.72                              0.0%    10    1.4   2.0   1.2   4.8   1.2
  5.|-- 137.221.68.34                              0.0%    10    1.0   1.0   0.9   1.1   0.0
  6.|-- xe-9-3-0.edge2.LosAngeles9.Level3.net      0.0%    10    0.9   0.9   0.8   1.0   0.0
  7.|-- ???                                       100.0    10    0.0   0.0   0.0   0.0   0.0
  8.|-- Verizon-level3-50G.LosAngeles1.Level3.net  0.0%    10    0.9   2.5   0.8  16.8   5.0
  9.|-- ???                                       100.0    10    0.0   0.0   0.0   0.0   0.0
 10.|-- ae203-0.CLPPVA-VFTTP-304.verizon-gni.net   0.0%    10   61.4  63.3  61.4  80.4   6.0
 11.|-- ???                                       100.0    10    0.0   0.0   0.0   0.0   0.0


07/01/2018 14:01:39 UTC
--------------------

MTR:
Start: Sun Jan  7 14:01:39 2018
HOST: Blizzard               Loss%   Snt   Last   Avg  Best  Wrst StDev
  1.|-- Blizzard                            0.0%    10    0.6   0.5   0.5   0.6   0.0
  2.|-- ???                                      100.0    10    0.0   0.0   0.0   0.0   0.0
  3.|-- ???                                      100.0    10    0.0   0.0   0.0   0.0   0.0
  4.|-- 137.221.69.72                             0.0%    10    2.2   2.7   2.0   7.3   1.5
  5.|-- 137.221.69.34                             0.0%    10    1.8   2.2   1.7   5.4   1.1
  6.|-- xe-11-3-0.edge4.Chicago3.Level3.net       0.0%    10    1.6   1.6   1.5   1.6   0.0
  7.|-- MCI-level3-ae.chicago3.level3.net         0.0%    10    1.5   1.5   1.5   1.5   0.0
  8.|-- ???                                      100.0    10    0.0   0.0   0.0   0.0   0.0
  9.|-- ae203-0.CLPPVA-VFTTP-304.verizon-gni.net  0.0%    10   21.1  24.2  21.1  51.5   9.6
 10.|-- ???                                      100.0    10    0.0   0.0   0.0   0.0   0.0


07/01/2018 14:01:39 UTC
--------------------

MTR:
Start: Sun Jan  7 14:01:44 2018
HOST: Blizzard               Loss%   Snt   Last   Avg  Best  Wrst StDev
  1.|-- Blizzard                            0.0%    10    0.6   0.6   0.5   0.6   0.0
  2.|-- ???                                      100.0    10    0.0   0.0   0.0   0.0   0.0
  3.|-- ???                                      100.0    10    0.0   0.0   0.0   0.0   0.0
  4.|-- 137.221.69.72                             0.0%    10    1.9   2.6   1.9   7.5   1.7
  5.|-- 137.221.69.34                             0.0%    10    1.9   1.8   1.8   1.9   0.0
  6.|-- xe-11-3-0.edge4.Chicago3.Level3.net       0.0%    10    1.6   1.6   1.5   1.6   0.0
  7.|-- MCI-level3-ae.chicago3.level3.net         0.0%    10    1.5   8.2   1.5  68.4  21.2
  8.|-- ???                                      100.0    10    0.0   0.0   0.0   0.0   0.0
  9.|-- ae203-0.CLPPVA-VFTTP-304.verizon-gni.net  0.0%    10   21.1  24.3  21.1  52.5   9.9
 10.|-- ???                                      100.0    10    0.0   0.0   0.0   0.0   0.0


07/01/2018 14:01:43 UTC
--------------------

seedcow

I'm currently experiencing very high latency when trying to connect to or use any Blizzard server, including any of their games or websites.

Apparently this issue is only being reported by Verizon FIOS users on the East coast, specifically in the Maryland/Virginia area

Originally reported about four hours ago.. by a few hundred people in this thread alone:

https://us.battle.net/forums/en/wow/topic/20760937159?page=1

Or if you dont want to use my link you can find the thread by going to:

WoW Forums -> Technical Support -> Connection issues 1/20/2018

This isn't listed as an outage or issue anywhere I can find on the FIOS site, and the fact that it's gone on for so many hours is concerning.. a large reason I pay for FIOS is for the reliable and fast connection to be able to play Blizzard games.

If I can expect service degredation this bad for periods of time this long, I'll have to move on to a different internet provider.

Devasi

For the past few hours, there have been massive reports on Blizzard forums about disconnects on the east coast for FiOS customers. I have experienced this as well, and it's very random!

Swells2

Blizzard games are currently crashing for many, many verizon internet users in the eastern united states. Blizzard says this is not on their end, and we need to compain to you all to fix it. Please fix it.

av8ordoc

I am experiencing the same thing in the Buffalo, NY area. My Fios speed test is right at my max speed (150/150Mbps), but Blizzard games like World of Warcraft have latencies over 1000 (also causing disconnects).

Mazdak

This problem has reoccurred 01/21/2017 at approximately 10:30AM EST.

When I run the Blizzard Battle.net Looking Glass tool, it's showing 20% to 40% packet loss rates for the last 2 hops to me.

Those routers are:

ae203-0.WASHDC-VFTTP-309.verizon-gni.net 20.0%

pool-108-31-123-14.washdc.fios.verizon.net 40.0%

Please fix these obviously malfunctioning routers.

darkiya

This has been going on for 24-hours now since 1/20/2018 at about 2pm EST. Steps taken personally to resolve it include::
- Computer Reboot
- Recycling the Router
- Calling customer support and having them recycle our box (Notes on my file for what they did)
- Contacting Blizzard Customer Service

MTR Data
MTR:
Start: Sun Jan 21 18:18:18 2018
HOST: Blizzard Loss% Snt Last Avg Best Wrst StDev
1.|-- 10.56.100.81 0.0% 10 0.3 0.3 0.2 0.8 0.0
2.|-- 37.244.22.131 0.0% 10 0.5 0.5 0.4 0.8 0.0
3.|-- 24.105.30.162 0.0% 10 0.9 1.1 0.8 2.2 0.0
4.|-- 137.221.66.6 0.0% 10 1.5 1.6 1.4 1.8 0.0
5.|-- 137.221.68.68 0.0% 10 1.5 1.6 1.4 1.8 0.0
6.|-- 137.221.68.32 0.0% 10 1.2 1.6 1.2 3.8 0.6
7.|-- xe-9-3-0.edge2.LosAngeles9.Level3.net 0.0% 10 1.4 1.1 1.0 1.4 0.0
8.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0
9.|-- Verizon-level3-50G.LosAngeles1.Level3.net 0.0% 10 1.1 1.7 1.1 6.6 1.7
10.|-- ae203-0.NRFLVA-VFTTP-303.verizon-gni.net 40.0% 10 176.3 177.0 176.3 178.8 0.8
11.|-- pool-71-120-216-189.nrflva.fios.verizon.net 40.0% 10 185.5 184.7 182.9 186.2 1.1

Groovymarlin

This problem is affecting all Blizzard games. I've hardly been able to play World of Warcraft at all. Information from Blizzard's forums (blue post):

"We've found that the source of these problems seems to be a backbone provider between your individual internet service provider and our servers. None of the looking glass traces we've received for these showed issues between our peers and the Level 3 backbone. The winMTRs and traceroutes we received, however, show that there is a problem after your ISP hands data off to this backbone provider.

What this means is that the source of this problem isn't really your ISP or us, most likely. There are quite a few routers in between your ISP and our servers having issues. In situations like this where the backbone is the culprit, it's really up to your ISP to submit a report to them and try to leverage their business deals with the backbone provider to get it fixed. It's quite possible that this is already happening because of how many people the issue is happening to, but you can always help them with their investigation."

So, Verizon, how can we help you solve this problem, which is apparently with L3?

Tracert results:

Tracing route to 137.221.105.2 over a maximum of 30 hops

  1    <1 ms    <1 ms    <1 ms  192.168.0.1
  2     1 ms    <1 ms    <1 ms  FIOS_Quantum_Gateway.fios-router.home [192.168.1.1]
  3     5 ms     3 ms     4 ms  lo0-100.CLPPVA-VFTTP-304.verizon-gni.net [72.86.37.1]
  4     8 ms    10 ms     7 ms  B3304.CLPPVA-LCR-21.verizon-gni.net [130.81.221.132]
  5     *        *        *     Request timed out.
  6     8 ms     8 ms     6 ms  0.et-5-3-0.BR1.IAD8.ALTER.NET [140.222.239.79]
  7     *       15 ms     *     ae16.edge1.washingtondc12.level3.net [4.68.62.133]
  8     *        *        *     Request timed out.
  9   123 ms   123 ms     *     BLIZZARD-EN.ear3.Washington1.Level3.net [4.16.70.182]
 10     *      124 ms   124 ms  ae1-br01-eqdc2.blizzardonline.net [137.221.72.33]
 11   134 ms     *        *     xe-0-0-36-1-br01-eqat2.blizzardonline.net [137.221.65.45]
 12     *        *        *     Request timed out.
 13     *        *        *     Request timed out.
 14     *        *        *     Request timed out.
 15     *        *        *     Request timed out.
 16     *        *        *     Request timed out.
 17     *        *        *     Request timed out.
 18     *        *        *     Request timed out.
 19     *        *        *     Request timed out.
 20     *        *        *     Request timed out.
 21     *        *        *     Request timed out.
 22     *        *        *     Request timed out.
 23     *        *        *     Request timed out.
 24     *        *        *     Request timed out.
 25     *        *        *     Request timed out.
 26     *        *        *     Request timed out.
 27     *        *        *     Request timed out.
 28     *        *

Here's an MTR:

MTR:
Start: Sun Jan 21 18:50:31 2018
HOST: Blizzard                Loss%   Snt   Last   Avg  Best  Wrst StDev
  1.|-- 24.105.30.2                                0.0%    10    4.9   3.1   0.5  13.8   4.4
  2.|-- ???                                       100.0    10    0.0   0.0   0.0   0.0   0.0
  3.|-- 137.221.66.4                               0.0%    10    1.3   1.3   1.1   1.4   0.0
  4.|-- 137.221.68.68                              0.0%    10    1.4   1.3   1.2   1.4   0.0
  5.|-- 137.221.68.32                              0.0%    10    1.0   4.3   0.9  33.7  10.3
  6.|-- xe-9-3-0.edge2.LosAngeles9.Level3.net      0.0%    10    0.8   0.9   0.8   1.0   0.0
  7.|-- ???                                       100.0    10    0.0   0.0   0.0   0.0   0.0
  8.|-- Verizon-level3-50G.LosAngeles1.Level3.net  0.0%    10    1.0   1.0   0.9   1.5   0.0
  9.|-- ???                                       100.0    10    0.0   0.0   0.0   0.0   0.0
 10.|-- ae203-0.CLPPVA-VFTTP-304.verizon-gni.net  30.0%    10  172.1 171.6 171.0 172.1   0.0
 11.|-- pool-72-73-26-252.clppva.fios.verizon.net 40.0%    10  178.3 178.9 177.0 180.6   1.3

Sh0rty

Also located in Buffalo, NY. My GF and myself are having the same issues anytime we connect to a blizzard game, specifically WoW. The game has become completely unplayable.

Swells2

I’ve been having this issue for over 24 hrs now.

ageske

There is an east coast latency issue for league of legends. All users with this increase in ping are verizon users as well. Here is a link to the Riot Games' forum: https://boards.na.leagueoflegends.com/en/c/help-support/EGjn4bXd-east-coast-latency-issue-verizon

What could cause this and is there any progress being done to fix the problem? At first glance, it does not appear to be Riot Games' at fault considering only Verizon users are affected. Although, I'm not sure. Would appreciate any advice!

mattt0696

I was having issues as well. Is anyone still having issues. I am in lower virginia and had issues up till yesturday when i got my router replaced. check to see if you are having issues with other internet connections. ie: other video games or wifi drop out and such.

c_brunk

I have also been having issues. Just outside of Richmond, VA. Cannot connect to 130.81.24.74 reports: Destination net unreachable. This occurs at the third hop and only seems to be affecting Blizzard games and their website. This has been happening since about 19 January 2018. So I have been unable to use the product(s) I have paid for. Could someone from Verizon please respond to this forum to at least acknowledge you know about the issue?

ShoFly

Same issues in Northern VA. Blizzard games have high latency. Ping and Tracert tests to Blizzard IP's and the mentioned League of Legends are terrible. Something is up with Verizon or their backbone.

Child Item