so i have verizon and i am trying to play overwatch but i am getting 70-120 ping when i should have around 34-42. My internet is fine i did a speedtest and these are the results, 752.30 Download / 941.90 Upload. Since it cant be my internet i am lost at this point. If anyone else is having this problem, know whats happening, and know a fix please help me.
That’s the first I’ve heard of it from a member of your ISP. Can you run a winMTR during a game and post the results here? Make sure to use the game IP address from your netgraph (ctrl+shift+N) to run the test. If you get a link error, you can just post it between two ` marks (same key as the tilde).
Looks like this when done right
Other than that, how long have you had the problem?
I’m actually having the same issue with the high latency. I usually get around the low 30s-40s as well.
I have Verizon as well. Have had the same issue with high latency for 2 days. Ran the winmtr with the Ip from the netgraph in game and i’m getting a “no response from host”.
Hey folks,
We actually saw a couple different reports of this recently, can you try a traceroute instead?
Tracing route to 24.105.45.112 over a maximum of 30 hops
1 <1 ms <1 ms <1 ms Fios_Quantum_Gateway.fios-router.home
2 2 ms 1 ms 1 ms 24.105.45.112
Trace complete.
Same issue except for the fact that I might be doing the traceroute incorrectly or it is just not working.
I’m having the same problem, latency is nearly triple what it usually is
Tracing route to 24.105.45.30 over a maximum of 30 hops
1 1 ms 1 ms <1 ms Fios_Quantum_Gateway.fios-router.home
2 11 ms 11 ms 11 ms 24.105.45.30
Trace complete.
Thanks for the tests everyone! It looks like the tests may be a bit weird due to the IPv6 backbone with Verizon. We may be able to gather some more information with a Looking Glass test to check out our network to the system.
TRACEROUTE:
traceroute to 108.16.135.194 (108.16.135.194), 15 hops max, 60 byte packets
1 Blizzard Blizzard 0.250 ms 0.260 ms 0.263 ms
2 24.105.18.131 (24.105.18.131) 0.520 ms 0.721 ms 0.785 ms
3 137.221.105.16 (137.221.105.16) 0.762 ms 0.789 ms 2.538 ms
4 137.221.66.22 (137.221.66.22) 1.611 ms 1.646 ms 1.655 ms
5 137.221.83.68 (137.221.83.68) 6.290 ms 6.324 ms 6.331 ms
6 137.221.65.68 (137.221.65.68) 6.336 ms 7.469 ms 7.455 ms
7 137.221.68.32 (137.221.68.32) 7.241 ms 6.179 ms 6.171 ms
8 xe-9-3-0.edge2.LosAngeles9.Level3 net (4.53.230.237) 24.318 ms 22.927 ms 22.895 ms
9 * * *
10 Verizon-level3-50G.LosAngeles1.Level3 net (4.68.62.170) 5.880 ms 5.662 ms 5.682 ms
11 * * *
12 ae203-0.PHLAPA-VFTTP-371.verizon-gni net (100.41.13.85) 132.341 ms 132.193 ms 132.376 ms
13 pool-108-16-135-194.phlapa.fios.verizon net (108.16.135.194) 140.298 ms 137.793 ms 137.307 ms
17/03/2019 02:27:37 UTC
MTR:
Start: Sun Mar 17 02:27:37 2019 Blizzard 1.|-- Blizzard 0.0% 10 0.3 0.3 0.3 0.5 0.0
2.|-- 24.105.18.131 0.0% 10 0.6 0.9 0.6 2.5 0.5
3.|-- 137.221.105.16 0.0% 10 0.7 0.7 0.6 0.9 0.0
4.|-- 137.221.66.22 0.0% 10 0.7 1.0 0.7 3.1 0.5
5.|-- 137.221.83.68 0.0% 10 5.0 17.4 1.8 120.0 36.5
6.|-- 137.221.65.68 0.0% 10 6.0 6.0 5.8 6.2 0.0
7.|-- 137.221.68.32 0.0% 10 5.6 8.4 5.6 21.4 4.9
8.|-- xe-9-3-0.edge2.LosAngeles9.Level3 net 0.0% 10 5.4 5.8 5.4 6.5 0.0
9.|-- ae-1-51.ear3.LosAngeles1.Level3 net 90.0% 10 960.9 960.9 960.9 960.9 0.0
10.|-- Verizon-level3-50G.LosAngeles1.Level3 net 0.0% 10 5.7 5.7 5.6 5.7 0.0
11.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0
12.|-- ae203-0.PHLAPA-VFTTP-371.verizon-gni net 0.0% 10 144.3 142.1 130.2 153.3 7.1
13.|-- pool-108-16-135-194.phlapa.fios.verizon net 0.0% 10 148.8 147.3 138.2 157.3 5.6
17/03/2019 02:27:37 UTC
Hope this is resolvable because it makes the game pretty much unplayable. Thanks to anyone who helps to solve this issue, you are all lifesavers!
Thanks, BunnyBanner! We are seeing a high jump in latency here.
Currently, we’re tracking and gathering information. If anyone else is running into the issue, please include the Looking Glass test requested!
TRACEROUTE:
traceroute to 100.19.67.90 (100.19.67.90), 15 hops max, 60 byte packets
1 Blizzard Blizzard 2.718 ms 2.715 ms 2.715 ms Blizzard(24.105.18.3) 3.049 ms 3.100 ms 3.247 ms
3 137.221.105.12 (137.221.105.12) 3.400 ms 3.412 ms 3.427 ms
4 137.221.66.16 (137.221.66.16) 3.408 ms 3.407 ms 3.406 ms
5 137.221.83.66 (137.221.83.66) 410.402 ms 631.557 ms 631.583 ms
6 * * *
7 137.221.68.32 (137.221.68.32) 5.595 ms 5.585 ms 5.659 ms
8 xe-9-3-0.edge2.LosAngeles9.Level3.ne (4.53.230.237) 5.372 ms 5.465 ms 5.435 ms
9 * * *
10 Verizon-level3-50G.LosAngeles1.Level3.ne (4.68.62.170) 5.397 ms 5.423 ms 5.354 ms
11 * * *
12 ae204-0.PHLAPA-VFTTP-382.verizon-gni.ne (100.41.129.165) 98.667 ms 98.699 ms 99.043 ms
13 pool-100-19-67-90.phlapa.fios.verizon.ne (100.19.67.90) 99.240 ms 100.190 ms 100.190 ms
17/03/2019 17:17:44 UTC
TRACEROUTE:
traceroute to 100.19.67.90 (100.19.67.90), 15 hops max, 60 byte packets
1 Blizzard Blizzard 8.848 ms 8.842 ms 8.845 ms
2 24.105.18.131 (24.105.18.131) 3.516 ms 3.545 ms 3.552 ms
3 137.221.105.12 (137.221.105.12) 8.833 ms 8.840 ms 8.896 ms
4 137.221.66.20 (137.221.66.20) 8.841 ms 8.857 ms 8.866 ms
5 137.221.83.68 (137.221.83.68) 382.627 ms 605.752 ms 605.847 ms
6 * * *
7 137.221.68.32 (137.221.68.32) 9.851 ms 6.856 ms 7.007 ms
8 xe-9-3-0.edge2.LosAngeles9.Level3.ne (4.53.230.237) 5.758 ms 6.020 ms 6.159 ms
9 * * *
10 Verizon-level3-50G.LosAngeles1.Level3.ne (4.68.63.246) 5.629 ms 5.589 ms 5.445 ms
11 * * *
12 ae204-0.PHLAPA-VFTTP-382.verizon-gni.ne (100.41.129.165) 102.905 ms 102.409 ms 102.395 ms
13 pool-100-19-67-90.phlapa.fios.verizon.ne (100.19.67.90) 102.661 ms 102.543 ms 102.721 ms
17/03/2019 17:17:44 UTC
PING:
PING 100.19.67.90 (100.19.67.90) 56(84) bytes of data.
64 bytes from 100.19.67.90: icmp_seq=1 ttl=49 time=100 ms
64 bytes from 100.19.67.90: icmp_seq=2 ttl=49 time=98.6 ms
64 bytes from 100.19.67.90: icmp_seq=3 ttl=49 time=99.8 ms
64 bytes from 100.19.67.90: icmp_seq=4 ttl=49 time=104 ms
— 100.19.67.90 ping statistics —
4 packets transmitted, 4 received, 0% packet loss, time 2998ms
rtt min/avg/max/mdev = 98.629/100.910/104.305/2.151 ms
17/03/2019 17:17:44 UTC
PING:
PING 100.19.67.90 (100.19.67.90) 56(84) bytes of data.
64 bytes from 100.19.67.90: icmp_seq=1 ttl=49 time=109 ms
64 bytes from 100.19.67.90: icmp_seq=2 ttl=49 time=99.5 ms
64 bytes from 100.19.67.90: icmp_seq=3 ttl=49 time=99.5 ms
64 bytes from 100.19.67.90: icmp_seq=4 ttl=49 time=104 ms
— 100.19.67.90 ping statistics —
4 packets transmitted, 4 received, 0% packet loss, time 2998ms
rtt min/avg/max/mdev = 99.526/103.374/109.818/4.249 ms
17/03/2019 17:17:44 UTC
MTR:
Start: Sun Mar 17 17:17:44 2019 Blizzard 1.|-- Blizzard 0.0% 10 0.2 0.3 0.2 0.3 0.0 Blizzard 0.0% 10 0.7 0.7 0.5 1.1 0.0
3.|-- 137.221.105.12 0.0% 10 0.7 0.9 0.5 2.6 0.6
4.|-- 137.221.66.16 0.0% 10 0.7 0.6 0.6 0.7 0.0
5.|-- 137.221.83.66 0.0% 10 326.0 219.4 32.7 745.5 206.5
6.|-- 137.221.65.68 20.0% 10 7588. 9812. 7588. 11704 1460.6
7.|-- 137.221.68.32 0.0% 10 9.8 6.1 5.4 9.8 1.3
8.|-- xe-9-3-0.edge2.LosAngeles9.Level3.ne 0.0% 10 5.4 7.4 5.4 24.7 6.1
9.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0
10.|-- Verizon-level3-50G.LosAngeles1.Level3.ne 0.0% 10 6.2 5.9 5.4 8.4 0.7
11.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0
12.|-- ae204-0.PHLAPA-VFTTP-382.verizon-gni.ne 0.0% 10 99.0 102.9 98.8 107.6 3.3
13.|-- pool-100-19-67-90.phlapa.fios.verizon.ne 0.0% 10 99.2 103.6 99.2 106.4 2.4
17/03/2019 17:17:44 UTC
MTR:
Start: Sun Mar 17 17:17:44 2019 Blizzard 1.|-- Blizzard 0.0% 10 0.3 0.3 0.2 0.4 0.0
2.|-- 24.105.18.131 0.0% 10 0.5 0.6 0.5 1.0 0.0
3.|-- 137.221.105.12 0.0% 10 0.6 0.7 0.5 1.3 0.0
4.|-- 137.221.66.20 0.0% 10 0.5 1.7 0.5 8.6 2.4
5.|-- 137.221.83.68 0.0% 10 151.9 186.8 50.8 616.0 159.9
6.|-- 137.221.65.68 20.0% 10 7414. 9704. 7414. 11794 1512.3
7.|-- 137.221.68.32 0.0% 10 5.6 6.0 5.5 10.4 1.4
8.|-- xe-9-3-0.edge2.LosAngeles9.Level3.ne 0.0% 10 5.5 5.6 5.4 6.1 0.0
9.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0
10.|-- Verizon-level3-50G.LosAngeles1.Level3.ne 0.0% 10 5.6 5.6 5.5 5.7 0.0
11.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0
12.|-- ae204-0.PHLAPA-VFTTP-382.verizon-gni.ne 0.0% 10 101.2 103.8 100.3 107.4 2.2
13.|-- pool-100-19-67-90.phlapa.fios.verizon.ne 0.0% 10 102.2 103.4 101.1 105.8 1.3
17/03/2019 17:17:44 UTC
I have the same issue. Verizon FIOS in Philadelphia lol
the problem was gone all of today until about 6ish, then it was back, and worse than before
TRACEROUTE:
traceroute to 108.16.135.194 (108.16.135.194), 15 hops max, 60 byte packets
1 Blizzard Blizzard 3.031 ms 2.990 ms 2.986 ms
2 24.105.18.131 (24.105.18.131) 2.203 ms 2.207 ms 2.211 ms
3 137.221.105.16 (137.221.105.16) 2.192 ms 2.195 ms 2.209 ms
4 137.221.66.22 (137.221.66.22) 2.973 ms 2.973 ms 2.974 ms
5 137.221.83.68 (137.221.83.68) 5.031 ms 5.031 ms 5.032 ms
6 137.221.65.68 (137.221.65.68) 6.744 ms 6.694 ms 6.673 ms
7 137.221.68.32 (137.221.68.32) 6.078 ms 6.627 ms 6.635 ms
8 xe-9-3-0.edge2.LosAngeles9.Level3 net (4.53.230.237) 6.129 ms 5.898 ms 5.880 ms
9 * * *
10 Verizon-level3-50G.LosAngeles1.Level3 net (4.68.62.170) 5.528 ms 5.618 ms 5.602 ms
11 * * *
12 ae203-0.PHLAPA-VFTTP-371.verizon-gni net (100.41.13.85) 150.489 ms 150.497 ms 150.499 ms
13 pool-108-16-135-194.phlapa.fios.verizon net (108.16.135.194) 154.427 ms 159.043 ms 159.016 ms
18/03/2019 00:09:28 UTC
PING:
PING 108.16.135.194 (108.16.135.194) 56(84) bytes of data.
64 bytes from 108.16.135.194: icmp_seq=1 ttl=49 time=154 ms
64 bytes from 108.16.135.194: icmp_seq=2 ttl=49 time=155 ms
64 bytes from 108.16.135.194: icmp_seq=3 ttl=49 time=152 ms
64 bytes from 108.16.135.194: icmp_seq=4 ttl=49 time=158 ms
— 108.16.135.194 ping statistics —
4 packets transmitted, 4 received, 0% packet loss, time 2998ms
rtt min/avg/max/mdev = 152.575/155.352/158.493/2.140 ms
18/03/2019 00:09:28 UTC
MTR:
Start: Mon Mar 18 00:09:28 2019 Blizzard 1.|-- Blizzard 0.0% 10 0.3 0.3 0.2 0.3 0.0
2.|-- 24.105.18.131 0.0% 10 0.6 0.6 0.5 0.7 0.0
3.|-- 137.221.105.16 0.0% 10 0.6 0.7 0.5 0.8 0.0
4.|-- 137.221.66.22 0.0% 10 0.7 0.7 0.6 0.8 0.0
5.|-- 137.221.83.68 0.0% 10 3.5 4.1 1.0 7.7 2.4
6.|-- 137.221.65.68 0.0% 10 5.6 5.8 5.6 6.1 0.0
7.|-- 137.221.68.32 0.0% 10 5.6 5.8 5.5 7.9 0.7
8.|-- xe-9-3-0.edge2.LosAngeles9.Level3 net 0.0% 10 5.4 5.5 5.3 6.3 0.0
9.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0
10.|-- Verizon-level3-50G.LosAngeles1.Level3 net 0.0% 10 5.6 5.6 5.5 5.8 0.0
11.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0
12.|-- ae203-0.PHLAPA-VFTTP-371.verizon-gni net 0.0% 10 166.4 165.4 152.8 222.0 20.6
13.|-- pool-108-16-135-194.phlapa.fios.verizon net 0.0% 10 172.2 163.3 153.1 172.2 5.1
18/03/2019 00:09:28 UTC
So I use Verizon and 2 days ago I went from 40 ping to 100+ ping. I did the test, I did them all separately while in a qp match. lemme know If I need to do anything differently.
MTR:
Start: Mon Mar 18 00:38:19 2019 Blizzard 1.|-- Blizzard 0.0% 10 0.3 0.3 0.2 0.3 0.0 Blizzard 0.0% 10 5.6 5.5 0.4 17.8 6.2
3.|-- 137.221.105.12 0.0% 10 0.6 0.7 0.5 0.9 0.0
4.|-- 137.221.66.20 0.0% 10 0.6 0.6 0.6 0.8 0.0
5.|-- 137.221.83.68 0.0% 10 4.1 4.2 1.4 7.9 2.2
6.|-- 137.221.65.68 0.0% 10 5.9 5.8 5.7 6.0 0.0
7.|-- 137.221.68.32 0.0% 10 5.7 8.2 5.5 20.1 4.8
8.|-- xe-9-3-0.edge2.LosAngeles9.Level3 net 0.0% 10 5.4 5.6 5.4 7.0 0.3
9.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0
10.|-- Verizon-level3-50G.LosAngeles1.Level3 net 0.0% 10 5.6 5.6 5.5 5.7 0.0
11.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0
12.|-- ae203-0.PHLAPA-VFTTP-310.verizon-gni net 0.0% 10 128.5 143.1 128.5 165.5 14.0
13.|-- pool-100-11-248-46.phlapa.fios.verizon net 0.0% 10 133.3 143.3 133.3 166.5 12.7
18/03/2019 00:38:19 UTC
MTR:
Start: Mon Mar 18 00:38:19 2019 Blizzard 1.|-- Blizzard 0.0% 10 0.3 0.4 0.2 1.2 0.0 Blizzard 0.0% 10 0.6 0.9 0.6 2.8 0.5
3.|-- 137.221.105.12 0.0% 10 0.7 0.6 0.5 0.8 0.0
4.|-- 137.221.66.20 0.0% 10 0.6 0.6 0.6 0.7 0.0
5.|-- 137.221.83.68 0.0% 10 7.3 5.5 0.7 8.8 2.6
6.|-- 137.221.65.68 0.0% 10 6.3 5.9 5.6 6.3 0.0
7.|-- 137.221.68.32 0.0% 10 5.5 7.9 5.5 28.6 7.2
8.|-- xe-9-3-0.edge2.LosAngeles9.Level3 net 0.0% 10 5.6 5.7 5.3 6.4 0.0
9.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0
10.|-- Verizon-level3-50G.LosAngeles1.Level3 net 0.0% 10 5.5 5.7 5.5 6.2 0.0
11.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0
12.|-- ae203-0.PHLAPA-VFTTP-310.verizon-gni net 0.0% 10 127.0 139.1 127.0 157.7 12.1
13.|-- pool-100-11-248-46.phlapa.fios.verizon net 0.0% 10 127.1 140.9 126.3 161.3 13.5
18/03/2019 00:38:19 UTC
TRACEROUTE:
traceroute to 100.11.248.46 (100.11.248.46), 15 hops max, 60 byte packets
1 Blizzard Blizzard 0.292 ms 0.294 ms 0.293 ms Blizzard(24.105.18.3) 0.927 ms 0.931 ms 0.930 ms
3 137.221.105.12 (137.221.105.12) 0.532 ms 0.627 ms 0.731 ms
4 137.221.66.20 (137.221.66.20) 0.560 ms 0.622 ms 0.622 ms
5 137.221.83.68 (137.221.83.68) 33.859 ms 33.874 ms 33.873 ms
6 137.221.65.68 (137.221.65.68) 5.679 ms 5.771 ms 5.743 ms
7 137.221.68.32 (137.221.68.32) 5.621 ms 5.624 ms 5.621 ms
8 xe-9-3-0.edge2.LosAngeles9.Level3 net (4.53.230.237) 5.492 ms 5.499 ms 5.496 ms
9 * * *
10 Verizon-level3-50G.LosAngeles1.Level3 net (4.68.62.170) 5.567 ms 5.431 ms 5.464 ms
11 * * *
12 ae203-0.PHLAPA-VFTTP-310.verizon-gni net (130.81.221.25) 129.660 ms 129.668 ms 129.624 ms
13 pool-100-11-248-46.phlapa.fios.verizon net (100.11.248.46) 132.910 ms 131.456 ms 129.677 ms
18/03/2019 00:39:17 UTC
TRACEROUTE:
traceroute to 100.11.248.46 (100.11.248.46), 15 hops max, 60 byte packets
1 Blizzard Blizzard 0.275 ms 0.271 ms 0.273 ms Blizzard(24.105.18.3) 0.495 ms 0.552 ms 0.647 ms
3 137.221.105.12 (137.221.105.12) 1.077 ms 1.116 ms 1.133 ms
4 137.221.66.20 (137.221.66.20) 1.113 ms 1.115 ms 1.116 ms
5 137.221.83.68 (137.221.83.68) 4.510 ms 4.526 ms 4.528 ms
6 137.221.65.68 (137.221.65.68) 5.729 ms 5.734 ms 5.721 ms
7 137.221.68.32 (137.221.68.32) 23.977 ms 23.609 ms 23.595 ms
8 xe-9-3-0.edge2.LosAngeles9.Level3 net (4.53.230.237) 5.375 ms 5.706 ms 5.745 ms
9 * * *
10 Verizon-level3-50G.LosAngeles1.Level3 net (4.68.62.170) 5.573 ms 5.553 ms 5.543 ms
11 * * *
12 ae203-0.PHLAPA-VFTTP-310.verizon-gni net (130.81.221.25) 127.545 ms 127.507 ms 127.311 ms
13 pool-100-11-248-46.phlapa.fios.verizon net (100.11.248.46) 138.361 ms 138.067 ms 136.686 ms
18/03/2019 00:39:17 UTC
PING:
PING 100.11.248.46 (100.11.248.46) 56(84) bytes of data.
64 bytes from 100.11.248.46: icmp_seq=1 ttl=49 time=137 ms
64 bytes from 100.11.248.46: icmp_seq=2 ttl=49 time=151 ms
64 bytes from 100.11.248.46: icmp_seq=3 ttl=49 time=153 ms
64 bytes from 100.11.248.46: icmp_seq=4 ttl=49 time=151 ms
— 100.11.248.46 ping statistics —
4 packets transmitted, 4 received, 0% packet loss, time 3003ms
rtt min/avg/max/mdev = 137.147/148.499/153.230/6.586 ms
18/03/2019 00:39:31 UTC
PING:
PING 100.11.248.46 (100.11.248.46) 56(84) bytes of data.
64 bytes from 100.11.248.46: icmp_seq=1 ttl=49 time=144 ms
64 bytes from 100.11.248.46: icmp_seq=2 ttl=49 time=149 ms
64 bytes from 100.11.248.46: icmp_seq=3 ttl=49 time=148 ms
64 bytes from 100.11.248.46: icmp_seq=4 ttl=49 time=151 ms
— 100.11.248.46 ping statistics —
4 packets transmitted, 4 received, 0% packet loss, time 3003ms
rtt min/avg/max/mdev = 144.657/148.585/151.914/2.585 ms
18/03/2019 00:39:31 UTC
I been having higher latency than usual as well, normally 40 ms but around 100-140 ms (unstable) now.