High Latency Issue for 6 months

Technical Support
1

I don’t have exact number and months or days that my ping goes up constantly but, I think it went through stages. like I use to have 30-40 ping. then 60-70 (I ignored it) , then it became 80-90 (its still fine), now its 95+ to 130 or up. basically its unplayable and it causes rubber bonding constantly.
I even check the games that I still play today and there’s no lag or anything even test ping online I still have 35 ms. or 30 or 25. I only have this amount of ping lately in overwatch I am not sure why.

I joined a match today and I ask my teammates and enemies which part of US are they playing and they said they are in EAST coast mostly, so I am wondering I am being directed to east coast, instead of West coast server.

I need help regarding this issue.

TRACEROUTE:
traceroute to 50.80.90.109 (50.80.90.109), 15 hops max, 60 byte packets
1 Blizzard Blizzard 3.692 ms 3.689 ms 3.693 ms
2 24.105.18.131 (24.105.18.131) 32.277 ms 32.299 ms 32.304 ms
3 137.221.105.12 (137.221.105.12) 4.688 ms 4.766 ms 4.778 ms
4 137.221.66.20 (137.221.66.20) 4.726 ms 4.730 ms 4.757 ms
5 137.221.83.68 (137.221.83.68) 41.388 ms 41.407 ms 41.411 ms
6 * * *
7 137.221.69.32 (137.221.69.32) 38.023 ms 38.052 ms 38.053 ms
8 137.221.66.165 (137.221.66.165) 38.367 ms 38.607 ms 38.685 ms
9 po10.chgil001cr1. mchsi. com (68.66.73.121) 81.259 ms 81.374 ms 81.385 ms
10 hu5-0-0.fthil001er8. mchsi. com (68.66.73.141) 81.720 ms 81.600 ms 81.657 ms
11 * * *
12 50-80-90-109. client.mchsi. com (50.80.90.109) 103.087 ms 103.117 ms 102.972 ms

19/03/2019 04:29:39 UTC

TRACEROUTE:
traceroute to 50.80.90.109 (50.80.90.109), 15 hops max, 60 byte packets
1 Blizzard Blizzard 0.244 ms 0.254 ms 0.266 ms
2 24.105.18.131 (24.105.18.131) 0.475 ms 0.579 ms 0.677 ms
3 137.221.105.12 (137.221.105.12) 1.180 ms 1.253 ms 1.284 ms
4 137.221.66.20 (137.221.66.20) 1.210 ms 1.221 ms 1.252 ms
5 137.221.83.68 (137.221.83.68) 37.998 ms 38.068 ms 38.092 ms
6 * * *
7 137.221.69.32 (137.221.69.32) 37.626 ms 37.659 ms 37.804 ms
8 137.221.66.165 (137.221.66.165) 37.824 ms 37.945 ms 38.189 ms
9 po10.chgil001cr1 .mchsi. com (68.66.73.121) 81.307 ms 81.338 ms 81.346 ms
10 hu5-0-0.fthil001er8. mchsi. com (68.66.73.141) 81.569 ms 81.624 ms 81.808 ms
11 * * *
12 50-80-90-109.client. mchsi. com (50.80.90.109) 102.456 ms 102.465 ms 101.647 ms

19/03/2019 04:29:40 UTC

PING:
PING 50.80.90.109 (50.80.90.109) 56(84) bytes of data.
64 bytes from 50.80.90.109: icmp_seq=1 ttl=53 time=107 ms
64 bytes from 50.80.90.109: icmp_seq=2 ttl=53 time=119 ms
64 bytes from 50.80.90.109: icmp_seq=3 ttl=53 time=103 ms
64 bytes from 50.80.90.109: icmp_seq=4 ttl=53 time=103 ms

— 50.80.90.109 ping statistics —
4 packets transmitted, 4 received, 0% packet loss, time 2998ms
rtt min/avg/max/mdev = 103.405/108.400/119.499/6.605 ms

19/03/2019 04:29:39 UTC

PING:
PING 50.80.90.109 (50.80.90.109) 56(84) bytes of data.
64 bytes from 50.80.90.109: icmp_seq=1 ttl=53 time=106 ms
64 bytes from 50.80.90.109: icmp_seq=2 ttl=53 time=107 ms
64 bytes from 50.80.90.109: icmp_seq=3 ttl=53 time=107 ms
64 bytes from 50.80.90.109: icmp_seq=4 ttl=53 time=119 ms

— 50.80.90.109 ping statistics —
4 packets transmitted, 4 received, 0% packet loss, time 2999ms
rtt min/avg/max/mdev = 106.721/110.068/119.362/5.378 ms

19/03/2019 04:29:40 UTC

MTR:
Start: Tue Mar 19 04:29:39 2019 Blizzard 1.|-- Blizzard 0.0% 10 0.3 0.3 0.2 0.5 0.0
2.|-- 24.105.18.131 0.0% 10 0.5 0.6 0.5 0.9 0.0
3.|-- 137.221.105.12 0.0% 10 0.6 0.9 0.4 2.8 0.5
4.|-- 137.221.66.20 0.0% 10 0.7 0.7 0.5 0.9 0.0
5.|-- 137.221.83.68 0.0% 10 38.7 46.9 37.8 87.2 18.8
6.|-- 137.221.65.133 0.0% 10 3204. 6501. 3204. 9913. 2298.6
7.|-- 137.221.69.32 0.0% 10 37.7 38.7 37.7 45.4 2.3
8.|-- 137.221.66.165 0.0% 10 38.3 38.2 37.9 39.4 0.3
9.|-- po10.chgil001cr1. mchsi. com 0.0% 10 81.3 81.3 81.1 81.5 0.0
10.|-- hu5-0-0.fthil001er8. mchsi. com 0.0% 10 82.0 82.1 81.5 85.9 1.1
11.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0
12.|-- 50-80-90-109.client. mchsi. com 0.0% 10 104.1 107.0 102.5 114.8 3.8

19/03/2019 04:29:39 UTC

MTR:
Start: Tue Mar 19 04:29:40 2019 Blizzard 1.|-- Blizzard 0.0% 10 0.3 0.3 0.2 0.5 0.0
2.|-- 24.105.18.131 0.0% 10 0.7 0.9 0.4 3.0 0.5
3.|-- 137.221.105.12 0.0% 10 0.6 0.6 0.5 0.8 0.0
4.|-- 137.221.66.20 0.0% 10 0.7 0.7 0.6 0.8 0.0
5.|-- 137.221.83.68 0.0% 10 38.0 43.7 37.9 69.2 12.0
6.|-- 137.221.65.133 0.0% 10 2923. 6088. 2923. 9612. 2276.6
7.|-- 137.221.69.32 0.0% 10 37.8 37.9 37.8 38.4 0.0
8.|-- 137.221.66.165 0.0% 10 38.2 38.2 38.1 38.3 0.0
9.|-- po10.chgil001cr1 .mchsi. com 0.0% 10 81.2 81.3 81.2 81.5 0.0
10.|-- hu5-0-0. fthil001er8.mchsi .com 0.0% 10 81.7 81.9 81.7 82.4 0.0
11.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0
12.|-- 50-80-90-109. client.mchsi .com 0.0% 10 109.0 109.5 102.9 118.2 5.4

19/03/2019 04:29:40 UTC

2

Okay, I realize I said make a thread, but this conversation is now taking place in three threads.

So we see you are gaining 40ms ping as soon as the connection is handed off to your ISP. I think a WinMTR will confirm this. The instructions on where to get the app and how to use it are all included on the link I’ve provided each time, and will do so here as well:

1 Like
3

this is the result I got

WinMTR Statistics

WinMTR statistics

Host % Sent Recv Best Avrg Wrst Last
192.168.0.1 2 394 388 1 26 319 3
50-80-90-1.client.mchsi.com 3 383 374 7 40 322 13
172.30.15.45 3 379 369 19 50 353 25
hu0-1-0-4.chgil001cr1.mchsi.com 3 375 364 64 95 383 74
po10.chgil001er1.mchsi.com 3 387 379 62 96 382 72
137.221.66.164 3 375 364 62 94 393 77
ae1-br01-eqch2.as57976.net 2 391 384 65 106 388 74
No response from host 100 83 0 0 0 0 0
No response from host 100 83 0 0 0 0 0
No response from host 100 83 0 0 0 0 0
No response from host 100 83 0 0 0 0 0
No response from host 100 83 0 0 0 0 0
No response from host 100 83 0 0 0 0 0
No response from host 100 83 0 0 0 0 0
No response from host 100 83 0 0 0 0 0
No response from host 100 83 0 0 0 0 0
No response from host 100 83 0 0 0 0 0
No response from host 100 83 0 0 0 0 0
No response from host 100 83 0 0 0 0 0
No response from host 100 83 0 0 0 0 0
No response from host 100 83 0 0 0 0 0
No response from host 100 83 0 0 0 0 0
No response from host 100 83 0 0 0 0 0
No response from host 100 83 0 0 0 0 0
No response from host 100 83 0 0 0 0 0
No response from host 100 83 0 0 0 0 0
No response from host 100 83 0 0 0 0 0
No response from host 100 83 0 0 0 0 0
No response from host 100 83 0 0 0 0 0
No response from host 100 83 0 0 0 0 0
4

You should always use the IP from the game netgraph, if possible, as instructed on the link. Once you read the steps and select Overwatch from the drop-down box, the instructions on where to get the correct IP appear:

You can use the in-game Network Graph to find your server’s IP address.

  1. Launch Overwatch and click Play -> Game Browser .
  2. Use the + Create button to create your own match.
  3. Click the ADD AI button and click Add .
  4. Start the game.
  5. After the map loads, press Ctrl+Shift+N to open the Network Graph.
  6. 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.

Depending on these results, you might test the general West server IP, but we’ll see.

1 Like
6

I am leaving this reply so you can add your test results. If I have a chance, I will look them over.

As a new member here, it’s worth taking a few minutes to look over this post from the staff, which covers some of the forum rules. These notes will help out if you have any future inquiries.

1 Like
7
WinMTR Statistics

WinMTR statistics

Host % Sent Recv Best Avrg Wrst Last
192.168.0.1 2 762 750 1 26 319 5
50-80-90-1.client.mchsi.com 3 745 729 7 40 324 45
172.30.15.45 2 762 750 19 50 353 30
hu0-1-0-4.chgil001cr1.mchsi.com 2 750 735 62 96 383 77
po10.chgil001er1.mchsi.com 3 723 702 62 92 382 72
137.221.66.164 3 733 715 62 93 393 69
ae1-br01-eqch2.as57976.net 3 721 703 63 146 4902 68
No response from host 100 161 0 0 0 0 0
No response from host 100 161 0 0 0 0 0
No response from host 100 161 0 0 0 0 0
No response from host 100 161 0 0 0 0 0
No response from host 100 161 0 0 0 0 0
No response from host 100 161 0 0 0 0 0
No response from host 100 161 0 0 0 0 0
No response from host 100 161 0 0 0 0 0
No response from host 100 161 0 0 0 0 0
No response from host 100 161 0 0 0 0 0
No response from host 100 161 0 0 0 0 0
No response from host 100 161 0 0 0 0 0
No response from host 100 161 0 0 0 0 0
No response from host 100 161 0 0 0 0 0
No response from host 100 161 0 0 0 0 0
No response from host 100 161 0 0 0 0 0
No response from host 100 161 0 0 0 0 0
No response from host 100 161 0 0 0 0 0
No response from host 100 161 0 0 0 0 0
No response from host 100 161 0 0 0 0 0
No response from host 100 161 0 0 0 0 0
No response from host 100 161 0 0 0 0 0
No response from host 100 161 0 0 0 0 0
8

You’re losing 2% of your data between your computer and router, and have a high worst response time of 319ms. This means the connection to your home equipment is unstable and likely causing your issue.

If you’re wireless, try wired. If you’re wired, try another port on the device or a new cable. If none of that helps, you’ll need to replace it. If it’s equipment owned by your ISP, you’ll need to schedule service or a hardware swap.

It’s also possible your issue is multiple things, but this is where you should start.

1 Like
9

so I did that trying another port and I restarted it as well I think it gotten a little better now. I am not quite sure but I have to check in the real competitive match. because the server keep putting me to a different server. so that causes the issue as well? If I remember last month this issue started when I joined a game and suddenly I was put in South American server, where everyone talks Spanish. or latin. I am pretty sure that I also ask my teammates when I joined a match in competitive they are all saying they are East coast. is that possible? for 2 weeks?

2nd test by the way:

WinMTR Statistics

WinMTR statistics

Host % Sent Recv Best Avrg Wrst Last
192.168.0.1 0 119 119 1 3 13 2
50-80-90-1.client.mchsi.com 0 119 119 7 18 69 18
172.30.15.45 0 119 119 20 29 48 29
hu0-1-0-4.chgil001cr1.mchsi.com 0 119 119 63 71 81 74
po10.chgil001er1.mchsi.com 0 119 119 63 72 84 72
137.221.66.164 0 119 119 62 71 90 72
ae1-br02-eqch2.as57976.net 0 119 119 67 86 333 137
No response from host 100 23 0 0 0 0 0
No response from host 100 23 0 0 0 0 0
No response from host 100 23 0 0 0 0 0
No response from host 100 23 0 0 0 0 0
No response from host 100 23 0 0 0 0 0
No response from host 100 23 0 0 0 0 0
No response from host 100 23 0 0 0 0 0
No response from host 100 23 0 0 0 0 0
No response from host 100 23 0 0 0 0 0
No response from host 100 23 0 0 0 0 0
No response from host 100 23 0 0 0 0 0
No response from host 100 23 0 0 0 0 0
No response from host 100 23 0 0 0 0 0
No response from host 100 23 0 0 0 0 0
No response from host 100 23 0 0 0 0 0
No response from host 100 23 0 0 0 0 0
No response from host 100 23 0 0 0 0 0
No response from host 100 23 0 0 0 0 0
No response from host 100 23 0 0 0 0 0
No response from host 100 23 0 0 0 0 0
No response from host 100 23 0 0 0 0 0
No response from host 100 23 0 0 0 0 0
No response from host 100 23 0 0 0 0 0
10

I can’t answer questions about what happened in the past without looking at data for those connections.

Run a WinMTR to the West Coast server this time and post results. However, make sure you run for 10 mins this time.

1 Like
11
WinMTR Statistics

WinMTR statistics

Host % Sent Recv Best Avrg Wrst Last
192.168.0.1 0 967 967 1 10 305 2
50-80-90-1.client.mchsi.com 1 952 948 5 21 322 16
172.30.15.45 1 948 943 19 34 333 27
hu0-1-0-4.chgil001cr1.mchsi.com 1 963 962 62 79 381 71
po10.chgil001er1.mchsi.com 1 963 962 61 78 380 71
137.221.66.164 1 948 943 62 78 381 75
ae1-br01-eqch2.as57976.net 1 951 949 104 139 4280 152
137.221.65.132 1 952 948 104 122 434 109
et-0-0-2-br01-eqla1.as57976.net 1 948 943 64 85 380 71
be1-pe01-eqla1.as57976.net 1 963 962 104 119 413 115
24.105.30.129 1 948 943 104 120 416 115
12

Your home equipment didn’t lose data in this test, but it’s still responding slowly at times. However, the ISP lines right after your modem are showing 1% packet loss, which means this is likely something your ISP is going to need to address for you.

1 Like
13

so this causes me to be routed on East Coast server? because everytime I play I am in East coast server. I ask my teammate and enemies. they are 3 hours time ahead of me. I called my ISP company today they reset it and stuff. and I tried queing for comp or qp. ping is still the same. I am pretty sure I am being routed to the wrong server aka East coast.
you mind helping me out with this issue? please? or should I start new thread about this?

14

You do not need to start another thread. Unfortunately, where you are routed is usually decided by your ISP.

The above is your ISP line in your city/neighborhood, and then a hub belonging to your ISP, and then your ISP’s hub in Chicago. So since Blizzard sees the connection coming in from Chicago, you’re matched to that server.

1 Like
15

So what should I tell my internet company then? this is really odd.

16

On a side, how old is the CAT-5 cord connecting your machine to your router?

I’ve noticed after a couple years they may start to degrade in quality, depending on where they are. There was some conversation in this thread that the issue was between the Computer and the Router, that is something to consider. (look for damaged insulation on the cord, make sure plugs stay firmly connected, etc…)

1 Like
17

Ask for tier 2 or 3 support and tell them you’re trying to connect to a server in California but being routed to Chicago via the ISP.

1 Like
18

A post was split to a new topic: High Latency Issues