Entire CARIBBEAN is getting high latency

Technical Support
83

TRACEROUTE:
traceroute to 24.50.226.236 (24.50.226.236), 15 hops max, 60 byte packets
1 10.56.100.81 (10.56.100.81) 0.322 ms 0.333 ms 0.331 ms
2 37.244.22.131 (37.244.22.131) 0.592 ms 0.607 ms 0.671 ms
3 24.105.30.148 (24.105.30.148) 1.030 ms 1.109 ms 1.172 ms
4 137.221.66.4 (137.221.66.4) 1.745 ms 1.767 ms 2.000 ms
5 137.221.68.72 (137.221.68.72) 17.287 ms 17.303 ms 17.309 ms
6 137.221.65.5 (137.221.65.5) 115.199 ms 112.602 ms 112.575 ms
7 137.221.65.9 (137.221.65.9) 68.257 ms 68.431 ms 68.436 ms
8 137.221.65.25 (137.221.65.25) 137.005 ms 136.826 ms 136.808 ms
9 137.221.79.32 (137.221.79.32) 136.652 ms 136.735 ms 136.723 ms
10 te0-7-0-33.rcr21.lhr01.atlas.cogentco.com (149.6.8.8) 136.827 ms 137.162 ms 137.149 ms
11 be3488.ccr42.lon13.atlas.cogentco.com (154.54.60.13) 137.914 ms 137.891 ms 137.645 ms
12 be2490.ccr42.jfk02.atlas.cogentco.com (154.54.42.85) 136.111 ms 136.234 ms 136.532 ms
13 be2057.ccr21.jfk10.atlas.cogentco.com (154.54.80.178) 136.366 ms 136.478 ms 136.875 ms
14 att.jfk10.atlas.cogentco.com (154.54.10.98) 140.023 ms 139.498 ms 139.475 ms
15 cr2.n54ny.ip.att.net (12.122.130.170) 182.820 ms 182.461 ms 181.952 ms

09/06/2018 00:26:15 UTC

TRACEROUTE:
traceroute to 24.50.226.236 (24.50.226.236), 15 hops max, 60 byte packets
1 10.57.100.13 (10.57.100.13) 0.399 ms 0.391 ms 0.391 ms
2 37.244.23.130 (37.244.23.130) 0.789 ms 0.798 ms 0.801 ms
3 24.105.62.146 (24.105.62.146) 1.493 ms 1.506 ms 1.534 ms
4 137.221.66.8 (137.221.66.8) 2.104 ms 2.112 ms 2.152 ms
5 137.221.69.70 (137.221.69.70) 2.054 ms 2.069 ms 2.071 ms
6 137.221.65.9 (137.221.65.9) 46.901 ms 44.368 ms 44.342 ms
7 137.221.65.25 (137.221.65.25) 91.006 ms 90.915 ms 90.898 ms
8 137.221.79.32 (137.221.79.32) 90.265 ms 91.308 ms 91.284 ms
9 te0-7-0-33.rcr21.lhr01.atlas.cogentco.com (149.6.8.8) 92.437 ms 93.747 ms 93.757 ms
10 be3488.ccr42.lon13.atlas.cogentco.com (154.54.60.13) 92.820 ms 92.094 ms 92.097 ms
11 be2490.ccr42.jfk02.atlas.cogentco.com (154.54.42.85) 95.454 ms 89.869 ms 89.903 ms
12 be2057.ccr21.jfk10.atlas.cogentco.com (154.54.80.178) 89.982 ms 90.160 ms 90.051 ms
13 att.jfk10.atlas.cogentco.com (154.54.10.98) 92.233 ms 91.673 ms 91.202 ms
14 cr2.n54ny.ip.att.net (12.122.130.170) 145.141 ms 143.615 ms 143.599 ms
15 cr2.wswdc.ip.att.net (12.122.28.42) 146.158 ms 145.609 ms 145.589 ms

09/06/2018 00:26:15 UTC

PING:
PING 24.50.226.236 (24.50.226.236) 56(84) bytes of data.

— 24.50.226.236 ping statistics —
4 packets transmitted, 0 received, 100% packet loss, time 3008ms

09/06/2018 00:26:15 UTC

PING:
PING 24.50.226.236 (24.50.226.236) 56(84) bytes of data.

— 24.50.226.236 ping statistics —
4 packets transmitted, 0 received, 100% packet loss, time 3001ms

09/06/2018 00:26:15 UTC

MTR:
Start: Sat Jun 9 00:26:15 2018
HOST: Blizzard Loss% Snt Last Avg Best Wrst StDev
1.|-- 10.57.100.13 0.0% 10 0.3 0.3 0.2 0.3 0.0
2.|-- 37.244.23.130 0.0% 10 0.5 0.5 0.4 0.8 0.0
3.|-- 24.105.62.146 0.0% 10 1.2 1.3 1.2 1.6 0.0
4.|-- 137.221.66.8 0.0% 10 2.0 2.0 1.9 2.1 0.0
5.|-- 137.221.69.70 0.0% 10 1.8 4.8 1.8 28.5 8.3
6.|-- 137.221.65.9 0.0% 10 22.2 22.1 21.8 22.8 0.0
7.|-- 137.221.65.25 0.0% 10 91.3 91.1 90.9 92.1 0.3
8.|-- 137.221.79.32 0.0% 10 90.3 90.5 90.2 91.2 0.0
9.|-- te0-7-0-33.rcr21.lhr01.atlas.cogentco.com 0.0% 10 90.7 90.5 90.4 90.7 0.0
10.|-- be3488.ccr42.lon13.atlas.cogentco.com 0.0% 10 92.4 92.0 91.7 92.4 0.0
11.|-- be2490.ccr42.jfk02.atlas.cogentco.com 0.0% 10 90.0 90.0 89.8 90.6 0.0
12.|-- be2057.ccr21.jfk10.atlas.cogentco.com 0.0% 10 90.2 90.1 90.0 90.4 0.0
13.|-- att.jfk10.atlas.cogentco.com 0.0% 10 91.9 92.4 90.7 94.2 0.8
14.|-- cr2.n54ny.ip.att.net 0.0% 10 146.0 145.7 143.6 150.1 1.6
15.|-- cr2.wswdc.ip.att.net 0.0% 10 140.8 143.4 140.8 153.7 4.2
16.|-- cr1.attga.ip.att.net 0.0% 10 148.5 142.1 140.1 148.5 2.4
17.|-- cr2.attga.ip.att.net 0.0% 10 157.3 149.0 146.9 157.3 2.9
18.|-- cr82.snjpr.ip.att.net 0.0% 10 144.1 142.2 140.9 145.0 1.5
19.|-- 12.123.241.133 0.0% 10 140.8 140.8 140.5 141.4 0.0
20.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0
21.|-- 254-196-38-65-static.centennialpr.net 0.0% 10 145.5 144.7 144.3 145.5 0.0
22.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0

09/06/2018 00:26:15 UTC

MTR:
Start: Sat Jun 9 00:26:15 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.7 0.0
3.|-- 24.105.30.148 0.0% 10 0.9 1.1 0.9 1.8 0.0
4.|-- 137.221.66.4 0.0% 10 1.7 1.5 1.4 1.7 0.0
5.|-- 137.221.68.72 0.0% 10 1.7 6.9 1.3 34.7 11.9
6.|-- 137.221.65.5 0.0% 10 47.7 50.7 47.7 75.6 8.7
7.|-- 137.221.65.9 0.0% 10 72.6 69.9 68.2 79.2 3.5
8.|-- 137.221.65.25 0.0% 10 137.8 137.0 136.7 137.8 0.0
9.|-- 137.221.79.32 0.0% 10 136.8 137.1 136.5 140.4 1.0
10.|-- te0-7-0-33.rcr21.lhr01.atlas.cogentco.com 0.0% 10 137.1 137.0 136.7 137.5 0.0
11.|-- be3488.ccr42.lon13.atlas.cogentco.com 0.0% 10 137.6 137.9 137.6 138.7 0.0
12.|-- be2490.ccr42.jfk02.atlas.cogentco.com 0.0% 10 137.6 136.6 136.2 137.6 0.3
13.|-- be2057.ccr21.jfk10.atlas.cogentco.com 0.0% 10 137.0 136.6 136.4 137.0 0.0
14.|-- att.jfk10.atlas.cogentco.com 0.0% 10 137.7 138.2 136.1 140.3 1.2
15.|-- cr2.n54ny.ip.att.net 0.0% 10 183.2 182.3 180.3 183.9 0.9
16.|-- cr2.wswdc.ip.att.net 0.0% 10 180.2 180.9 177.4 185.0 2.3
17.|-- cr1.attga.ip.att.net 0.0% 10 183.8 182.2 178.5 186.5 2.3
18.|-- cr2.attga.ip.att.net 0.0% 10 183.3 180.7 178.3 183.7 2.1
19.|-- cr82.snjpr.ip.att.net 0.0% 10 179.4 180.3 178.7 182.1 0.9
20.|-- 12.123.241.133 0.0% 10 178.4 178.7 178.3 179.7 0.3
21.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0
22.|-- 254-196-38-65-static.centennialpr.net 0.0% 10 182.7 182.9 182.6 183.3 0.0
23.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0

09/06/2018 00:26:15 UTC

84

Just a quick update. At 9:09 pm my time. My ping settled. Might be temporary. But I’m optimistic

85

just checked mine and its still 180ms

86

So update to my update. I only have my regular ping when my friend from America invites me to a group. Other than that. If I solo queue. My ping is atrocious.
I’m guessing blizzard rerouted us Caribbean ppl to a separate server and that’s screwing with our ping.

87

Im gonna try that with my friend. Nice call.

I hope they fix it. Seeing that 100ms~ again will be delicious.

88

I’m from Puerto Rico and I’m having the same problem.

89

Same here, I’m from Puerto Rico. I used to have 80ms ~ 100ms but now it is from 160ms to all over 250ms.

On Destiny 2, the Raids are a joke, a real bad one.

The response from Blizzard Tech Support was “it is normal because you live in a pretty far island”…

Ticket Number: US63249688

90

That is ridiculous. Whoever the tech is should be fired

4 Likes
91

wow. But ive been playing this game for 2 years and I had 80-100ms almost the entire time. This just happened on Monday. My friend lives 5 minutes from me and gets 110ms right now playing OW. This is weird. Apparently its happening in Canada too.

3 Likes
92

Is he using a different ISP?

93

yes (Claro) but someone here said that one of their friends also has Claro and still has the problem.

94

My ping seem to have settled

95

Hello, i’m from Panama and i have the same issue, i get thrown into the BR server wich is way farther away from me than the US (the fact that i don’t speak portuguese is even worse than the high ping btw)… Anyway, i found a little app that helps you block the ips from any server on your firewall so you can technically force the game to connect only to the ones you want, funny thing is, when the only servers available on my firewall are the US ones, the game won’t connect at all… I also couldn’t ping to the US servers

1 Like
96

Not for me. Just checked.

97

Im from Puerto Rico and getting 280sr already dropped 300sr

98

i’m still at 200. (liberty)

99

I’m From trinidad and still getting 200ms, From FLOW…I’m crying here.

100

Remember everyone, to quickly identify the issues with your latency, please take the time to post a WinMTR test. This gives very important details to Blizzard so they can have a better idea where the problem is occurring:

WinMTR instructions:

  1. Download WinMTR from http://winmtr.net/download-winmtr/ (Console players need a Windows Desktop Computer connected to the same network as their console to do this.)
  2. Unzip the WinMTR.zip file to the Desktop.
  3. Open the WinMTR folder and select the 32 or 64 bit version. Choose whichever one corresponds to your version of Windows.
  4. Run the WinMTR.exe
  5. Type the IP address you want to trace in the “Host” field. To get the correct IP you will actually need to open up the game and go Practice Vs AI or Quick Play and if you are on PC hit Ctrl+Shift+N and it will bring up the ingame network diagnostic graph, or go to Video > Options > Display Network Performance Graph if you are on any platform including Console. In the top left corner is the IP address you want to run WinMTR to.
    Network Graph
    note When looking at the IP it will show up ingame as something like 12.34.56.78:12345. You will want to leave the last 5 digits and the colon at the end off and the IP you want to use is just the 12.34.56.78
  6. Once you notice the connection issue while playing, play for about 6 more minutes, minimize the game and click on “Stop”.
  7. Click on “Copy text to clipboard”, then return to this forum thread.
  8. Type two sets of four squiggly lines and then paste the contents of the WinMTR test between: ~~~~ Paste WinMTR Test Results Here ~~~~

If in the event you can’t even connect to Overwatch and get into any game mode at all, please use one of the following IP addresses based on your geographical region:

  • US West - 24.105.30.129
  • US Central - 24.105.62.129 ← RECOMMENDED
  • Brazil - 54.207.107.12
  • Europe - 185.60.114.159
  • Europe - 185.60.112.157
  • Korea - 211.234.110.1
  • Taiwan - 203.66.81.98
2 Likes
101

Thansk dude but, look at all the posts. Ive already done that. They said theyre looking into it but I still have the problem. I would like an update.

102

I know, but sometime things like this take time. For as far as we know this could be similar to an issue like the Southeast Asia sea cable cuts and that is taking weeks to fix. By continuing to post periodical WinMTRs that can help them track the status. I was observing too many players just complaining about the latency which is why I posted the reminder.

1 Like