i feel like they just ignore this post
1 Like
Hello Vortex,
Did you run the WinMTR while having high latency? Could you please run another one, and create a traceroute and pathping as well?
- Traceroute (right after a disconnection or whenever you’re experiencing the issue)
- Pathping (right after a disconnection or whenever you’re experiencing the issue)
- WinMTR (right after a disconnection or whenever you’re experiencing the issue)
To other players posting on the thread:
If you’re experiencing connection issues, please check this article and make sure you follow all the instructions, including the advanced steps:
battle.net/support/article/99037
If the issue persists, we need the following information so we can investigate:
- Details of issue:
- Date/time it started:
- City/Country:
- Internet Provider:
- Traceroute (right after a disconnection or whenever you’re experiencing the issue)
- Pathping (right after a disconnection or whenever you’re experiencing the issue)
- WinMTR (right after a disconnection or whenever you’re experiencing the issue)
Got feedback about the support I’m providing? Leave your comments here!
firstly thanks for taking your time and answering
yes and i still have problem with high latency , i’m not sure if it have anything to do with but the problem occurred after hammond update
1 <1 ms <1 ms <1 ms 193.150.117.100
2 8 ms 10 ms 9 ms 10.177.48.1
3 15 ms 16 ms 20 ms 172.18.2.238
4 21 ms 15 ms 16 ms 172.17.10.74
5 * * * Request timed out.
6 * * * Request timed out.
7 84 ms 85 ms 86 ms adm-b3-link.telia.net [213.248.69.129]
8 91 ms 87 ms 85 ms adm-bb3-link.telia.net [62.115.122.178]
9 109 ms 83 ms 84 ms adm-b2-link.telia.net [213.155.137.211]
10 83 ms 83 ms 86 ms 62.115.46.198
11 84 ms 86 ms 85 ms ae1-br02-eqam1.blizzardonline.net [137.221.78.35]
12 90 ms 91 ms 96 ms et-0-0-3-br02-eqpa4.blizzardonline.net [137.221.65.92]
13 160 ms 159 ms 159 ms be2-pe02-eqpa4.blizzardonline.net [137.221.77.73]
14 165 ms 163 ms 163 ms 185.60.114.159
1 193.150.117.100
2 10.177.48.1
3 172.18.2.238
4 172.17.10.74
5 * 172.17.10.185
6 * * *
Computing statistics for 125 seconds...
Source to Here This Node/Link
Hop RTT Lost/Sent = Pct Lost/Sent = Pct Address
0
0/ 100 = 0% |
1 1ms 0/ 100 = 0% 0/ 100 = 0% 193.150.117.100
100/ 100 =100% |
2 --- 100/ 100 =100% 0/ 100 = 0% 10.177.48.1
0/ 100 = 0% |
3 --- 100/ 100 =100% 0/ 100 = 0% 172.18.2.238
0/ 100 = 0% |
4 --- 100/ 100 =100% 0/ 100 = 0% 172.17.10.74
0/ 100 = 0% |
5 --- 100/ 100 =100% 0/ 100 = 0% 172.17.10.18
|------------------------------------------------------------------------------------------|
| WinMTR statistics |
| Host - % | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
| 193.150.117.100 - 0 | 5 | 5 | 0 | 0 | 0 | 0 |
| 10.177.48.1 - 0 | 5 | 5 | 7 | 8 | 10 | 8 |
| 172.18.2.238 - 0 | 5 | 5 | 15 | 18 | 23 | 21 |
| 172.17.10.74 - 0 | 5 | 5 | 15 | 18 | 25 | 15 |
| No response from host - 100 | 1 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 1 | 0 | 0 | 0 | 0 | 0 |
| adm-b3-link.telia.net - 0 | 5 | 5 | 87 | 89 | 94 | 90 |
| adm-bb3-link.telia.net - 0 | 5 | 5 | 89 | 90 | 94 | 89 |
| adm-b2-link.telia.net - 0 | 5 | 5 | 86 | 87 | 89 | 86 |
| 62.115.46.198 - 0 | 5 | 5 | 85 | 86 | 88 | 85 |
| ae1-br02-eqam1.blizzardonline.net - 0 | 5 | 5 | 87 | 88 | 92 | 87 |
| et-0-0-3-br02-eqpa4.blizzardonline.net - 0 | 5 | 5 | 93 | 95 | 97 | 97 |
| be2-pe02-eqpa4.blizzardonline.net - 0 | 5 | 5 | 160 | 161 | 164 | 160 |
| 185.60.114.159 - 0 | 5 | 5 | 165 | 168 | 172 | 168 |
|________________________________________________|______|______|______|______|______|______|
Hello Volrex,
I don’t really see anything especial on the diagnostics. The ping seems to keep going higher along the path, but that’s normal. It escalates quite a lot here:
It goes from 21ms in jump 4, to 86 in jump 7. Unfortunately, nodes 5 and 6 seem to be protected, so we have no way of knowing what happens there. In jump 9 there seems to be a huge variation between connection tries on the same node; from 83ms to 109ms.
I would personally recommend contacting your internet provider so they can check the traceroute and make sure everything is working as it should. I can’t see any outstanding issues, but they might be able to check if anything is wrong in those nodes that are protected and show no data.
Got feedback about the support I’m providing? Leave your comments here!
but why i’m having problem only with blizzard servers
i have no problem with counter strike global offensive servers and rust officialese servers
and why it’s suddenly jumps to 160
13 160 ms 159 ms 159 ms be2-pe02-eqpa4.blizzardonline. net [137.221.77.73]
Basically, your connection doesn’t take the same path when it goes towards Overwatch servers than it takes when it goes towards other game or service’s servers. You can find a more detailed explanation about this here:
Got feedback about the support I’m providing? Leave your comments here!
i tried reinstalling overwatch and turning off firewall and anti virus ,and nothing helped
the problem literally happened overnight , played OW , was having around 90 ms ,the next day suddenly it’s 170ms
Is there any way to fix that ?
Having the same problem, going to post my trace route so Blizz people have more to work with.
"
| WinMTR statistics |
| Host - % | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
| 192.168.1.1 - 0 | 151 | 151 | 0 | 0 | 7 | 0 |
| 10.234.40.1 - 0 | 151 | 151 | 6 | 10 | 18 | 10 |
| 172.18.10.106 - 0 | 151 | 151 | 13 | 16 | 32 | 18 |
| 172.17.1.9 - 0 | 151 | 151 | 12 | 16 | 24 | 15 |
| 172.17.10.185 - 91 | 33 | 3 | 0 | 14 | 16 | 14 |
| No response from host - 100 | 31 | 0 | 0 | 0 | 0 | 0 |
| adm-b3-link.telia. net - 0 | 151 | 151 | 83 | 86 | 116 | 87 |
| adm-bb3-link.telia. net - 0 | 151 | 151 | 84 | 87 | 94 | 85 |
| adm-b2-link.telia. net - 0 | 151 | 151 | 80 | 83 | 96 | 84 |
| 62.115.46.198 - 0 | 151 | 151 | 83 | 88 | 113 | 86 |
| ae1-br01-eqam1.blizzardonline. net - 0 | 151 | 151 | 74 | 79 | 138 | 76 |
| et-0-0-31-pe02-eqam1.blizzardonline. net - 0 | 151 | 151 | 155 | 158 | 168 | 161 |
| 185.60.112.157 - 0 | 151 | 151 | 156 | 160 | 175 | 161 |
|________________________________________________|______|______|______|______|______|______|
WinMTR v0.92 GPL V2 by Appnor MSP - Fully Managed Hosting & Cloud Provider"
hope they find A fix quickly cause right now I can’t play.
Seems like between eqam . blizzardonline. net under blizzard domain I am losing most of my latency.
1 Like
Im getting 75% penalty and lost 100 SR because of this HIGH PING…WTF blizzard…why am I getting punished for your Incompetency…PLEASE FIX THIS OR you are gonna lose more players…you already lost 30% of your players since the OWL…
1 Like
what do you mean 75% penalty ?
and can you please post here WinMTR and/or traceroute so blizzard can see what the problem is
5 72 ms 73 ms 73 ms adm-b3-link.telia.net [213.248.69.129]
6 80 ms 74 ms 75 ms adm-bb4-link.telia.net [62.115.122.190]
7 89 ms 85 ms 84 ms adm-b2-link.telia.net [62.115.118.147]
8 82 ms 83 ms 83 ms 62.115.46.198
9 71 ms 71 ms 73 ms ae1-br02-eqam1.blizzardonline.net [137.221.78.35]
10 76 ms 77 ms 78 ms et-0-0-3-br02-eqpa4.blizzardonline.net [137.221.65.92]
11 155 ms 154 ms 154 ms be2-pe02-eqpa4.blizzardonline.net [137.221.77.73]i have my ping problem with the same servers
I have the same exact problem for a few weeks now.
My MTR:
|------------------------------------------------------------------------------------------|
| WinMTR statistics |
| Host - % | Sent | Recv | Best | Avrg | Wrst | Last |
|---|---|---|---|---|---|---|
| OpenWrt.lan - 0 | 412 | 412 | 0 | 0 | 2 | 0 |
| 10.240.40.1 - 0 | 412 | 412 | 6 | 9 | 16 | 9 |
| 172.18.11.2 - 83 | 97 | 17 | 0 | 9 | 21 | 12 |
| BB-H2-B31.231-HFA-HOT-100G.hotnet.net.il - 88 | 93 | 12 | 0 | 8 | 11 | 10 |
| adm-b3-link.telia .net - 0 | 412 | 412 | 69 | 72 | 91 | 69 |
| adm-bb4-link.telia .net - 0 | 412 | 412 | 71 | 74 | 80 | 75 |
| adm-b1-link.telia .net - 0 | 412 | 412 | 70 | 73 | 83 | 74 |
| adm-bb3-link.telia .net - 0 | 412 | 412 | 70 | 74 | 81 | 73 |
| adm-b2-link.telia .net - 0 | 412 | 412 | 70 | 73 | 82 | 71 |
| 62.115.46.198 - 0 | 412 | 412 | 71 | 75 | 98 | 75 |
| ae1-br01-eqam1.blizzardonline .net - 0 | 412 | 412 | 69 | 75 | 238 | 71 |
| et-0-0-31-pe02-eqam1.blizzardonline .net - 0 | 412 | 412 | 147 | 150 | 164 | 150 |
| 185.60.112.157 - 0 | 412 | 412 | 150 | 153 | 167 | 151 |
| ________________________________________________ | ______ | ______ | ______ | ______ | ______ | ______ |
WinMTR v0.92 GPL V2 by Appnor MSP - Fully Managed Hosting & Cloud Provider
MTR of my friend that is on another ISP and does not have the issue:
|------------------------------------------------------------------------------------------|
| WinMTR statistics |
| Host - % | Sent | Recv | Best | Avrg | Wrst | Last |
|---|---|---|---|---|---|---|
| 192.168.1.1 - 0 | 79 | 79 | 1 | 4 | 42 | 5 |
| 10.240.144.1 - 0 | 79 | 79 | 9 | 16 | 56 | 17 |
| 172.18.11.2 - 94 | 16 | 1 | 0 | 16 | 16 | 16 |
| 172.17.10.186 - 0 | 79 | 79 | 12 | 21 | 60 | 17 |
| 172.17.0.5 - 29 | 35 | 25 | 11 | 16 | 29 | 21 |
| bzq-114-65-29.cust.bezeqint .net - 2 | 75 | 74 | 12 | 20 | 60 | 16 |
| bzq-219-189-197.dsl.bezeqint .net - 0 | 79 | 79 | 12 | 19 | 60 | 14 |
| bzq-25-82-82.cust.bezeqint .net - 0 | 79 | 79 | 12 | 21 | 58 | 13 |
| bzq-25-77-2.cust.bezeqint .net - 2 | 75 | 74 | 12 | 21 | 60 | 18 |
| bzq-219-189-34.dsl.bezeqint .net - 0 | 79 | 79 | 12 | 21 | 60 | 19 |
| 80.249.208.83 - 0 | 79 | 79 | 73 | 83 | 126 | 74 |
| ae1-br02-eqam1.blizzardonline .net - 0 | 79 | 79 | 73 | 84 | 143 | 92 |
| et-0-0-67-pe02-eqam1.blizzardonline .net - 2 | 75 | 74 | 72 | 80 | 126 | 82 |
| 185.60.112.157 - 2 | 75 | 74 | 73 | 81 | 126 | 81 |
| ________________ | __ | __ | __ | __ | __ | __ |
WinMTR v0.92 GPL V2 by Appnor MSP - Fully Managed Hosting & Cloud Provider
I talked with Blizzard’s tech support and they said the problem might be the hop to adm-b3-link.telia.net.
I asked about the big ping gap at the hop ae1-br01-eqam1.blizzardonline.net -> et-0-0-31-pe02-eqam1.blizzardonline.net, I got some different responses from the 2 different support people I talked with. First one said it may be related to blizard’s DDoS protection. The second one said it can be an issue caused by earlier problem in my route, or a suboptimal route (possible, but I don’t see from the above data how that would make sense, as the first blizzard server hit is always 70ish ping).
I rephrased the above responses so don’t take them as anything official.
It still looks to me like the problem is somewhere on blizzard’s end. My ISP was not helpful to say the least when discussing this problem.
If anyone reading this thread also has the same problem please post here as well to help with visibility. Thanks.
Can someone from Blizzard please contact “Hotnet” and try to solve the problem with them? there are many Hotnet customers that complain about the same issue. this is not something we as users can solve by ourselves. I don’t think switching ISP just because one game’s ping is too high is a reasonable solution.
2 Likes
bump
i still got the problem
Ok, i’ve given up. changed my ISP and now the ping is 100ms which is much better. still not the 80ms I used to have, but oh well.
I opened a ticket on Blizzard’s support, they asked for diagnostics from the Blizzard looking-glass tool.
I hope with more data they could pinpoint the issue, so please post in the following thread:
(unfortunately the looking-glass thing only gives me an error right now, but maybe it’s just me…)
cant we open the same thing here
i’m banned from US forums
what ISP ,bezek ?
Partner on cable. although i had some issues today where ping spiked to 140 at some parts. but on average it’s around 105.
I have a similar issue, about 3 updates ago my ping started staying at about 97ms, it used to be a solid 60-70ms before the updates but I didn’t think much of it since 97ms is still quite playable even though I prefer it to be lower.
But then I started getting spikes to around 160ms and the game is now only on 120ms, it’s almost as if in every new update that comes out my ping gets worse, a couple of days ago I was even booted off a comp game with no explanation as to why, my internet was completely fine outside of Overwatch.
I play on the EU servers and every other game I play with EU servers does not have this issue.
I have also spoken to my ISP and they say that since my ping is fine with every other server we tested it can’t be an ISP issue.
So naturally I checked everything is fine on my end (updated drivers etc) and everything seemed to be fine.
Now playing with 150ms on an EU server which is not that far away from me is awful, sometimes I get hits which don’t appear to register, and sometimes they do register but I don’t get the X telling me that I actually got the hit and elimination, I just see it in the kill feed!
Pharah is almost unplayable as the rockets sometimes don’t even register they just get swallowed into the walls and ground.
My specs are:
OS - Windows 10 Pro
CPU - Intel core I7 2600k
GPU - MSI GTX750ti
RAM - G.Skill 12GB 1600Mhz Ram
Here are my WINMTR results:
WinMTR statistics |
| Host - % | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
| BEZEQ - 1 | 590 | 588 | 0 | 0 | 18 | 0 |
| bb-205-152-117.018.net.il - 1 | 591 | 589 | 10 | 14 | 57 | 11 |
| bb-205-153-61.018.net.il - 1 | 594 | 593 | 10 | 13 | 50 | 11 |
| bb-191-17.018.net.il - 2 | 575 | 569 | 61 | 67 | 112 | 72 |
|`te0-0-0-24.rcr22.fra06.atlas.cogentco.com` - 2 | 571 | 564 | 62 | 66 | 95 | 63 |
|gi0-0-1-5.nr11.b015760-1.fra06.atlas.cogentco.com - 1 | 579 | 574 | 62 | 65 | 109 | 64 |
| ae1-br01-eqfr5.blizzardonline.net - 2 | 575 | 569 | 62 | 66 | 155 | 63 |
| et-0-0-2-br01-eqpa4.blizzardonline.net - 2 | 559 | 549 | 72 | 81 | 197 | 75 |
| No response from host - 100 | 120 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 120 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 120 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 120 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 120 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 120 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 120 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 120 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 120 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 120 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 120 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 120 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 120 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 120 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 120 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 120 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 120 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 120 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 120 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 120 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 120 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 120 | 0 | 0 | 0 | 0 | 0 |
|________________________________________________|______|______|______|______|______|______|
WinMTR v0.92 GPL V2 by Appnor MSP - Fully Managed Hosting & Cloud Provider