High ping (israel)

again there is a problem for israel players getting higher pings ,this is not the first time this happen, just last year after an update of overwatch you log and your ping is higher, this same problem is here again, an increase of latency to around 125 ms from a normal 85-95 for me, i already seen other posts in the forum from the last days suggesting its happening again, i used the spyglass tool to run the test if there is anything else i need to provide let me know

TRACEROUTE:
traceroute to 37.142.159.179 (37.142.159.179), 15 hops max, 60 byte packets
1 Blizzard Blizzard 0.352 ms 0.345 ms 0.346 ms
2 37.244.24.130 (37.244.24.130) 0.528 ms 0.624 ms 0.699 ms
3 Blizzard Blizzard 1.251 ms 1.357 ms 1.417 ms
4 137.221.66.44 (137.221.66.44) 1.344 ms 1.486 ms 1.502 ms
5 137.221.78.72 (137.221.78.72) 6.900 ms 6.919 ms 6.923 ms
6 137.221.65.90 (137.221.65.90) 6.698 ms 6.971 ms 6.941 ms
7 137.221.79.32 (137.221.79.32) 7.088 ms 6.899 ms 6.880 ms
8 e-lon-cor-r2fe911.uklon.ecs-ip. net (195.66.236.91) 41.749 ms 40.866 ms 40.828 ms
9 mad1-cr1-hu5-0-0.cprm. net (195.8.0.238) 36.622 ms 36.867 ms 36.967 ms
10 213.248.76.185 (213.248.76.185) 38.190 ms 38.031 ms 38.248 ms
11 prs-bb3-link.telia. net (62.115.139.134) 43.699 ms 43.620 ms 43.561 ms
12 ldn-bb3-link.telia. net (62.115.134.93) 45.213 ms 45.023 ms 45.045 ms
13 ldn-b1-link.telia. net (62.115.114.235) 45.232 ms 45.177 ms 46.697 ms
14 * * *
15 * * *

06/10/2019 22:34:35 UTC

TRACEROUTE:
traceroute to 37.142.159.179 (37.142.159.179), 15 hops max, 60 byte packets
1 Blizzard Blizzard 0.365 ms 1.114 ms 1.119 ms
2 37.244.25.2 (37.244.25.2) 1.116 ms 1.114 ms 1.115 ms
3 Blizzard Blizzard 1.459 ms 1.506 ms 1.558 ms
4 137.221.66.38 (137.221.66.38) 1.115 ms 1.132 ms 1.182 ms
5 137.221.77.72 (137.221.77.72) 7.657 ms 7.675 ms 7.678 ms
6 137.221.65.19 (137.221.65.19) 14.778 ms 12.136 ms 12.087 ms
7 137.221.79.34 (137.221.79.34) 7.572 ms 7.693 ms 7.651 ms
8 e-lon-cor-r2fe911.uklon.ecs-ip. net (195.66.236.91) 33.135 ms 33.152 ms 33.151 ms
9 mad1-cr1-hu5-0-0.cprm. net (195.8.0.238) 32.040 ms 32.006 ms 32.064 ms
10 213.248.76.185 (213.248.76.185) 38.701 ms 35.257 ms 35.214 ms
11 prs-bb3-link.telia. net (62.115.139.134) 47.280 ms 47.261 ms 47.095 ms
12 ldn-bb3-link.telia. net (62.115.134.93) 49.665 ms 49.855 ms 49.903 ms
13 ldn-b1-link.telia. net (62.115.114.235) 48.619 ms 49.780 ms 49.117 ms
14 * * *
15 * * *

06/10/2019 22:34:35 UTC

PING:
PING 37.142.159.179 (37.142.159.179) 56(84) bytes of data.
64 bytes from 37.142.159.179: icmp_seq=1 ttl=48 time=110 ms
64 bytes from 37.142.159.179: icmp_seq=2 ttl=48 time=109 ms
64 bytes from 37.142.159.179: icmp_seq=3 ttl=48 time=107 ms
64 bytes from 37.142.159.179: icmp_seq=4 ttl=48 time=108 ms

— 37.142.159.179 ping statistics —
4 packets transmitted, 4 received, 0% packet loss, time 2998ms
rtt min/avg/max/mdev = 107.895/108.955/110.585/1.049 ms

06/10/2019 22:34:35 UTC

PING:
PING 37.142.159.179 (37.142.159.179) 56(84) bytes of data.
64 bytes from 37.142.159.179: icmp_seq=1 ttl=47 time=111 ms
64 bytes from 37.142.159.179: icmp_seq=2 ttl=47 time=111 ms
64 bytes from 37.142.159.179: icmp_seq=3 ttl=47 time=111 ms
64 bytes from 37.142.159.179: icmp_seq=4 ttl=47 time=111 ms

— 37.142.159.179 ping statistics —
4 packets transmitted, 4 received, 0% packet loss, time 2999ms
rtt min/avg/max/mdev = 111.463/111.685/111.987/0.405 ms

06/10/2019 22:34:35 UTC

MTR:
Start: Sun Oct 6 22:34:35 2019 Blizzard 1.|-- Blizzard 0.0% 10 0.4 0.4 0.3 0.5 0.0
2.|-- 37.244.24.130 0.0% 10 0.8 0.7 0.5 1.2 0.0
3.|-- Blizzard 0.0% 10 1.4 1.5 1.2 1.9 0.0
4.|-- 137.221.66.44 0.0% 10 1.2 1.4 1.1 2.9 0.3
5.|-- 137.221.78.72 0.0% 10 3377. 1068. 6.8 3377. 1337.7
6.|-- 137.221.65.90 0.0% 10 6.8 6.9 6.8 7.2 0.0
7.|-- 137.221.79.32 0.0% 10 7.0 8.3 6.9 19.0 3.8
8.|-- e-lon-cor-r2fe911.uklon.ecs-ip. net 0.0% 10 40.7 40.0 38.0 42.6 1.5
9.|-- mad1-cr1-hu5-0-0.cprm. net 0.0% 10 36.7 36.7 36.6 36.9 0.0
10.|-- 213.248.76.185 0.0% 10 38.3 38.6 38.2 40.3 0.6
11.|-- prs-bb3-link.telia. net 0.0% 10 43.7 43.8 43.6 44.0 0.0
12.|-- ldn-bb3-link.telia. net 0.0% 10 45.0 45.6 45.0 48.0 0.7
13.|-- ldn-b1-link.telia. net 0.0% 10 45.3 46.8 45.2 58.4 4.1
14.|-- hotnet-ic-333789-ldn-b5.c.telia. net 90.0% 10 43.9 43.9 43.9 43.9 0.0
15.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0
16.|-- CON-HOT-100G-V236-HFA.hotnet.net.il 70.0% 10 97.3 97.4 97.3 97.6 0.0
17.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0
18.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0
19.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0
20.|-- dynamic-37-142-159-179.hotnet.net.il 0.0% 10 109.7 110.5 107.8 116.8 2.6

06/10/2019 22:34:34 UTC

MTR:
Start: Sun Oct 6 22:34:35 2019 Blizzard 1.|-- Blizzard 0.0% 10 0.2 0.3 0.2 0.4 0.0
2.|-- 37.244.25.2 0.0% 10 0.7 0.9 0.5 4.3 1.2
3.|-- Blizzard 0.0% 10 1.2 2.3 1.1 11.1 3.1
4.|-- 137.221.66.38 0.0% 10 1.1 1.1 0.9 1.2 0.0
5.|-- 137.221.77.72 0.0% 10 7.4 12.9 7.4 62.0 17.3
6.|-- 137.221.65.19 0.0% 10 7.3 7.7 7.3 10.0 0.7
7.|-- 137.221.79.34 0.0% 10 7.6 11.3 7.5 43.8 11.4
8.|-- e-lon-cor-r2fe911.uklon.ecs-ip. net 0.0% 10 34.6 33.4 31.9 34.6 0.7
9.|-- mad1-cr1-hu5-0-0.cprm. net 0.0% 10 31.8 31.9 31.7 32.3 0.0
10.|-- 213.248.76.185 0.0% 10 33.4 33.5 33.4 34.1 0.0
11.|-- prs-bb3-link.telia. net 0.0% 10 47.0 47.0 46.9 47.2 0.0
12.|-- ldn-bb3-link.telia .net 0.0% 10 48.4 49.1 48.3 53.2 1.3
13.|-- ldn-b1-link.telia. net 0.0% 10 48.8 48.5 48.5 48.8 0.0
14.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0
15.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0
16.|-- CON-HOT-100G-V236-HFA.hotnet.net.il 70.0% 10 100.6 100.6 100.6 100.7 0.0
17.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0
18.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0
19.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0
20.|-- dynamic-37-142-159-179.hotnet.net.il 0.0% 10 112.2 112.4 111.0 114.5 0.9

06/10/2019 22:34:35 UTC

ill add that its only overwatch that have this problem of high latency

Hello Lordbulbul :slight_smile:

The MTR tests are showing big packet losses in some of the international nodes used to route your connection, an issue that can definitely explain high latency.

That said, looking glass only shows part of the routing, so it would be nice to see results of a WinMTR test, as those will show us in detail the missing part and can be extremely useful to determine the origin of the problem ^^

there were 2 ip to choose for eu so i did for both , tell me if its ok or i need to do it again.

| WinMTR statistics |

| Host - % | Sent | Recv | Best | Avrg | Wrst | Last |

|------------------------------------------------|------|------|------|------|------|------|

| 192.168.1.1 - 0 | 464 | 464 | 3 | 3 | 12 | 3 |

| No response from host - 0 | 464 | 464 | 9 | 16 | 39 | 16 |

| 172.18.14.218 - 0 | 464 | 464 | 16 | 21 | 40 | 17 |

| 172.17.1.94 - 0 | 464 | 464 | 16 | 22 | 46 | 18 |

| 172.17.3.74 - 84 | 107 | 18 | 0 | 22 | 33 | 18 |

|BB-H2-B31.231-HFA-HOT-100G.hotnet.net.il - 99 | 93 | 1 | 0 | 21 | 21 | 21 |

| No response from host - 100 | 92 | 0 | 0 | 0 | 0 | 0 |

| No response from host - 100 | 92 | 0 | 0 | 0 | 0 | 0 |

| No response from host - 100 | 92 | 0 | 0 | 0 | 0 | 0 |

| No response from host - 100 | 92 | 0 | 0 | 0 | 0 | 0 |

| No response from host - 100 | 92 | 0 | 0 | 0 | 0 | 0 |

| No response from host - 100 | 92 | 0 | 0 | 0 | 0 | 0 |

| No response from host - 100 | 92 | 0 | 0 | 0 | 0 | 0 |

| No response from host - 100 | 92 | 0 | 0 | 0 | 0 | 0 |

| No response from host - 100 | 92 | 0 | 0 | 0 | 0 | 0 |

| No response from host - 100 | 92 | 0 | 0 | 0 | 0 | 0 |

| No response from host - 100 | 92 | 0 | 0 | 0 | 0 | 0 |

| No response from host - 100 | 92 | 0 | 0 | 0 | 0 | 0 |

| No response from host - 100 | 92 | 0 | 0 | 0 | 0 | 0 |

| No response from host - 100 | 92 | 0 | 0 | 0 | 0 | 0 |

| No response from host - 100 | 92 | 0 | 0 | 0 | 0 | 0 |

| No response from host - 100 | 92 | 0 | 0 | 0 | 0 | 0 |

| No response from host - 100 | 92 | 0 | 0 | 0 | 0 | 0 |

| No response from host - 100 | 92 | 0 | 0 | 0 | 0 | 0 |

| No response from host - 100 | 92 | 0 | 0 | 0 | 0 | 0 |

| No response from host - 100 | 92 | 0 | 0 | 0 | 0 | 0 |

| No response from host - 100 | 92 | 0 | 0 | 0 | 0 | 0 |

| No response from host - 100 | 92 | 0 | 0 | 0 | 0 | 0 |

| No response from host - 100 | 92 | 0 | 0 | 0 | 0 | 0 |

| No response from host - 100 | 92 | 0 | 0 | 0 | 0 | 0 |

|________________________________________________|______|______|______|______|______|______|

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

WinMTR statistics                                   |

| Host - % | Sent | Recv | Best | Avrg | Wrst | Last |

|------------------------------------------------|------|------|------|------|------|------|

| 192.168.1.1 - 0 | 305 | 305 | 3 | 4 | 11 | 4 |

| No response from host - 0 | 305 | 305 | 10 | 14 | 29 | 26 |

| 172.18.14.210 - 0 | 305 | 305 | 15 | 20 | 32 | 19 |

| 172.17.1.90 - 0 | 305 | 305 | 14 | 19 | 33 | 26 |

| 172.17.3.70 - 86 | 69 | 10 | 0 | 20 | 25 | 21 |

|BB-H2-B32.236-HFA-HOT-100G.hotnet.net.il - 93 | 65 | 5 | 0 | 19 | 23 | 17 |

| No response from host - 100 | 61 | 0 | 0 | 0 | 0 | 0 |

| No response from host - 100 | 61 | 0 | 0 | 0 | 0 | 0 |

| No response from host - 100 | 61 | 0 | 0 | 0 | 0 | 0 |

| No response from host - 100 | 61 | 0 | 0 | 0 | 0 | 0 |

| No response from host - 100 | 61 | 0 | 0 | 0 | 0 | 0 |

| No response from host - 100 | 61 | 0 | 0 | 0 | 0 | 0 |

| No response from host - 100 | 61 | 0 | 0 | 0 | 0 | 0 |

| No response from host - 100 | 61 | 0 | 0 | 0 | 0 | 0 |

| No response from host - 100 | 61 | 0 | 0 | 0 | 0 | 0 |

| No response from host - 100 | 61 | 0 | 0 | 0 | 0 | 0 |

| No response from host - 100 | 61 | 0 | 0 | 0 | 0 | 0 |

| No response from host - 100 | 61 | 0 | 0 | 0 | 0 | 0 |

| No response from host - 100 | 61 | 0 | 0 | 0 | 0 | 0 |

| No response from host - 100 | 61 | 0 | 0 | 0 | 0 | 0 |

| No response from host - 100 | 61 | 0 | 0 | 0 | 0 | 0 |

| No response from host - 100 | 61 | 0 | 0 | 0 | 0 | 0 |

| No response from host - 100 | 61 | 0 | 0 | 0 | 0 | 0 |

| No response from host - 100 | 61 | 0 | 0 | 0 | 0 | 0 |

| No response from host - 100 | 61 | 0 | 0 | 0 | 0 | 0 |

| No response from host - 100 | 61 | 0 | 0 | 0 | 0 | 0 |

| No response from host - 100 | 61 | 0 | 0 | 0 | 0 | 0 |

| No response from host - 100 | 61 | 0 | 0 | 0 | 0 | 0 |

| No response from host - 100 | 61 | 0 | 0 | 0 | 0 | 0 |

| No response from host - 100 | 61 | 0 | 0 | 0 | 0 | 0 |

|________________________________________________|______|______|______|______|______|______|

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

It has to do something with HOT’s internet service because I’m facing the same issue as you.

Hey there Lordbulbul, thanks a lot for the tests!

The results of the WinMTR tests are showing some packet loss as well, located in the same area shown in the looking glass. To be more specific:

Considering the results above - we are talking of an 80%+ packet loss - high latency is unfortunately to be expected :frowning:

The nodes above seems to be within the network infrastructure of your ISP, so you may want to contact them to report the situation above.

its Feb 16th 2020
gettin some major connection problems for the past 3 days i think.
the connection problem icon apear on screen and game laging.

unplayable
TRACEROUTE:
traceroute to 109.64.239.118 (109.64.239.118), 15 hops max, 60 byte packets
1 Blizzard Blizzard 0.347 ms 0.332 ms 0.335 ms
2 37.244.24.3 (37.244.24.3) 0.587 ms 0.678 ms 0.782 ms
3 Blizzard Blizzard 1.099 ms 1.181 ms 1.199 ms
4 137.221.66.40 (137.221.66.40) 1.876 ms 1.915 ms 1.917 ms
5 137.221.78.66 (137.221.78.66) 6.533 ms 6.535 ms 6.532 ms
6 137.221.65.28 (137.221.65.28) 6.493 ms 8.604 ms 8.582 ms
7 137.221.80.32 (137.221.80.32) 6.583 ms 6.660 ms 6.633 ms
8 decix3.bezeqintnet (80.81.193.191) 7.613 ms 7.773 ms 7.740 ms
9 bzq-219-189-77.cablep.bezeqintnet (62.219.189.77) 65.127 ms 64.216 ms 64.205 ms
10 bzq-219-189-2.cablep.bezeqintnet (62.219.189.2) 71.918 ms 71.928 ms 71.896 ms
11 bzq-25-77-13.cust.bezeqintnet (212.25.77.13) 71.049 ms 71.176 ms 71.058 ms
12 * * *
13 * * *
14 * * *
15 * * *

16/02/2020 19:29:21 UTC

TRACEROUTE:
traceroute to 109.64.239.118 (109.64.239.118), 15 hops max, 60 byte packets
1 Blizzard Blizzard 0.339 ms 0.331 ms 0.330 ms
2 37.244.25.130 (37.244.25.130) 0.603 ms 0.663 ms 0.718 ms
3 Blizzard Blizzard 1.297 ms 1.316 ms 2.750 ms
4 137.221.66.38 (137.221.66.38) 1.092 ms 1.118 ms 1.155 ms
5 137.221.77.68 (137.221.77.68) 9.415 ms 9.434 ms 9.436 ms
6 137.221.65.27 (137.221.65.27) 9.259 ms 9.527 ms 9.491 ms
7 137.221.80.34 (137.221.80.34) 9.414 ms 9.519 ms 9.462 ms
8 decix3.bezeqintnet (80.81.193.191) 13.786 ms 13.803 ms 13.802 ms
9 bzq-179-161-217.pop.bezeqintnet (212.179.161.217) 62.737 ms 62.044 ms 62.009 ms
10 bzq-179-124-254.cust.bezeqintnet (212.179.124.254) 61.372 ms 60.721 ms 60.056 ms
11 bzq-25-77-13.cust.bezeqintnet (212.25.77.13) 60.992 ms 60.471 ms 67.583 ms
12 * * *
13 * * *
14 * * *
15 * * *

16/02/2020 19:29:21 UTC

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

— 109.64.239.118 ping statistics —
4 packets transmitted, 0 received, 100% packet loss, time 2999ms

16/02/2020 19:29:21 UTC

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

— 109.64.239.118 ping statistics —
4 packets transmitted, 0 received, 100% packet loss, time 2999ms

16/02/2020 19:29:21 UTC

MTR:
Start: Sun Feb 16 19:29:21 2020 Blizzard 1.|-- Blizzard 0.0% 10 0.4 0.3 0.3 0.4 0.0
2.|-- 37.244.24.3 0.0% 10 0.6 0.6 0.5 0.7 0.0
3.|-- Blizzard 0.0% 10 1.2 1.4 1.1 2.5 0.3
4.|-- 137.221.66.40 0.0% 10 1.9 4.7 1.1 26.8 8.0
5.|-- 137.221.78.66 0.0% 10 6.4 6.4 6.3 6.6 0.0
6.|-- 137.221.65.28 0.0% 10 6.7 6.4 6.3 6.7 0.0
7.|-- 137.221.80.32 0.0% 10 6.4 8.0 6.4 20.0 4.2
8.|-- decix3.bezeqintnet 0.0% 10 7.6 7.6 7.3 7.8 0.0
9.|-- bzq-219-189-77.dsl.bezeqintnet 0.0% 10 60.5 60.6 60.4 61.6 0.0
10.|-- bzq-219-189-2.dsl.bezeqintnet 0.0% 10 71.9 78.4 71.9 93.2 9.3
11.|-- bzq-25-77-13.cust.bezeqintnet 0.0% 10 71.2 71.8 70.9 76.7 1.6
12.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0

16/02/2020 19:29:21 UTC

MTR:
Start: Sun Feb 16 19:29:21 2020 Blizzard 1.|-- Blizzard 0.0% 10 0.3 0.3 0.3 0.5 0.0
2.|-- 37.244.25.130 20.0% 10 0.5 208.0 0.5 658.1 270.3
3.|-- Blizzard 0.0% 10 1.3 1.3 1.1 1.4 0.0
4.|-- 137.221.66.38 0.0% 10 1.1 1.1 1.1 1.3 0.0
5.|-- 137.221.77.68 0.0% 10 9.5 9.4 9.2 9.6 0.0
6.|-- 137.221.65.27 0.0% 10 9.4 9.9 9.3 13.5 1.2
7.|-- 137.221.80.34 0.0% 10 9.5 12.1 9.5 34.3 7.7
8.|-- decix3.bezeqintnet 0.0% 10 13.8 13.6 13.4 13.9 0.0
9.|-- bzq-161-217.pop.bezeqintnet 0.0% 10 61.5 61.7 61.5 61.8 0.0
10.|-- bzq-179-124-254.cust.bezeqintnet 0.0% 10 60.0 60.1 59.9 61.1 0.3
11.|-- bzq-25-77-13.cust.bezeqintnet 0.0% 10 60.6 61.2 60.5 63.0 0.7
12.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0

16/02/2020 19:29:21 UTC

90 ping is low here in israel.

Hi there,

Going to close this thread since the original reports are several months old.

@DontBeMad: If you’re still having issues with this, please make sure you start with the steps over in this article: Overwatch - Latency Problems.

If the problem persists, please start a new thread with the relevant details and diagnostics, such as:

  • Country and City
  • Internet Service Provider
  • Date/time of your connection issues
  • a WinMTR
  • a Pathping
  • Results from all 3 tests over at Looking-Glass

Please note that all diagnostics need to be run while the problem is present in-game, in case it’s only happening during certain times or comes and goes.

You can share links in your post as Preformatted text by highlighting your link and clicking the </> icon or writing the link between ``. To share files with us, you can use a page like Pastebin.com or share directly with us through OneDrive.

Thanks!