[Verizon] Random high ping wont go down

Technical Support
1

Hey guys, so, I generally play OW on about 37ms, and I was playing at 37ms all night up until about 9-10am which is when my ping rose up to about 140-160ms (100% playable, but as a doom player this is is a fun latency to play with…)

I’ve tried all the normal suggestions, reboot router, restart pc, checked for driver updates, the whole general non complicated stuff, I read an a few articles on how to fix this, and one of them sayd go to battle net looking glass, and to post the following here to see if someone more technically inclined than I am can see what the problem is…

First Results (yesterday 8/25)

TRACEROUTE:
traceroute to 72.90.82.103 (72.90.82.103), 15 hops max, 60 byte packets
 1  Blizzard Blizzard  0.330 ms  0.286 ms  0.281 ms
 2  24.105.18.2 (24.105.18.2)  13.881 ms  14.116 ms  14.118 ms
 3  137.221.105.10 (137.221.105.10)  0.987 ms  0.986 ms  0.984 ms
 4  137.221.66.16 (137.221.66.16)  0.945 ms  0.957 ms  0.956 ms
 5  137.221.83.80 (137.221.83.80)  924.131 ms  924.156 ms  924.158 ms
 6  * * *
 7  137.221.68.32 (137.221.68.32)  23.253 ms  23.247 ms  23.239 ms
 8  4-1-3.ear3.LosAngeles1.Level3.net (4.71.135.105)  5.630 ms  5.638 ms  5.634 ms
 9  ae-1-3501.edge7.LosAngeles1.Level3.net (4.69.219.41)  5.917 ms  5.501 ms  5.486 ms
10  TWC-level3-40G.Miami.Level3.net (4.68.62.182)  5.542 ms  5.683 ms  5.751 ms
11  ae203-0.SYRCNY-VFTTP-304.verizon-gni.net (100.41.198.203)  179.790 ms  179.800 ms  179.798 ms
12  pool-72-90-82-103.syrcny.fios.verizon.net (72.90.82.103)  179.384 ms  181.661 ms  181.707 ms


25/08/2020 16:55:12 UTC
--------------------

TRACEROUTE:
traceroute to 72.90.82.103 (72.90.82.103), 15 hops max, 60 byte packets
 1  Blizzard Blizzard  0.286 ms  0.335 ms  0.358 ms
 2  37.244.23.131 (37.244.23.131)  0.570 ms  0.605 ms  0.689 ms
 3  24.105.62.152 (24.105.62.152)  0.722 ms  0.733 ms  0.845 ms
 4  137.221.66.10 (137.221.66.10)  1.933 ms  1.958 ms  1.961 ms
 5  * * *
 6  137.221.69.32 (137.221.69.32)  4.335 ms  3.025 ms  5.047 ms
 7  7-1-4.ear7.Chicago2.Level3.net (4.7.196.133)  2.332 ms  2.391 ms  2.374 ms
 8  ae-1-3504.ear6.Chicago2.Level3.net (4.69.217.234)  2.365 ms  2.322 ms  2.287 ms
 9  Verizon-level3-Chicago2.Level3.net (4.68.37.186)  2.247 ms  2.484 ms  2.455 ms
10  ae204-0.SYRCNY-VFTTP-304.verizon-gni.net (100.41.213.245)  132.826 ms  132.827 ms  133.007 ms
11  pool-72-90-82-103.syrcny.fios.verizon.net (72.90.82.103)  137.814 ms  137.844 ms  137.860 ms

25/08/2020 16:55:12 UTC
--------------------

PING:
PING 72.90.82.103 (72.90.82.103) 56(84) bytes of data.
64 bytes from 72.90.82.103: icmp_seq=1 ttl=45 time=187 ms
64 bytes from 72.90.82.103: icmp_seq=2 ttl=45 time=179 ms
64 bytes from 72.90.82.103: icmp_seq=3 ttl=45 time=180 ms
64 bytes from 72.90.82.103: icmp_seq=4 ttl=45 time=180 ms

--- 72.90.82.103 ping statistics ---
4 packets transmitted, 4 received, 0% packet loss, time 2997ms
rtt min/avg/max/mdev = 179.030/181.904/187.575/3.342 ms


25/08/2020 16:55:12 UTC
--------------------

PING:
PING 72.90.82.103 (72.90.82.103) 56(84) bytes of data.
64 bytes from 72.90.82.103: icmp_seq=1 ttl=46 time=140 ms
64 bytes from 72.90.82.103: icmp_seq=2 ttl=46 time=136 ms
64 bytes from 72.90.82.103: icmp_seq=3 ttl=46 time=135 ms
64 bytes from 72.90.82.103: icmp_seq=4 ttl=46 time=137 ms

--- 72.90.82.103 ping statistics ---
4 packets transmitted, 4 received, 0% packet loss, time 2998ms
rtt min/avg/max/mdev = 135.711/137.562/140.355/1.735 ms


25/08/2020 16:55:12 UTC
--------------------

MTR:
Start: Tue Aug 25 16:55:12 2020 Blizzard  1.|-- Blizzard                               0.0%    10    0.3   0.3   0.2   0.4   0.0
  2.|-- 24.105.18.2                                0.0%    10    0.6   4.5   0.6  22.8   7.1
  3.|-- 137.221.105.10                             0.0%    10    1.1   1.4   0.7   5.1   1.2
  4.|-- 137.221.66.16                              0.0%    10    0.6   0.6   0.4   0.8   0.0
  5.|-- 137.221.83.80                              0.0%    10  121.7 502.0  64.0 1065. 391.2
  6.|-- ???                                       100.0    10    0.0   0.0   0.0   0.0   0.0
  7.|-- 137.221.68.32                              0.0%    10    5.8   7.1   5.8  16.6   3.3
  8.|-- 4-1-3.ear3.LosAngeles1.Level3.net          0.0%    10    5.4   5.6   5.4   5.9   0.0
  9.|-- ae-1-3501.edge7.LosAngeles1.Level3.net     0.0%    10   10.4   6.5   5.5  10.4   1.4
 10.|-- TWC-level3-40G.Miami.Level3.net            0.0%    10    5.8   5.7   5.6   5.9   0.0
 11.|-- ae203-0.SYRCNY-VFTTP-304.verizon-gni.net   0.0%    10  179.8 190.3 179.6 240.0  21.9
 12.|-- pool-72-90-82-103.syrcny.fios.verizon.net  0.0%    10  181.1 180.0 179.2 181.1   0.7


25/08/2020 16:55:12 UTC
--------------------

MTR:
Start: Tue Aug 25 16:55:12 2020 Blizzard  1.|-- Blizzard                              0.0%    10    0.3   0.4   0.3   0.6   0.0
  2.|-- 37.244.23.131                              0.0%    10    0.5   0.6   0.5   0.9   0.0
  3.|-- 24.105.62.152                              0.0%    10    1.0   0.9   0.8   1.1   0.0
  4.|-- 137.221.66.10                              0.0%    10    2.0   7.4   1.9  56.7  17.3
  5.|-- ???                                       100.0    10    0.0   0.0   0.0   0.0   0.0
  6.|-- 137.221.69.32                              0.0%    10    2.8   4.2   2.4  18.8   5.1
  7.|-- 7-1-4.ear7.Chicago2.Level3.net             0.0%    10    2.1   2.2   2.1   2.4   0.0
  8.|-- ae-1-3504.ear6.Chicago2.Level3.net        90.0%    10    2.3   2.3   2.3   2.3   0.0
  9.|-- Verizon-level3-Chicago2.Level3.net         0.0%    10    1.9   2.3   1.9   3.1   0.0
 10.|-- ae204-0.SYRCNY-VFTTP-304.verizon-gni.net   0.0%    10  132.1 132.6 131.5 134.5   0.7
 11.|-- pool-72-90-82-103.syrcny.fios.verizon.net  0.0%    10  137.5 136.8 135.8 138.1   0.5


25/08/2020 16:55:12 UTC
--------------------

Second set of results (Today 8/26)

TRACEROUTE:
traceroute to 72.90.82.103 (72.90.82.103), 15 hops max, 60 byte packets
 1  Blizzard Blizzard  0.245 ms  0.241 ms  0.286 ms
 2  24.105.18.2 (24.105.18.2)  1.066 ms  1.065 ms  1.074 ms
 3  137.221.105.10 (137.221.105.10)  1.075 ms  1.075 ms  1.074 ms
 4  137.221.66.16 (137.221.66.16)  0.995 ms  1.011 ms  1.011 ms
 5  137.221.83.80 (137.221.83.80)  1530.777 ms  1530.802 ms  1530.834 ms
 6  * * *
 7  137.221.68.32 (137.221.68.32)  37.471 ms  37.476 ms  37.478 ms
 8  4-1-3.ear3.LosAngeles1.Level3.net (4.71.135.105)  5.434 ms  5.545 ms  5.530 ms
 9  ae-1-3501.edge7.LosAngeles1.Level3.net (4.69.219.41)  5.762 ms  6.168 ms  6.168 ms
10  TWC-level3-40G.Miami.Level3.net (4.68.62.182)  6.120 ms  6.113 ms  6.143 ms
11  ae203-0.SYRCNY-VFTTP-304.verizon-gni.net (100.41.198.203)  172.309 ms  172.311 ms  172.043 ms
12  pool-72-90-82-103.syrcny.fios.verizon.net (72.90.82.103)  171.721 ms  172.604 ms  172.601 ms


26/08/2020 21:01:41 UTC
--------------------

TRACEROUTE:
traceroute to 72.90.82.103 (72.90.82.103), 15 hops max, 60 byte packets
 1  Blizzard Blizzard  0.297 ms  0.314 ms  0.344 ms
 2  37.244.23.131 (37.244.23.131)  0.700 ms  0.727 ms  0.736 ms
 3  24.105.62.152 (24.105.62.152)  0.967 ms  0.978 ms  0.985 ms
 4  137.221.66.10 (137.221.66.10)  2.058 ms  2.088 ms  2.093 ms
 5  * * *
 6  137.221.69.32 (137.221.69.32)  4.720 ms  3.184 ms  3.342 ms
 7  7-1-4.ear7.Chicago2.Level3.net (4.7.196.133)  2.396 ms  2.318 ms  2.347 ms
 8  * * *
 9  Verizon-level3-Chicago2.Level3.net (4.68.37.186)  2.083 ms  2.390 ms  2.384 ms
10  ae204-0.SYRCNY-VFTTP-304.verizon-gni.net (100.41.213.245)  135.090 ms  135.123 ms  135.123 ms
11  * pool-72-90-82-103.syrcny.fios.verizon.net (72.90.82.103)  142.037 ms  142.045 ms


26/08/2020 21:01:41 UTC
--------------------

PING:
PING 72.90.82.103 (72.90.82.103) 56(84) bytes of data.
64 bytes from 72.90.82.103: icmp_seq=1 ttl=45 time=142 ms
64 bytes from 72.90.82.103: icmp_seq=2 ttl=45 time=140 ms
64 bytes from 72.90.82.103: icmp_seq=3 ttl=45 time=142 ms
64 bytes from 72.90.82.103: icmp_seq=4 ttl=45 time=142 ms

--- 72.90.82.103 ping statistics ---
4 packets transmitted, 4 received, 0% packet loss, time 2999ms
rtt min/avg/max/mdev = 140.648/141.852/142.293/0.745 ms


26/08/2020 21:01:41 UTC
--------------------

PING:
PING 72.90.82.103 (72.90.82.103) 56(84) bytes of data.
64 bytes from 72.90.82.103: icmp_seq=1 ttl=44 time=173 ms
64 bytes from 72.90.82.103: icmp_seq=2 ttl=44 time=173 ms
64 bytes from 72.90.82.103: icmp_seq=3 ttl=44 time=172 ms
64 bytes from 72.90.82.103: icmp_seq=4 ttl=44 time=172 ms

--- 72.90.82.103 ping statistics ---
4 packets transmitted, 4 received, 0% packet loss, time 2999ms
rtt min/avg/max/mdev = 172.237/173.041/173.873/0.657 ms


26/08/2020 21:01:41 UTC
--------------------

MTR:
Start: Wed Aug 26 21:01:40 2020 Blizzard  1.|-- Blizzard                               0.0%    10    0.3   0.3   0.3   0.4   0.0
  2.|-- 24.105.18.2                                0.0%    10    0.6   3.8   0.6  25.7   7.8
  3.|-- 137.221.105.10                             0.0%    10    0.9   1.2   0.8   3.3   0.7
  4.|-- 137.221.66.16                              0.0%    10    0.5   3.0   0.3  25.4   7.9
  5.|-- 137.221.83.80                              0.0%    10  608.7 627.9  72.2 1354. 446.2
  6.|-- ???                                       100.0    10    0.0   0.0   0.0   0.0   0.0
  7.|-- 137.221.68.32                              0.0%    10   55.8  12.3   5.7  55.8  15.7
  8.|-- 4-1-3.ear3.LosAngeles1.Level3.net          0.0%    10    5.6   5.6   5.4   5.7   0.0
  9.|-- ae-1-3501.edge7.LosAngeles1.Level3.net     0.0%    10   14.5   6.5   5.6  14.5   2.8
 10.|-- TWC-level3-40G.Miami.Level3.net            0.0%    10    5.7   5.7   5.5   5.9   0.0
 11.|-- ae203-0.SYRCNY-VFTTP-304.verizon-gni.net   0.0%    10  172.5 172.6 171.4 175.9   1.2
 12.|-- pool-72-90-82-103.syrcny.fios.verizon.net  0.0%    10  172.8 172.5 171.1 174.8   0.9


26/08/2020 21:01:40 UTC
--------------------

MTR:
Start: Wed Aug 26 21:01:41 2020 Blizzard  1.|-- Blizzard                              0.0%    10    0.4   0.4   0.3   0.5   0.0
  2.|-- 37.244.23.131                              0.0%    10    0.4   0.6   0.4   0.7   0.0
  3.|-- 24.105.62.152                              0.0%    10    1.0   1.0   0.8   1.1   0.0
  4.|-- 137.221.66.10                              0.0%    10    2.0   2.0   1.9   2.2   0.0
  5.|-- ???                                       100.0    10    0.0   0.0   0.0   0.0   0.0
  6.|-- 137.221.69.32                              0.0%    10    2.4   6.1   2.4  33.7   9.8
  7.|-- 7-1-4.ear7.Chicago2.Level3.net             0.0%    10    2.2   2.3   2.1   3.3   0.0
  8.|-- ae-1-3504.ear6.Chicago2.Level3.net        80.0%    10    2.3   2.3   2.3   2.3   0.0
  9.|-- Verizon-level3-Chicago2.Level3.net         0.0%    10    2.4   3.0   2.1  10.0   2.4
 10.|-- ae204-0.SYRCNY-VFTTP-304.verizon-gni.net   0.0%    10  135.4 136.7 134.0 138.2   1.1
 11.|-- pool-72-90-82-103.syrcny.fios.verizon.net  0.0%    10  141.7 141.8 140.8 142.6   0.3


26/08/2020 21:01:41 UTC
--------------------

The first round of tests are results from yesterday… the problem seemed to have resolved its self around 6:30pm… but when I woke up at 4pm today, the ping is the same, if not worse today… Todays Looking Glass results will be the second one.

And, yet another edit… I posted this as a reply, but just so people don’t have to search for is down there… The issue seems to be with the ISP (internet service provider) specifically verizon… I called and ended up getting hung up on… twice…

But from what I can tell, you can temporarily resolve the issue with a VPN, my norton security package comes with a VPN, but some free ones I would recommend, are Speedify VPN, ProtonVPN, and Hotspot Shield VPN.

These services have both paid and free versions, but the free one will work just fine since they try to connect you to their nearest server.

Yet another edit, because the issue seems to be resolved, yet again… Long story short, ping was fine until 9/10am on 8/25, when it went up to 150-160ms, then went back down to 40-50 at 6-7pm on 8/25… Then today 8/26 I saw someone say ping went down at 9/10am again, I ran a Looking Glass test at about 5pm, and results showed high ping again, 150-160ms. Ran another Looking Glass tes at around 6:30pm, and had about 50-60ms latency again. 8/26

The following results are from 8/26 6:30pm

TRACEROUTE:
traceroute to 72.90.82.103 (72.90.82.103), 15 hops max, 60 byte packets
 1  Blizzard Blizzard  0.466 ms  0.459 ms  0.458 ms
 2  24.105.18.2 (24.105.18.2)  0.582 ms  0.617 ms  0.725 ms
 3  137.221.105.10 (137.221.105.10)  0.926 ms  0.982 ms  0.993 ms
 4  137.221.66.16 (137.221.66.16)  0.633 ms  0.644 ms  0.645 ms
 5  137.221.83.80 (137.221.83.80)  305.495 ms  305.518 ms  305.523 ms
 6  * * *
 7  137.221.68.32 (137.221.68.32)  8.528 ms  7.536 ms  7.695 ms
 8  4-1-3.ear3.LosAngeles1.Level3.net (4.71.135.105)  7.039 ms  7.067 ms  7.052 ms
 9  ae-1-3501.edge7.LosAngeles1.Level3.net (4.69.219.41)  11.429 ms  8.906 ms  8.880 ms
10  TWC-level3-40G.Miami.Level3.net (4.68.62.182)  5.837 ms  5.541 ms  5.516 ms
11  ae203-0.SYRCNY-VFTTP-304.verizon-gni.net (100.41.198.203)  66.579 ms  66.596 ms  66.544 ms
12  pool-72-90-82-103.syrcny.fios.verizon.net (72.90.82.103)  68.092 ms  66.540 ms  68.053 ms


26/08/2020 22:29:43 UTC
--------------------

PING:
PING 72.90.82.103 (72.90.82.103) 56(84) bytes of data.
64 bytes from 72.90.82.103: icmp_seq=1 ttl=45 time=67.3 ms
64 bytes from 72.90.82.103: icmp_seq=2 ttl=45 time=66.1 ms
64 bytes from 72.90.82.103: icmp_seq=3 ttl=45 time=66.1 ms
64 bytes from 72.90.82.103: icmp_seq=4 ttl=45 time=66.8 ms

--- 72.90.82.103 ping statistics ---
4 packets transmitted, 4 received, 0% packet loss, time 2998ms
rtt min/avg/max/mdev = 66.136/66.617/67.335/0.593 ms


26/08/2020 22:29:43 UTC
--------------------

MTR:
Start: Wed Aug 26 22:29:43 2020 Blizzard  1.|-- Blizzard                               0.0%    10    0.3   0.3   0.2   0.4   0.0
  2.|-- 24.105.18.2                                0.0%    10    0.6   0.6   0.4   1.4   0.0
  3.|-- 137.221.105.10                             0.0%    10    0.8   0.8   0.7   1.1   0.0
  4.|-- 137.221.66.16                              0.0%    10    0.5   1.9   0.3  15.4   4.7
  5.|-- 137.221.83.80                              0.0%    10  546.4 662.4 194.8 1241. 407.6
  6.|-- ???                                       100.0    10    0.0   0.0   0.0   0.0   0.0
  7.|-- 137.221.68.32                              0.0%    10   47.9  10.3   5.7  47.9  13.2
  8.|-- 4-1-3.ear3.LosAngeles1.Level3.net          0.0%    10    5.7   5.5   5.3   5.8   0.0
  9.|-- ae-1-3501.edge7.LosAngeles1.Level3.net     0.0%    10    5.6   6.9   5.6  12.6   2.4
 10.|-- TWC-level3-40G.Miami.Level3.net            0.0%    10    5.8   6.9   5.6  17.9   3.8
 11.|-- ae203-0.SYRCNY-VFTTP-304.verizon-gni.net   0.0%    10   66.9  66.9  66.7  67.2   0.0
 12.|-- pool-72-90-82-103.syrcny.fios.verizon.net  0.0%    10   66.2  66.7  66.0  67.7   0.0


26/08/2020 22:29:43 UTC
--------------------

I am sorry for the edit spam, if a forum moderator / dev would like me to stop, let me know, but I figured I should edit saying this is the 2nd day in a row that latency went up around 9-10am and went down again between 6-7pm…

2

Im having the exact same problem today. Are you on Verizon FIOS by chance?

1 Like
3

Yeah I’m on verizon too Eph and I’m having the same issues

4

I don’t know if it’s because of OW or the wifi itself

5

alright, so verison seems to be having trouble then, I’ve been sitting here trying legit everything (and I mean EVERYTHING) to fix it on my end, but its not even my problem lol

6

Yep same here 147 ms on verizon

7

Ah! I just posted about this - On Verizon FIOS as well! Glad that it is not just me.

I left my thread up so hopefully if anyone else is running issues they could see it as well.

8

FYI all - on Verizon, it may be trying to put you on SAE1 servers (Brazil) so. That could be it. Although even when it placed me on Ord1 (Chicago), i still saw the high ping.

9

Yes sa servers for some reason

10

I’m on Verizon FIOS and live in US East as well and have been having latency issues with only Blizzard games this past week.

1 Like
11

Verizon Fios here as well, east coast. Mine was fine last night but logged on this afternoon to play and initially got put on sa1. Restarted and forced a ord1 connection and it still connected to lax1. Ran a ping on the ord1 server and all packets were lost. Restarted computer and router, managed to get into a ord1 server but ping still near 180ms.

12

Still the same for me. I wonder when it will start to get fixed. Is this a Blizzard problem with Verizon, or is this a Verizon only problem? I don’t seem to have any issues with non-blizzard related things.

13

Had this issue last week and now it’s come back. Really sucks.

I have Cox Communcations.

EDIT:
According to Ping Plotter if you’re playing in the west coast (24.105.30.129) we are being dumped off to Atlanta servers (68.105.30.130, 68.1.4.252) which would explain the high ping? Unless I misunderstood.

https://imgur.com/VXh0SfK

14

I mean, I don’t know about anyone else on here, but I’m on NA east.

The one thing we all have in common though is verizon fios, so I’m going to assume its something on their end.

15

They’re one again have severe server issues. It’s been ongoing for a couple weeks now from one of their updates, or they had servers crash and didn’t tell anyone, or something.

16

I’m on NA east too and never had issues up until a couple weeks ago with high ping and loss of connection b/c of it

17

hopefully they fix the issue

18

maybe next week at this point lol they’re really bad at letting people know when they have issues. typical blizzard style

19

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.

20

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