Ping issue. playing from alaska

Icarus-1314 · September 18, 2018, 5:59am

im in anchorage, alaska. i used to have 70 - 80 ms but now its going to constant 130.

Kaedi-11739 · September 18, 2018, 3:18pm

The best way to determine why this has happen is to run a WinMTR test:

WinMTR instructions:

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.)
Unzip the WinMTR.zip file to the Desktop.
Open the WinMTR folder and select the 32 or 64 bit version. Choose whichever one corresponds to your version of Windows.
Run the WinMTR.exe
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.

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
Once you notice the connection issue while playing, play for about 6 more minutes, minimize the game and click on “Stop”.
Click on “Copy text to clipboard”, then return to this forum thread.
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
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

Icarus-1314 · September 19, 2018, 4:31am

|------------------------------------------------------------------------------------------|
| WinMTR statistics |

Host - %	Sent	Recv	Best	Avrg	Wrst	Last
192.168.1.1 - 0	264	264	0	0	1	0
No response from host - 100	53	0	0	0	0	0
10.128.26.105 - 72	69	20	8	13	18	15
10.128.8.58 - 89	59	7	11	15	20	13
10.128.4.129 - 80	64	13	28	30	34	28
10.128.240.18 - 80	64	13	26	30	36	28
10.128.4.165 - 84	61	10	49	52	58	52
10.128.6.29 - 84	61	10	99	103	109	107
eqix-ix-ch1.blizzard.com - 80	64	13	107	111	127	107
ae1-br01-eqch2.as57976.net - 77	65	15	110	114	120	114
No response from host - 100	53	0	0	0	0	0
No response from host - 100	53	0	0	0	0	0
No response from host - 100	53	0	0	0	0	0
No response from host - 100	53	0	0	0	0	0
No response from host - 100	53	0	0	0	0	0
No response from host - 100	53	0	0	0	0	0
No response from host - 100	53	0	0	0	0	0
No response from host - 100	53	0	0	0	0	0
No response from host - 100	53	0	0	0	0	0
No response from host - 100	53	0	0	0	0	0
No response from host - 100	53	0	0	0	0	0
No response from host - 100	53	0	0	0	0	0
No response from host - 100	53	0	0	0	0	0
No response from host - 100	53	0	0	0	0	0
No response from host - 100	53	0	0	0	0	0
No response from host - 100	53	0	0	0	0	0
No response from host - 100	53	0	0	0	0	0
No response from host - 100	53	0	0	0	0	0
No response from host - 100	53	0	0	0	0	0
No response from host - 100	53	0	0	0	0	0
________________________________________________	______	______	______	______	______	______

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

Nicole-1893 · September 19, 2018, 7:46am

Major packet loss on your ISP lines.

Kristal-11786 · September 19, 2018, 7:50am

Are you a moderator? I see you everywhere in the technical support forums

Kaedi-11739 · September 19, 2018, 8:46am

No, but I am one of the forum MVPs. Basically we are a group of hardcore Blizzard gamers who take a little bit of time each day to try and help other players resolve issues with Blizzard games.

Kristal-11786 · September 19, 2018, 9:21am

gasp that’s so cool. I wanna do that sometime

Icarus-1314 · September 19, 2018, 9:43pm

is this an issue i have bring up to my ISP and tell them to fix?

xperii-11679 · September 20, 2018, 6:38am

I am also in Alaska, not sure what all this means but I’ve attached a the result’s I got from using looking glass:

TRACEROUTE:
traceroute to 24.237.56.98 (24.237.56.98), 15 hops max, 60 byte packets
 1  Blizzard Blizzard  0.320 ms  0.299 ms  0.297 ms
 2  37.244.22.131 (37.244.22.131)  0.773 ms  0.924 ms  1.123 ms
 3  24.105.30.148 (24.105.30.148)  0.967 ms  0.969 ms  1.042 ms
 4  137.221.66.4 (137.221.66.4)  1.834 ms  1.949 ms  1.998 ms
 5  137.221.68.72 (137.221.68.72)  25.923 ms  25.933 ms  25.931 ms
 6  137.221.65.7 (137.221.65.7)  25.726 ms  25.766 ms  25.725 ms
 7  137.221.65.41 (137.221.65.41)  25.713 ms  25.709 ms  25.681 ms
 8  137.221.73.32 (137.221.73.32)  25.582 ms  25.587 ms  25.585 ms
 9  six2.gci.net (206.81.81.63)  25.658 ms  25.598 ms  25.814 ms
10  * * *
11  * * *
12  * * *
13  * * *
14  * * *
15  * * *


20/09/2018 06:27:40 UTC
--------------------

TRACEROUTE:
traceroute to 24.237.56.98 (24.237.56.98), 15 hops max, 60 byte packets
 1  Blizzard Blizzard  2.391 ms  2.380 ms  2.382 ms
 2  37.244.23.2 (37.244.23.2)  2.398 ms  2.399 ms  3.038 ms
 3  24.105.62.146 (24.105.62.146)  2.373 ms  2.373 ms  2.375 ms
 4  137.221.66.8 (137.221.66.8)  2.985 ms  3.012 ms  3.020 ms
 5  137.221.69.70 (137.221.69.70)  51.014 ms  51.035 ms  51.038 ms
 6  137.221.65.43 (137.221.65.43)  50.861 ms  50.762 ms  50.718 ms
 7  137.221.73.32 (137.221.73.32)  50.473 ms  50.498 ms  50.653 ms
 8  six2.gci.net (206.81.81.63)  50.626 ms  50.529 ms  50.733 ms
 9  * * *
10  * * *
11  * * *
12  * * *
13  * * *
14  * * *
15  * * *


20/09/2018 06:27:40 UTC
--------------------

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

--- 24.237.56.98 ping statistics ---
4 packets transmitted, 0 received, 100% packet loss, time 2998ms



20/09/2018 06:27:40 UTC
--------------------

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

--- 24.237.56.98 ping statistics ---
4 packets transmitted, 0 received, 100% packet loss, time 2999ms



20/09/2018 06:27:40 UTC
--------------------

MTR:
Start: Thu Sep 20 06:27:40 2018 Blizzard  1.|-- Blizzard      0.0%    10    0.3   0.3   0.3   0.3   0.0
  2.|-- 37.244.22.3       0.0%    10    0.5   0.5   0.5   0.7   0.0
  3.|-- 24.105.30.148     0.0%    10    1.2   1.1   0.9   1.2   0.0
  4.|-- 137.221.66.4      0.0%    10    1.4   1.5   1.4   1.6   0.0
  5.|-- 137.221.68.72     0.0%    10   27.2  26.6  25.6  33.1   2.3
  6.|-- 137.221.65.7      0.0%    10   25.8  25.7  25.7  25.8   0.0
  7.|-- 137.221.65.41     0.0%    10   25.7  25.7  25.7  25.8   0.0
  8.|-- 137.221.73.32     0.0%    10   25.6  25.6  25.5  25.7   0.0
  9.|-- six2.gci.net      0.0%    10   25.7  25.6  25.6  25.8   0.0
 10.|-- ???              100.0    10    0.0   0.0   0.0   0.0   0.0


20/09/2018 06:27:40 UTC
--------------------

MTR:
Start: Thu Sep 20 06:27:40 2018 Blizzard  1.|-- Blizzard      0.0%    10    0.4   0.4   0.3   0.4   0.0
  2.|-- 37.244.23.2       0.0%    10    0.5   0.6   0.5   0.8   0.0
  3.|-- 24.105.62.146     0.0%    10    1.0   1.0   0.8   1.3   0.0
  4.|-- 137.221.66.8      0.0%    10    1.9   1.9   1.8   2.1   0.0
  5.|-- 137.221.69.70     0.0%    10   53.7  54.3  50.5  84.8  10.7
  6.|-- 137.221.65.43     0.0%    10   50.6  50.7  50.6  51.2   0.0
  7.|-- 137.221.73.32     0.0%    10   50.3  50.4  50.3  50.5   0.0
  8.|-- six2.gci.net      0.0%    10   50.5  50.6  50.4  51.1   0.0
  9.|-- ???              100.0    10    0.0   0.0   0.0   0.0   0.0


20/09/2018 06:27:40 UTC
--------------------

Nicole-1893 · September 21, 2018, 4:07pm

Yes it is

Kaedi-11739 · September 21, 2018, 8:55pm

xperii, it looks like you provided the Traceroute from a Looking Glass test, but it looks incomplete. Can you try running a WinMTR test instead?

WinMTR instructions:

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.)
Unzip the WinMTR.zip file to the Desktop.
Open the WinMTR folder and select the 32 or 64 bit version. Choose whichever one corresponds to your version of Windows.
Run the WinMTR.exe
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.

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
Once you notice the connection issue while playing, play for about 6 more minutes, minimize the game and click on “Stop”.
Click on “Copy text to clipboard”, then return to this forum thread.
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
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

scur-1299 · September 23, 2018, 11:40pm

I’m in Alaska and have the same problem. I just emailed GCI about it and I think anyone else who has the same problem should do that too. They won’t know it’s an issue unless we tell them.

Nicole-1893 · September 24, 2018, 3:47am

Thank you for being proactive!

Toast59-1684 · November 15, 2018, 1:43am

Hi! This is a bit of a late response, however, I’m in Anchorage as well and I’m experiencing identical latency issues to the ones you had outlined. I was devastated to find that my latency degraded so much in such a short period, so I ended up using Haste in a desperate attempt to resolve the issues… and it worked! It’s not the best solution, but it at least made the game enjoyable again.