High ping lately


#1

for some reason i get really high ping lately

i uselly get 80-100ms ,most of the time 86-90 , it’s rarely ever goes above 100 and the highest i ever got was 120ms

now it’s sitting on 160-200ms , most of the time around 186-190

i checked some other game (counter strike global offensive) and my ping was : around 90-100ms

i dont download anything

i have no VPN or something like that

i did restart router

i did flush dns

nothing helped

an imagine of ctr+shift+N
ht tps://imgur.com/a/Ni6ZqDD

|------------------------------------------------------------------------------------------|
| WinMTR statistics |

Host - % Sent Recv Best Avrg Wrst Last
193.150.117.100 - 0 4 4 0 0 1 0
10.177.48.1 - 0 4 4 8 12 15 13
172.18.2.238 - 0 4 4 15 20 26 18
172.17.10.74 - 0 4 4 18 21 26 18
No response from host - 0 0 0 0 0 0 0
No response from host - 0 0 0 0 0 0 0
adm-b3-link.telia. net - 0 4 4 83 88 94 83
adm-bb3-link.telia. net - 0 4 4 89 91 96 89
adm-b2-link.telia. net - 0 4 4 86 89 93 86
62.115.46.198 - 0 4 4 83 89 98 87
ae1-br02-eqam1.blizzardonline. net - 0 4 4 83 88 95 83
et-0-0-3-br02-eqpa4.blizzardonline. net - 0 4 4 95 97 101 95
be2-pe02-eqpa4.blizzardonline. net - 0 4 4 158 163 170 158
185.60.114.159 - 0 4 4 164 170 175 167
________________________________________________ ______ ______ ______ ______ ______ ______

#2

I have the same thing!
I usually have around 60-70 ms and since yesterday im having 160 ms!
I checked “speed test” and its looks like my internet work normally
And in other games my ping is perefecly fine. its happend only in overwatch


#3

Yeah i’ve been getting 160ms ping since the last patch (it used to be 70-80ms). I did the tracert thing and I think I found the problem h ttps://imgur.com/NDnVfPQ


#4

same thing here
most time my ping is 70-80
but now its constant 160, i cant play like this never hit anything


#5

As far as I know, Blizz has a lot of problems now,
this is the new hero and development of the Queen JunkerTown about which they make so many hints, there is a huge chance that it will be the next tank, but only when the tank goes unknown. The blizz are now working, and their servers have received a gruesome overload recently.
They are all busy (server)
The problem is not in you.
Nevertheless, I play calmly, without any problems with ping.

Your connected server or the server of your country is simply overloaded.

As far as I’ve heard Blizzards connect another additional pack of servers


#6

up

the problem is still here and still no respond :frowning:


#7

Well, it is a weekend. i guess we’re stuck with this problem at least until monday.


#8

i feel like they just ignore this post


#9

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!


High MS just in Overwatch
#10

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 |
|________________________________________________|______|______|______|______|______|______|

#11

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!


#12

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]


#13

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!


#14

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 ?


#15

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.


#16

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…


#17

what do you mean 75% penalty ?

and can you please post here WinMTR and/or traceroute so blizzard can see what the problem is


#18
 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]

#19

i have my ping problem with the same servers


#20

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.