We used to have a stable 75ms ping but like three months ago we are having very unstable latencies starting from 115ms.
I got a 16mb/1mb connection with Claro who is the most stable residential ISP in the country. This issue is also happening with other ISP like Liberty Cable (the fastest in the country) 100mb/3mb.
I can ping to Miami with 68ms results or any east coast server without surpassing 100ms ping, but Overwatch is always 110+ when the best I ever had was 63ms
Please check what is happening with Blizzard’s end.
Thanks.
TRACEROUTE:
traceroute to 66.50.49.146 (66.50.49.146), 15 hops max, 60 byte packets
1 Blizzard Blizzard 0.439 ms 0.433 ms 0.434 ms
2 37.244.22.131 (37.244.22.131) 0.709 ms 0.783 ms 0.845 ms
3 24.105.30.162 (24.105.30.162) 1.176 ms 1.233 ms 1.328 ms
4 137.221.66.2 (137.221.66.2) 1.745 ms 1.788 ms 1.843 ms
5 137.221.68.66 (137.221.68.66) 1.707 ms 1.723 ms 1.725 ms
6 137.221.68.32 (137.221.68.32) 1.401 ms 1.059 ms 1.267 ms
7 xe-9-3-0.edge2.LosAngeles9.Level3.net (4.53.230.237) 0.952 ms 1.089 ms 1.066 ms
8 * * *
9 PUERTO-RICO.ear3.Atlanta2.Level3.net (4.14.25.206) 82.378 ms 82.393 ms 82.394 ms
10 * * *
11 * * *
12 * * *
13 cvx-ppp-66-50-49-146.coqui.net (66.50.49.146) 117.983 ms 111.891 ms 112.640 ms
29/07/2018 23:48:37 UTC
--------------------
TRACEROUTE:
traceroute to 66.50.49.146 (66.50.49.146), 15 hops max, 60 byte packets
1 Blizzard Blizzard 0.418 ms 0.396 ms 0.392 ms
2 37.244.23.2 (37.244.23.2) 0.688 ms 0.954 ms 1.040 ms
3 24.105.62.150 (24.105.62.150) 2.366 ms 2.370 ms 2.383 ms
4 137.221.66.14 (137.221.66.14) 2.159 ms 2.209 ms 2.276 ms
5 137.221.69.72 (137.221.69.72) 2.113 ms 2.119 ms 2.130 ms
6 137.221.69.34 (137.221.69.34) 1.465 ms 1.286 ms 1.248 ms
7 xe-11-3-0.edge4.Chicago3.Level3.net (4.53.98.45) 0.995 ms 1.015 ms 1.009 ms
8 * * *
9 PUERTO-RICO.ear3.Atlanta2.Level3.net (4.14.25.206) 58.244 ms 58.315 ms 58.325 ms
10 * * *
11 * * *
12 * * *
13 cvx-ppp-66-50-49-146.coqui.net (66.50.49.146) 87.070 ms 86.497 ms 87.175 ms
29/07/2018 23:48:37 UTC
--------------------
PING:
PING 66.50.49.146 (66.50.49.146) 56(84) bytes of data.
64 bytes from 66.50.49.146: icmp_seq=1 ttl=47 time=123 ms
64 bytes from 66.50.49.146: icmp_seq=2 ttl=47 time=123 ms
64 bytes from 66.50.49.146: icmp_seq=3 ttl=47 time=113 ms
64 bytes from 66.50.49.146: icmp_seq=4 ttl=47 time=112 ms
--- 66.50.49.146 ping statistics ---
4 packets transmitted, 4 received, 0% packet loss, time 2998ms
rtt min/avg/max/mdev = 112.729/118.182/123.370/5.095 ms
29/07/2018 23:48:37 UTC
--------------------
PING:
PING 66.50.49.146 (66.50.49.146) 56(84) bytes of data.
64 bytes from 66.50.49.146: icmp_seq=1 ttl=49 time=87.1 ms
64 bytes from 66.50.49.146: icmp_seq=2 ttl=49 time=86.5 ms
64 bytes from 66.50.49.146: icmp_seq=3 ttl=49 time=86.6 ms
64 bytes from 66.50.49.146: icmp_seq=4 ttl=49 time=86.9 ms
--- 66.50.49.146 ping statistics ---
4 packets transmitted, 4 received, 0% packet loss, time 2998ms
rtt min/avg/max/mdev = 86.506/86.810/87.107/0.241 ms
29/07/2018 23:48:37 UTC
--------------------
MTR:
Start: Sun Jul 29 23:48:37 2018 Blizzard 1.|-- Blizzard 0.0% 10 0.3 0.3 0.3 0.5 0.0
2.|-- 37.244.22.131 0.0% 10 0.6 0.5 0.5 0.7 0.0
3.|-- 24.105.30.162 0.0% 10 1.0 1.0 0.8 1.8 0.0
4.|-- 137.221.66.2 0.0% 10 1.6 1.5 1.4 1.7 0.0
5.|-- 137.221.68.66 0.0% 10 1.5 2.0 1.3 7.1 1.7
6.|-- 137.221.68.32 0.0% 10 1.3 1.3 1.1 1.7 0.0
7.|-- xe-9-3-0.edge2.LosAngeles9.Level3.net 0.0% 10 1.1 1.2 1.1 1.9 0.0
8.|-- ae-2-52.ear3.Atlanta2.Level3.net 90.0% 10 50.1 50.1 50.1 50.1 0.0
9.|-- PUERTO-RICO.ear3.Atlanta2.Level3.net 0.0% 10 84.2 83.4 81.5 84.9 1.1
10.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0
11.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0
12.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0
13.|-- cvx-ppp-66-50-49-146.coqui.net 0.0% 10 116.1 112.8 111.6 116.1 1.2
29/07/2018 23:48:37 UTC
--------------------
MTR:
Start: Sun Jul 29 23:48:37 2018 Blizzard 1.|-- Blizzard 0.0% 10 0.2 0.2 0.2 0.3 0.0
2.|-- 37.244.23.2 0.0% 10 0.5 0.5 0.4 0.8 0.0
3.|-- 24.105.62.150 0.0% 10 0.9 1.0 0.9 1.9 0.0
4.|-- 137.221.66.14 0.0% 10 1.8 1.9 1.7 2.1 0.0
5.|-- 137.221.69.72 0.0% 10 1.9 1.8 1.7 1.9 0.0
6.|-- 137.221.69.34 0.0% 10 1.3 1.2 1.1 1.6 0.0
7.|-- xe-11-3-0.edge4.Chicago3.Level3.net 0.0% 10 1.0 1.3 1.0 2.5 0.3
8.|-- ae-2-52.ear3.Atlanta2.Level3.net 90.0% 10 24.2 24.2 24.2 24.2 0.0
9.|-- PUERTO-RICO.ear3.Atlanta2.Level3.net 0.0% 10 57.0 56.9 55.2 58.7 0.9
10.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0
11.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0
12.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0
13.|-- cvx-ppp-66-50-49-146.coqui.net 0.0% 10 86.8 88.5 85.8 97.4 4.1
29/07/2018 23:48:37 UTC
--------------------
Looks like this connecting point is having issues, which is something your ISP will have to handle. Call them and ask if they can ping/traceroute the same point and they will likely see the issue. I can see the issue it from my own computer when pinging that host.
Here is another result with a trace back to blizzard from my end.
TRACEROUTE:
traceroute to 72.50.111.193 (72.50.111.193), 15 hops max, 60 byte packets
1 Blizzard Blizzard 0.267 ms 0.238 ms 0.233 ms
2 37.244.22.3 (37.244.22.3) 1.041 ms 1.166 ms 1.267 ms
3 24.105.30.162 (24.105.30.162) 0.880 ms 0.919 ms 2.304 ms
4 137.221.66.2 (137.221.66.2) 1.511 ms 1.586 ms 1.652 ms
5 137.221.68.70 (137.221.68.70) 1.391 ms 1.394 ms 1.458 ms
6 137.221.68.34 (137.221.68.34) 1.195 ms 1.138 ms 1.115 ms
7 te0-4-0-9.ccr41.lax05.atlas.cogentco.com (38.104.84.12) 1.431 ms 1.626 ms 1.681 ms
8 be3243.ccr41.lax01.atlas.cogentco.com (154.54.27.117) 1.628 ms 1.630 ms 1.651 ms
9 be2931.ccr31.phx01.atlas.cogentco.com (154.54.44.85) 13.200 ms 13.343 ms 13.372 ms
10 be2929.ccr21.elp01.atlas.cogentco.com (154.54.42.66) 21.571 ms 21.569 ms 21.575 ms
11 be2928.ccr42.iah01.atlas.cogentco.com (154.54.30.161) 36.690 ms 36.645 ms 36.630 ms
12 be3570.ccr22.mia01.atlas.cogentco.com (154.54.84.2) 61.591 ms 61.666 ms 61.640 ms
13 be3401.ccr21.mia03.atlas.cogentco.com (154.54.47.30) 61.598 ms 61.731 ms 61.710 ms
14 38.142.153.2 (38.142.153.2) 115.958 ms 112.843 ms 112.823 ms
15 * * *
03/08/2018 15:38:34 UTC
--------------------
TRACEROUTE:
traceroute to 72.50.111.193 (72.50.111.193), 15 hops max, 60 byte packets
1 Blizzard Blizzard 0.361 ms 0.344 ms 0.341 ms
2 37.244.23.130 (37.244.23.130) 0.543 ms 0.629 ms 0.720 ms
3 24.105.62.150 (24.105.62.150) 0.976 ms 1.048 ms 1.107 ms
4 137.221.66.14 (137.221.66.14) 2.061 ms 2.135 ms 2.209 ms
5 137.221.69.68 (137.221.69.68) 2.018 ms 2.042 ms 2.047 ms
6 137.221.69.32 (137.221.69.32) 1.527 ms 1.277 ms 1.248 ms
7 te0-19-0-2.ccr41.ord03.atlas.cogentco.com (38.104.102.28) 1.371 ms 1.452 ms 1.446 ms
8 be2766.ccr42.ord01.atlas.cogentco.com (154.54.46.177) 1.529 ms 1.805 ms 1.784 ms
9 be2736.ccr42.atl01.atlas.cogentco.com (154.54.5.86) 20.097 ms 20.131 ms 20.133 ms
10 be3483.ccr22.mia01.atlas.cogentco.com (154.54.28.50) 33.263 ms 33.281 ms 32.887 ms
11 be3401.ccr21.mia03.atlas.cogentco.com (154.54.47.30) 33.225 ms 33.242 ms 33.215 ms
12 38.142.153.2 (38.142.153.2) 86.875 ms 86.262 ms 86.570 ms
13 * * *
14 * * *
15 adsl-72-50-111-193.prtc.net (72.50.111.193) 100.170 ms 100.113 ms 100.828 ms
03/08/2018 15:38:34 UTC
--------------------
MTR:
Start: Fri Aug 3 15:38:34 2018 Blizzard 1.|-- Blizzard 0.0% 10 0.3 0.3 0.2 0.3 0.0
2.|-- 37.244.22.131 0.0% 10 0.5 0.6 0.5 1.0 0.0
3.|-- 24.105.30.162 0.0% 10 0.9 1.2 0.8 2.1 0.0
4.|-- 137.221.66.6 0.0% 10 1.7 1.6 1.5 1.8 0.0
5.|-- 137.221.68.72 0.0% 10 1.4 2.5 1.4 12.2 3.4
6.|-- 137.221.68.34 0.0% 10 1.2 1.2 1.1 1.3 0.0
7.|-- te0-4-0-9.ccr41.lax05.atlas.cogentco.com 0.0% 10 1.7 1.6 1.4 2.5 0.0
8.|-- be3359.ccr42.lax01.atlas.cogentco.com 0.0% 10 1.7 1.5 1.3 1.7 0.0
9.|-- be2932.ccr32.phx01.atlas.cogentco.com 0.0% 10 13.0 13.3 13.0 13.5 0.0
10.|-- be2930.ccr21.elp01.atlas.cogentco.com 0.0% 10 21.4 21.4 21.3 21.7 0.0
11.|-- be2927.ccr41.iah01.atlas.cogentco.com 0.0% 10 37.1 36.9 36.8 37.2 0.0
12.|-- be3569.ccr21.mia01.atlas.cogentco.com 0.0% 10 61.7 61.7 61.5 62.0 0.0
13.|-- be3400.ccr21.mia03.atlas.cogentco.com 0.0% 10 61.6 61.7 61.5 61.9 0.0
14.|-- 38.142.153.2 0.0% 10 113.1 114.2 112.4 115.8 1.0
15.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0
16.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0
17.|-- adsl-72-50-111-193.prtc.net 0.0% 10 128.1 128.1 127.4 128.9 0.0
03/08/2018 15:38:34 UTC
--------------------
MTR:
Start: Fri Aug 3 15:38:34 2018 Blizzard 1.|-- Blizzard 0.0% 10 0.6 0.3 0.3 0.6 0.0
2.|-- 37.244.23.130 0.0% 10 0.6 0.6 0.4 1.3 0.0
3.|-- 24.105.62.150 0.0% 10 1.0 1.3 1.0 2.5 0.3
4.|-- 137.221.66.14 0.0% 10 2.0 2.1 2.0 2.2 0.0
5.|-- 137.221.69.68 0.0% 10 2.0 1.9 1.9 2.1 0.0
6.|-- 137.221.69.32 0.0% 10 1.3 3.4 1.2 22.1 6.6
7.|-- te0-19-0-2.ccr41.ord03.atlas.cogentco.com 0.0% 10 1.5 1.5 1.4 1.6 0.0
8.|-- be2766.ccr42.ord01.atlas.cogentco.com 0.0% 10 1.7 1.7 1.5 1.9 0.0
9.|-- be2736.ccr42.atl01.atlas.cogentco.com 0.0% 10 20.1 20.1 19.9 20.3 0.0
10.|-- be3483.ccr22.mia01.atlas.cogentco.com 0.0% 10 33.1 33.2 33.0 33.3 0.0
11.|-- be3401.ccr21.mia03.atlas.cogentco.com 0.0% 10 33.3 33.3 33.1 33.7 0.0
12.|-- 38.142.153.2 0.0% 10 86.4 85.8 84.4 87.3 0.9
13.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0
14.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0
15.|-- adsl-72-50-111-193.prtc.net 0.0% 10 99.3 99.7 99.3 100.2 0.0
03/08/2018 15:38:34 UTC
--------------------
Tracing route to 131.22.244.37.in-addr.arpa [37.244.22.131]
over a maximum of 30 hops:
1 62 ms 99 ms 99 ms dsldevice.lan [10.0.0.138]
2 17 ms 17 ms 17 ms adsl-207-204-166-128.prtc.net [207.204.166.128]
3 18 ms 17 ms 17 ms 253.141.210.10.in-addr.arpa [10.210.141.253]
4 16 ms 19 ms 19 ms 62.2.208.10.in-addr.arpa [10.208.2.62]
5 68 ms 68 ms 68 ms 38.142.153.1
6 68 ms 79 ms 68 ms be3401.ccr22.mia01.atlas.cogentco.com [154.54.47.29]
7 69 ms 74 ms 68 ms be3411.rcr21.b002802-2.mia01.atlas.cogentco.com [154.54.26.42]
8 69 ms 68 ms 68 ms te0-0-2-0.nr11.b002802-1.mia01.atlas.cogentco.com [154.24.43.46]
9 68 ms 68 ms 68 ms gi0-0-0-18.205.nr11.b002802-1.mia01.atlas.cogentco.com [38.104.90.5]
10 68 ms 69 ms 68 ms ae1-br01-eqmi2.blizzardonline.net [137.221.76.33]
11 99 ms 99 ms 98 ms xe-0-0-1-1-br01-eqda6.blizzardonline.net [137.221.65.62]
12 129 ms 129 ms 129 ms et-0-0-2-br02-swlv10.blizzardonline.net [137.221.65.67]
13 129 ms 128 ms 128 ms 137.221.65.32
14 129 ms 128 ms 129 ms et-0-0-2-br01-eqla1.blizzardonline.net [137.221.65.68]
15 129 ms 129 ms 133 ms be1-pe01-eqla1.blizzardonline.net [137.221.68.67]
16 129 ms 128 ms 129 ms lax-eqla1-ia-bons-01.blizzardonline.net [137.221.66.1]
17 129 ms 129 ms 128 ms 37.244.22.131
Trace complete.
As far as I can see from my side, the problem starts as soon as I reach Blizzard’s server.
10 68 ms 69 ms 68 ms ae1-br01-eqmi2.blizzardonline.net [137.221.76.33]
11 99 ms 99 ms 98 ms xe-0-0-1-1-br01-eqda6.blizzardonline.net [137.221.65.62]
12 129 ms 129 ms 129 ms et-0-0-2-br02-swlv10.blizzardonline.net [137.221.65.67]
Not sure if this is part of your ISP, but this ping is pretty high. Also, in In the last Traceroute before your sample your local ping is high, and I see 2 MTRs from Blizzard to you, but not one from you to them?
I’m from Puerto Rico and also having random rubber banding or micro pauses in almost every match but no apparent high ping or connection issues. I’m not the only one. Even my friends are experiencing the same issues whenever we are on different matches or on the same squad.
Im being affected by this Issue too… Games is unplayable for me… A similar situation was taken care of not long ago… What is happening this time Blizzard…???
Rubber banding like there is no tomorrow. How is it that I have low latency but still manage to lag or have my shots not get registered? I live in Puerto Rico and it seems like I’m not the only one here having this issue.
Hey everyone, from the network tracing you’ve all been posting, this appears to be an issue within your ISP’s network. You’ll likely need to contact them to sort this out.
Nicole’s recommendation is actually spot on in this case. The Looking Glass results that have been posted have been consistently showing that data is getting through and exiting our network and peering partners with relatively low latency.
Consistently in the looking glasses, we’re not seeing elevated latency until the traffic begins to be routed via backbones/local infrastructure. Since most, if not all, of you guys are on Liberty Cable, we’d like you to run WinMTR tests while connected to a Custom vs AI match and post them here - try to capture the disconnect/rubberbanding in the MTR. With information that looks at the route the other way, we may be able to identify a problem node.
Some forums are not moderated as it should and your reply makes it feel that we are not left in the dark.
Back on point, it is never safe to assume we are all using the same local ISP’s. Not to brag about, but in my case this is the best ISP/Connection Method I could get in my area and to be honest at this time it is only happening on Blizzard game tittles. Not long ago I report a similar incident and apparently Puerto Rico was not the only one experiencing the same problem.
I’m aware of many external variables that can contribute to connectivity issues but sometimes we as an average customer can’t determine or explain the technical aspect of the problem to the ISP Tech Rep, maybe not due by the lack of knowledge but also because of the platform that we are connecting from. But when an IT/Provisioning/Engineering Dept/Group of a company such Blizzard “bring their two cents” it is my guess that the ISP will be more “willing” to listen and improve their nodes/routes, etc.
In my case I’m using PC version of Blizzard tittles. I’ll run WinMTR and post the results as suggested.
Below the results of WinMTR test during an entire Quick Match took place. Judging by the results, Blizzard servers showed connection inconsistencies multiple times.
I actually wasn’t assuming that everyone who had posted was on the same ISP, I was checking against where everyone was posting from. We’re able to get some limited data from when you post, including what ISP is being utilized. The majority of the posts so far were consistently coming from Liberty Cable, so that’s why I mentioned it explicitly.
Really appreciate the MTR results though! To clarify, those two nodes with elevated worst latency are some of our peering partners. If we can get additional MTR results that are all consistently showing the same data, we may be able to escalate something up to have it investigated.
Well, I believe this is it then… I’m trying to help but if every time we report some issues that evidently is not related to our end and the Admins/Moderator reply without any sense of commitment to the customers, certainly nothing will be escalated/addressed accordingly.
Just to make sure I got you right, and for the benefic of the users/customers reading your answer:
If two Blizzard’s nodes are reporting constant delays that actually is more than 3-4 times randomly, will it cause any connectivity like issues?
If so, why it can’t be considered to be escalated?
Even more, with the same test results / Troubleshooting Procedures you asked for? Which by the way are well and officially documented on this forum.
Sorry, but honestly I don’t understand how this incidents are addressed by your Tech/Help Desk System/Policies.
This kind of response from your Tech Support perspective puts you on a questionable spot. Bare in mind, most of Us, your customers, are IT Pros who don’t buy lazy answers.
Anyways, I don’t think this isn’t going to get us any further.
Today, I called to Liberty PR ISP Tech Support only to make sure there is nothing reported on my area and also I’ve requested to monitor my line for 72 hrs. The report should be ready on this Sunday afternoon.