I’ve talked to Blizzard staff over the past week and after running many tests, and troubleshooting, they have come to the conclusion that my higher than average ping isn’t a problem I can fix on my end.
Here is the last update I got:
Howdy!
I am Game Master and Tech Specialist Vladosiky and I am here to address your connection concern!
I apologize for the confusion. Nothing you do on your end will change the route to our servers. This would be a routing issue outside of your control. Overwatch runs a “ping” test once you connect to the game and will place you on the server that has the best ping available. There is no way around this on your end.
If any routes to the best server have congestion or packet loss, it will default you the next best option. The path pings and trace routes look fine in the most recent ones on dropbox. I am not sure why you are being routed to a different server, or experiencing the latency that you are with those tests.
This would be a routing issue outside of your control. I would recommend making a forum topic at: “Overwatch Technical Forums Link Here” asking if anyone else with a Telus Communications connection is experiencing higher than normal latency or are being routed to a different location.
This will help us see if it is area wide and we can track the issue. With more information about who is experiencing it, we can see if there is anything possible we can do on our end.
Thank you again for the information, and hopefully it will be resolved soon.
![:slight_smile:](https://d74zh8edaijub.cloudfront.net/en/overwatch/images/emoji/twitter/slight_smile.png?v=5" ":slight_smile:")
In an effort to help find the cause of this problem, I’m asking that anyone in Alberta area or Canada in general post here if they are having ping problems as of late. This includes:
- Higher than average ping (for the past 2 weeks roughly)
- Noticeable ping spikes during gameplay
- Non-optimal server connection (not the best possible server to be connected on)
- Ping fluctuations from day to day
To help narrow down the problem and insure it’s related please post with this template filled out:
General
- Location (Province or Territory/City):
- Internet service provider (Telus, Shaw, Rogers, Tbaytel, ect…):
- Connection type (Cable, Wifi, Hotspot, from Mobile device):
- Any addition networking software/settings (VPN, Proxy, Virtual Machine Adapters, Firewalls, Antivirus, Custom Windows firewall settings):
Overwatch
- Connected server IP (See optional section):
- Average ping (Example 104-110ms):
- Game modes tested (Practice range, Quick play, Custom, Arcade, Competitive):
- Does ping differ from day to day (Yes, no, unsure):
Optional
If you are willing, provide a traceroute, pathping, dxdiag, and msinfo report. Please include these in Blockquote to make scrolling easier for everyone.
- Getting connected server IP:
You can use the in-game Network Graph to find your server’s IP address.
- Launch Overwatch and click Play -> Game Browser.
- Use the + Create button to create your own match.
- Click the ADD AI button and click Add.
- Start the game.
- After the map loads, press Ctrl+Shift+N to open the Network Graph.
- The server’s IP address is listed in the upper left of the graph.
- Note: You need to remove the port and preceding colon (12.345.67.89:PORT) from the IP address before running a test
- Getting traceroute report:
- Click Start. Windows 8® users start on step
- In the search field, type cmd.
- Right-click on CMD.exe and select Run as Administrator.
- Enter the command tracert xx.xx.xx.xx > c:\tracert.txt and press Enter. Note: Replace the Xs with the appropriate IP address from the list below. Run this command once per IP address for your region.
- Allow several minutes for the traceroute to complete. When you see a new line of text in the command prompt, the traceroute is done. This creates a file on your C: drive called tracert.txt. Note: If you receive an error, you did not run the command prompt in Administrator Mode. Go back to step three and try again.
- Close the command window.
- Getting a pathping report:
- Click Start.
- In the search field, type cmd.
- Right-click on CMD.exe and select Run as Administrator.
- Enter the command pathping xx.xx.xx.xx > c:\pathping.txt and press Enter.
- Note: Replace the Xs with the appropriate IP address from the list below. Run this command once per IP address for your region.
- Allow several minutes for the test to complete. When you see a new line of text in the command prompt, the pathping is done. This creates a file on your C: drive called pathping.txt. Note: If you receive an error, you did not run the command prompt in Administrator Mode. Go back to step three and try again.
- Close the command window.
- Getting MSInfo report:
- Press Windows Key + R.
- Type MSInfo32 and press Enter.
- In the System Information window, click File, then Export.
- When the Export As window appears, choose Desktop.
- Name the file “MSInfo” and click Save.
- Getting DxDiag report:
- Press Windows Key + R.
- Type DxDiag and press Enter.
- In the DxDiag window, click Save All Information.
- Name the file “dxdiag” and click Save.