Server status

Technical Support
Your servers are down, I've tried everything, aside from moving to another coast to get on a different server. Please update.
I do believe there is a major issue now forming for some players, as there is a significant increase in reports in the last few minutes. Please help out by describing your platform (PC, XB1, PS4), your ISP, and where you live (City, State if you don't mind). Also try running a WinMTR test or a Looking glass test to help us map out any possible connection issues:

Looking Glass Test: https://us.battle.net/support/en/article/34785

WinMTR instructions:
1. Download WinMTR from http://winmtr.net/download-winmtr/
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 hit Ctrl+Shift+N and it will bring up the ingame network diagnostic graph. 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
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" and paste the results into your reply.

STOP playing Competitive mode whenever you encounter a disconnection. Penalties CANNOT be reversed and continued disconnections will lead to more severe penalties up to and including a season-ban.
TRACEROUTE:
traceroute to 73.83.41.82 (73.83.41.82), 15 hops max, 60 byte packets
1 24.105.30.3 (24.105.30.3) 0.890 ms 0.887 ms 0.906 ms
2 * * *
3 137.221.66.2 (137.221.66.2) 1.194 ms 1.269 ms 1.339 ms
4 137.221.68.66 (137.221.68.66) 1.193 ms 1.292 ms 1.326 ms
5 137.221.68.32 (137.221.68.32) 0.997 ms 1.009 ms 1.010 ms
6 te-0-4-0-10-pe02.600wseventh.ca.ibone.comcast.net (50.242.151.165) 2.372 ms 1.277 ms 1.329 ms
7 be-11587-cr02.losangeles.ca.ibone.comcast.net (68.86.83.17) 2.914 ms 2.931 ms 2.946 ms
8 be-11015-cr02.sunnyvale.ca.ibone.comcast.net (68.86.86.97) 11.030 ms 11.055 ms 11.054 ms
9 be-7922-ar01.burien.wa.seattle.comcast.net (68.86.93.30) 25.426 ms 25.525 ms 25.552 ms
10 po-1-rur01.burlington.wa.seattle.comcast.net (69.139.164.45) 28.843 ms 28.797 ms 28.835 ms
11 po-1-1-cbr03.burlington.wa.seattle.comcast.net (68.85.241.182) 28.885 ms 28.889 ms 28.894 ms
12 c-73-83-41-82.hsd1.wa.comcast.net (73.83.41.82) 37.822 ms 39.626 ms 45.607 ms

22/01/2018 19:09:22 UTC
--------------------

MTR:
Start: Mon Jan 22 19:09:22 2018
HOST: Blizzard Loss% Snt Last Avg Best Wrst StDev
1.|-- 24.105.30.3 0.0% 10 0.5 2.0 0.4 11.5 3.4
2.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0
3.|-- 137.221.66.2 0.0% 10 1.4 1.3 1.2 1.4 0.0
4.|-- 137.221.68.66 0.0% 10 1.3 1.3 1.2 1.3 0.0
5.|-- 137.221.68.32 0.0% 10 1.0 1.0 0.9 1.1 0.0
6.|-- te-0-4-0-10-pe02.600wseventh.ca.ibone.comcast.net 0.0% 10 1.3 1.3 1.2 1.4 0.0
7.|-- be-11587-cr02.losangeles.ca.ibone.comcast.net 0.0% 10 3.3 2.7 1.5 3.5 0.5
8.|-- be-11015-cr02.sunnyvale.ca.ibone.comcast.net 0.0% 10 9.4 10.3 9.4 11.0 0.3
9.|-- be-7922-ar01.burien.wa.seattle.comcast.net 0.0% 10 25.4 25.5 25.4 25.8 0.0
10.|-- po-1-rur01.burlington.wa.seattle.comcast.net 0.0% 10 28.9 28.9 28.9 28.9 0.0
11.|-- po-1-1-cbr03.burlington.wa.seattle.comcast.net 0.0% 10 28.9 28.9 28.9 29.0 0.0
12.|-- c-73-83-41-82.hsd1.wa.comcast.net 0.0% 10 37.8 39.2 37.6 41.7 1.0

22/01/2018 19:09:22 UTC
--------------------
100% loss?
01/22/2018 11:11 AMPosted by BT160530
100% loss?


Some hubs are configured to not respond to ping tests, so this may or may not be a problem. That one you are seeing is a usual non-responsive so I don't often count that one.
Verizon Fios user here. High ping and disconnection problem for almost three days. Till today I still got placed in Brazil/Singapore servers when I was playing in east coast. The only way I am able to connect back to NA server is to use VPN. After that it was back to normal, ping dropping to 40ms from ~300 when connecting to Brazil/Singapore server.
Hey folks, our network engineers have investigated an issue causing connection problems for some west coast players. They've made a change to mitigate the problem and players who were affected should have stable connections now.
Yeah my ping can be 69 70 then everything stops moving except me then I glitch back with 350 ping on Xbox one pls help and right now 165 ping in practice range!!

Join the Conversation

Return to Forum