High ping - Blizzard node issue or FIOS?

Technical Support
1

For the last 4 days or so my ping has gone from a normal 38, to a now 78-80… After finally having time to do a little troubleshooting I noticed I am having issue with the “ae1-br01-eqny8.as57976.net_ (137.221.71.33)” node… Is this a Blizzard issue or a FIOS issue where I can see if they can redirect it somehow? Below are two traceroutes I’ve done to the US servers.

2022-06-26T03:30:56+0500
HOST: DNSChecker                                 Loss%   Snt   Last   Avg  Best  Wrst StDev
  1.|-- ???                                             100.0     3    0.0   0.0   0.0   0.0   0.0
  2.|-- 10.74.196.69                                     0.0%     3    0.7   1.2   0.7   2.2   0.8
  3.|-- 138.197.251.0                                    0.0%     3    1.1   1.4   1.0   2.1   0.6
  4.|-- 138.197.248.16                                   0.0%     3    0.9   1.0   0.7   1.4   0.4
  5.|-- 138.197.244.44                                   0.0%     3    1.2   1.3   1.2   1.4   0.1
  6.|-- nyiix.eqny8.blizzardonline.net (198.32.160.141)  0.0%     3    1.9   2.3   1.9   2.9   0.5
  7.|-- ae1-br01-eqny8.as57976.net (137.221.71.33)       0.0%     3  304.1 187.2  93.4 304.1 107.3
  8.|-- ???                                             100.0     3    0.0   0.0   0.0   0.0   0.0
  9.|-- et-0-0-1-pe01-eqch2.as57976.net (137.221.69.51)  0.0%     3   22.1  22.1  22.0  22.1   0.1
 10.|-- 24.105.62.129                                    0.0%     3   23.0  23.4  23.0  24.1   0.6

Start: 2022-06-26T03:33:34+0500
HOST: DNSChecker                                 Loss%   Snt   Last   Avg  Best  Wrst StDev
  1.|-- ???                                             100.0     3    0.0   0.0   0.0   0.0   0.0
  2.|-- 10.74.132.79                                     0.0%     3    0.8   1.2   0.8   2.0   0.7
  3.|-- 138.197.251.14                                   0.0%     3    1.1   7.5   1.1  19.3  10.3
  4.|-- 138.197.248.18                                   0.0%     3    1.4   1.8   1.1   3.1   1.1
  5.|-- 138.197.244.44                                   0.0%     3    1.4   1.6   1.2   2.1   0.5
  6.|-- nyiix.eqny8.blizzardonline.net (198.32.160.141)  0.0%     3    3.4   2.9   2.3   3.4   0.6
  7.|-- ae1-br01-eqny8.as57976.net (137.221.71.33)       0.0%     3  230.9 148.4  69.4 230.9  80.8
  8.|-- ???                                             100.0     3    0.0   0.0   0.0   0.0   0.0
  9.|-- et-0-0-3-br02-eqla1.as57976.net (137.221.65.4)   0.0%     3  141.1  91.3  66.3 141.1  43.1
 10.|-- 137.221.68.91                                    0.0%     3   69.1  73.4  69.1  82.0   7.5
 11.|-- lax-eqla1-ia-bons-03.as57976.net (137.221.66.7)  0.0%     3   81.3  73.8  69.9  81.3   6.5
 12.|-- 24.105.30.129                                    0.0%     3   69.5  70.2  69.5  70.7   0.6
1 Like
2

that’s their network, had 4 lost games today because of DC’s. They never respond if it’s their AS causing issues.

3

Can’t use a looking glass to tell you where the issue is happening, that’s only useful if you can’t log in. Run a WinMTR instead.

4

Below is the WinMTR, but users on Verizon FIOS, such as myself, don’t show the complete hops through all of the nodes - only the starting IP and ending IP… Which is why I posted the traceroutes that show the issue is at hop 7 and 9 of the traceroutes…

You can see the issue with FIOS and WinMTR described here:

https://forums.verizon.com/t5/fios-internet/tracert-broken/m-p/896349

https://www.reddit.com/r/HomeNetworking/comments/9kae1k/winmtr_isnt_showing_intermediate_hops_why_is_this/

|------------------------------------------------------------------------------------------|

|                                      WinMTR statistics                                   |

|                       Host              -   %  | Sent | Recv | Best | Avrg | Wrst | Last |

|------------------------------------------------|------|------|------|------|------|------|

|                             192.168.1.1 -    0 |  353 |  353 |    0 |    0 |   30 |    0 |

|                           24.105.46.225 -    0 |  353 |  353 |    1 |    4 |   64 |    4 |

|________________________________________________|______|______|______|______|______|______|

   WinMTR v0.92 GPL V2 by Appnor MSP - Fully Managed Hosting & Cloud Provider

A recommended tool from Verizon is PingPlotter… I’ve ran the scan and below are the results…

https://share.pingplotter.com/CAmZasmSH5V.png

5

PingPlotter is showing a max ping of 54.90ms, but you only ran it for 72 seconds. It could be that the connection issue is happening less frequently than the test is sending packets. And it could also be that the issue is on the local hardware, like the network card.

6

Yes, I only ran it for 72 seconds just to show the issue is there. I just played 1 complete game on Hanamura for 7 minutes and here are the results:

https://share.pingplotter.com/MBVnpEFscpu

This happens on my PC as well as my 2 childrens, with and without a router and with ethernet and WiFI. We don’t use Wifi ever, but I did just to test to elimate the NIC card.
A neighbor a block away on FIOS has the same issue

edit - I was escalated to Verizon engineering and there response was:

" You can pinpoint what server is causing the lag/spike/latency by doing an IP address lookup.

For example in your first set of traceroute results ping 7 IP address 137.221.71.33 is where the latency starts if you look up that IP address (»[whatismyipaddress.com/ip-lookup](https://whatismyipaddress.com/ip-lookup)) that is going from Blizzard Entertainment Inc.

We do not have a way of controlling any spikes or latency on none Verizon servers, but based on the traceroute results you have provided here all the issues are coming from non Verizon servers."

1 Like
7

Those pings look good; the average is 50.3ms, max is 59.55ms.

You can’t measure the connection off one Blizzard hop. Most of them are designed to ignore external pings via ICMP or UDP as a DDoS protection mechanism.

I recommend trying a VPN and seeing if the connection improves. If it does, then it’s liking a routing problem, which just requires waiting for ISP and routing peer to figure things out.

8

But there is severe packet loss on all Blizzard servers… But ok, thanks for your help!

Have a good day.

9

As I mentioned already, Blizzard servers ignore these tests, which inflates their response time. You cannot use them to measure connection quality.

10

I’m having the exact same packet loss/connectivity issues for the past week and nothing has changed on my end. Only happens during the day, goes back to normal when it’s late at night. No other games have issues (WoW, Warzone etc) so it must be an Overwatch thing.

11

Same here with FIOS in NYC for the last week or so. Routing through cloudflare warp in the meantime.

edit: just saw your post on dslreports.

2 Likes
12

If the roads leading to your grocery store have an accident blocking them, is it the grocery store’s fault? All games use different routes from your home and are not hosted in the same buildings, cities, or states. A problem with one route doesn’t mean the end server is to blame.

13

From your previous posts it sounds like you’ll try everything in your power to blame the person and not admit there is an actual problem with the servers recently. Almost every game I join there’s other people experiencing the exact same issue so even though that’s a wonderful analogy, that is not the case in this situation.

1 Like
14

I don’t work at Blizzard and have no monetary or positioning reason to defend their servers. However, the majority of people experiencing problems are using similar routes. This happens everywhere in the world. All major ISPs share just a handful of routing peers, so if the routing peer has an issue, the customers of 10+ ISPs do also. The situation is more pronounced in countries where only 1–2 companies route traffic outside borders.

15

With that analogy, an accident blocking a road will only cause an issue for a few hours, absolute 24 hours tops…

This has been going on for well over a week for a lot of people, on various forums, on servers that are ran, owned or paid for by Blizzard… There is an obvious issue, so why isn’t it being addressed by Blizzard?

The game is old, yes, but we still paid for it… The obvious connection issues are all on Blizzard servers… I shouldn’t have to pay for a VPN to go back to the way I’ve played the game for the past 5 years…

16

There is no data here demonstrating an obvious issue on Blizzard servers. Instead, there is a misunderstanding on how to read these test results. If the server was having an issue, all players would be experiencing it, but they’re simply not.

17

Either way, looks like it’s finally resolved today.

18

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.