High latency in OW1 since installing OW2 PVP beta

Technical Support
1

While normally I get 70/75 ms ping, since 4/28/22 I’ve been having double that amount, at 148-152ms on both OW1 and OW2 PVP Beta. I hadn’t played the game since then, and last night i noticed the high latency was still and issue, and continues today. My ISP is Mediacom, I am on a wired connection. 201.1 Mbps down, 17.5 Mbps up. Thanks for any help in advance.


Tracing route to 24.105.42.109 over a maximum of 30 hops

  0  DESKTOP-9LOC1FI [192.168.0.111] 
  1  192.168.0.1 
  2  10.214.128.1 
  3  172.30.15.89 
  4  hu0-1-0-4.chgil001cr1.mchsi.com [68.66.73.140] 
  5  po10.chgil001er1.mchsi.com [68.66.73.122] 
  6  137.221.66.164 
  7  ae1-br02-eqch2.as57976.net [137.221.69.35] 
  8  et-0-0-1-pe01-eqch2.as57976.net [137.221.69.51] 
  9     *        *        *     
Computing statistics for 200 seconds...
            Source to Here   This Node/Link
Hop  RTT    Lost/Sent = Pct  Lost/Sent = Pct  Address
  0                                           DESKTOP-9LOC1FI [192.168.0.111] 
                                0/ 100 =  0%   |
  1    0ms     0/ 100 =  0%     0/ 100 =  0%  192.168.0.1 
                                0/ 100 =  0%   |
  2   10ms     0/ 100 =  0%     0/ 100 =  0%  10.214.128.1 
                                0/ 100 =  0%   |
  3   85ms     0/ 100 =  0%     0/ 100 =  0%  172.30.15.89 
                                0/ 100 =  0%   |
  4  130ms     0/ 100 =  0%     0/ 100 =  0%  hu0-1-0-4.chgil001cr1.mchsi.com [68.66.73.140] 
                                0/ 100 =  0%   |
  5  121ms     0/ 100 =  0%     0/ 100 =  0%  po10.chgil001er1.mchsi.com [68.66.73.122] 
                                0/ 100 =  0%   |
  6  133ms     0/ 100 =  0%     0/ 100 =  0%  137.221.66.164 
                                0/ 100 =  0%   |
  7  135ms     0/ 100 =  0%     0/ 100 =  0%  ae1-br02-eqch2.as57976.net [137.221.69.35] 
                                0/ 100 =  0%   |
  8  122ms     0/ 100 =  0%     0/ 100 =  0%  et-0-0-1-pe01-eqch2.as57976.net [137.221.69.51] 

Trace complete.



Tracing route to 24.105.42.109 over a maximum of 30 hops

  1    <1 ms     2 ms    <1 ms  192.168.0.1 
  2    16 ms     8 ms    11 ms  10.214.128.1 
  3    86 ms    87 ms    85 ms  172.30.15.89 
  4   140 ms   137 ms   141 ms  hu0-1-0-4.chgil001cr1.mchsi.com [68.66.73.140] 
  5   127 ms   127 ms   128 ms  po10.chgil001er1.mchsi.com [68.66.73.122] 
  6   128 ms   128 ms   127 ms  137.221.66.164 
  7   184 ms   879 ms   439 ms  ae1-br02-eqch2.as57976.net [137.221.69.35] 
  8   126 ms   135 ms   129 ms  et-0-0-1-pe01-eqch2.as57976.net [137.221.69.51] 
  9     *        *        *     Request timed out.
 10     *        *        *     Request timed out.
 11     *        *        *     Request timed out.
 12     *        *        *     Request timed out.
 13     *        *        *     Request timed out.
 14     *        *        *     Request timed out.
 15     *        *        *     Request timed out.
 16     *        *        *     Request timed out.
 17     *        *        *     Request timed out.
 18     *        *        *     Request timed out.
 19     *        *        *     Request timed out.
 20     *        *        *     Request timed out.
 21     *        *        *     Request timed out.
 22     *        *        *     Request timed out.
 23     *        *        *     Request timed out.
 24     *        *        *     Request timed out.
 25     *        *        *     Request timed out.
 26     *        *        *     Request timed out.
 27     *        *        *     Request timed out.
 28     *        *        *     Request timed out.
 29     *        *        *     Request timed out.
 30     *        *        *     Request timed out.

Trace complete.


MTR:
Start: Thu May  5 06:56:29 2022 Blizzard  1.|-- Blizzard                    0.0%    10    0.2   0.3   0.2   0.3   0.0
  2.|-- 37.244.23.3                     0.0%    10    0.5   0.6   0.5   1.0   0.0
  3.|-- 24.105.62.152                   0.0%    10    0.9   0.9   0.7   1.0   0.0
  4.|-- 137.221.66.14                   0.0%    10    2.0   1.2   1.0   2.0   0.0
  5.|-- ???                            100.0    10    0.0   0.0   0.0   0.0   0.0
  6.|-- 137.221.69.32                   0.0%    10   31.2   9.7   2.0  31.2  10.5
  7.|-- 137.221.66.165                  0.0%    10    2.5   2.5   2.4   2.6   0.0
  8.|-- po10.chgil001cr1.mchsi.com      0.0%    10   46.0  45.8  45.7  46.0   0.0
  9.|-- hu5-0-0.fthil001er8.mchsi.com   0.0%    10   45.8  45.5  45.3  45.8   0.0
 10.|-- ???                            100.0    10    0.0   0.0   0.0   0.0   0.0
 11.|-- 173-28-103-92.client.mchsi.com  0.0%    10  120.3 121.3 118.6 125.2   2.3


05/05/2022 06:56:29 UTC
--------------------

MTR:
Start: Thu May  5 06:56:30 2022 Blizzard  1.|-- Blizzard                    0.0%    10    0.3   0.3   0.3   0.4   0.0
  2.|-- 24.105.18.2                     0.0%    10    0.8   0.6   0.5   0.8   0.0
  3.|-- 137.221.105.10                  0.0%    10    0.9   0.9   0.7   1.1   0.0
  4.|-- 137.221.66.16                   0.0%    10    0.7   0.5   0.4   0.7   0.0
  5.|-- 137.221.83.80                   0.0%    10  1020. 529.4  63.2 1125. 428.7
  6.|-- ???                            100.0    10    0.0   0.0   0.0   0.0   0.0
  7.|-- 137.221.69.32                   0.0%    10   67.5  43.7  38.2  67.5  11.4
  8.|-- 137.221.66.165                  0.0%    10   38.5  38.7  38.5  39.3   0.0
  9.|-- po10.chgil001cr1.mchsi.com      0.0%    10   81.8  81.9  81.8  82.0   0.0
 10.|-- hu5-0-0.fthil001er8.mchsi.com   0.0%    10   81.9  83.2  81.7  92.5   3.4
 11.|-- ???                            100.0    10    0.0   0.0   0.0   0.0   0.0
 12.|-- 173-28-103-92.client.mchsi.com  0.0%    10  164.2 168.1 164.0 177.4   4.0


05/05/2022 06:56:29 UTC
--------------------
2

The two clients share some assets, but they have no bearing on your latency.

Your tests are showing high ping on mchsi nodes leading into Chicago.

1 <1 ms 2 ms <1 ms 192.168.0.1 — home equipment
2 16 ms 8 ms 11 ms 10.214.128.1 — ISP local node
3 86 ms 87 ms 85 ms 172.30.15.89 — ISP node
4 140 ms 137 ms 141 ms hu0-1-0-4.chgil001cr1.mchsi.com [68.66.73.140] — ISP node/peer

All of these hops are before you reach the game servers.

3

I’m not entirely sure what that means. Is this something that I can fix on my end, or is it related to my ISP? Thanks

4

Contact your ISP and if possible share these test results with them. It may take them time to fix it. Alternatively, try running a VPN service to see if you can connect to the game better.

5

I got in contact with my ISP. I told them that I had high latency on a node leading into Chicago before reaching the Overwatch game servers. They had me run a Speed Test, which came back at 15 ms 267/21 Mbps. I spoke with a lvl 1 and lvl 2 tech support specialists, and they assured me that I had no connection problems, and that the were not the ones routing the connection to Chicago. They told me that is was an issue with Blizzard, as all other games I play aren’t having high latency. They told me they aren’t the ones that route the connection to the game servers. They also recommended I inquire about ping tunneling from you guys to get a direct connection. At this point, this has been happening for three weeks almost.

Why would I be getting routed into a node in Chicago when I live in southern arizona?

6

A speed test pings a server closest to you, and is not an accurate measure of your connection quality or routing.

Neither level is likely to understand about the routing mechanisms that the ISP uses. You usually need Level 3.

Because all players in North America can land on Los Angeles or Chicago servers. That is the intended behavior to create matches based on mode selected, rank, and group size.

7

So why am I getting routed to the server that is geographically further away from me, when I have one that is is L.A? What is the logic behind getting routed to the furthest server from me geographically and thus giving me higher latency when I have one in L.A.? Who routes the connection? Because at this point, both Blizzard and my ISP are playing a game of hot potato blaming each other and the end product is that the game is unplayable, when up to the 28th of April, everything was working as it needed to. Also, why is this only happening with Overwatch?

UPDATE: I spoke with Mediacom level 3 OP. I was informed that there was noise in my connection, and they are having a technician come out to check it out tomorrow. I hope that resolves the issues, but I’m still confused as to how my connection is routed. Is that something that gets determined by my ISP, or by Blizzard? And why would it only be happening with Overwatch?

1 Like
8

Asked and answered above. However, this thread was originally about latency, not server location. High ping spikes are showing on the ISP network heading into Chicago. The route to LA might be spotless in terms of high pings, but ideally, it should be that way for both locations.

Blizzard doesn’t handle routing, only server-matching. If you are in Diamond and other players available for the LA server are only in Bronze or GM, you aren’t likely to be matched with them. Your ISP helps route the connection after receiving info from the game client as to where the endpoint/destination is located.

Games like WoW or Final Fantasy have fixed servers; you are always logging in to a specific server in a datacenter/city. That is not how Overwatch matchmaking works.

The server matching for Overwatch is dynamic. In this case, your region is North America. I am also in the NA region, located in the Southeast U.S. I am often matched to the LA (farther) server instead of Chicago (closer) server due to the times of day I play, as well as modes.

Again, this is perfectly normal/expected and isn’t going to change even if your ISP comes out and looks at your connection. Noise on your connection will affect connection quality, but not which server you land on.

You should only be concerned if you are located in Arizona and being matched onto servers in Europe or Asia. In that case, you’d be looking at an ISP routing issue.

9

I’m having a similar issue, except I’m not experiencing disconnections frequently. I struggle more with random intense spikes in latency, causing rubber banding. When I run a ping test I see no loss in packets and my ISP network tests detect no problems. I only experience lags on Overwatch so I’d like to see if we can identify a problem there. I ran the WinMTR test and followed instructed to find my connected server’s IP through shift+CTRL+N and used the address given to put into the Host section. When I run a test it just repeats “No response from host”. Am I doing something wrong or should I send the results anyway?

10

The OP didn’t mention disconnections.

A ping test is instant and generally doesn’t provide any valuable troubleshooting info for the problem you’re describing.

It sounds like you’re adding extra port numbers not needed for the test.

Please start your own thread for troubleshooting.

11

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.