Constant high ping only in OW after Season 10 update

Technical Support
1

Ever since the season 10 update my ping has doubled for no reason. I used to have around 50ms give or take and now I get a minimum of 80ms and it usually stays around 100ms. I have tried a VPN and the other stuff that Blizzard recommends like changing to the Google DNS but neither helped. I also tried switching back to Battle.net but it didnt change. I have the Trace route and Pathping though.

Edit: Might have been fixed by flushing my DNS, havent fully tested it


Tracing route to 24.105.62.129 over a maximum of 30 hops

  0  Max-Desktop.orld.fl.wtsky.net [10.127.16.78] 
  1  10.127.16.1 
  2  208.64.158.254 
  3  52.124.44.177 
  4  206.41.108.97 
  5  ae1-br01-eqmi2.as57976.net [137.221.76.33] 
  6  xe-0-0-0-1-br01-eqat2.as57976.net [137.221.65.50] 
  7     *        *        *     
Computing statistics for 150 seconds...
            Source to Here   This Node/Link
Hop  RTT    Lost/Sent = Pct  Lost/Sent = Pct  Address
  0                                           Max-Desktop.orld.fl.wtsky.net [10.127.16.78] 
                                0/ 100 =  0%   |
  1    0ms     0/ 100 =  0%     0/ 100 =  0%  10.127.16.1 
                                0/ 100 =  0%   |
  2    5ms     0/ 100 =  0%     0/ 100 =  0%  208.64.158.254 
                                0/ 100 =  0%   |
  3    5ms     0/ 100 =  0%     0/ 100 =  0%  52.124.44.177 
                                0/ 100 =  0%   |
  4    8ms     0/ 100 =  0%     0/ 100 =  0%  206.41.108.97 
                                8/ 100 =  8%   |
  5   83ms    12/ 100 = 12%     4/ 100 =  4%  ae1-br01-eqmi2.as57976.net [137.221.76.33] 
                                0/ 100 =  0%   |
  6   87ms     8/ 100 =  8%     0/ 100 =  0%  xe-0-0-0-1-br01-eqat2.as57976.net [137.221.65.50] 

Trace complete.



Tracing route to 24.105.62.129 over a maximum of 30 hops

  1     6 ms     6 ms     6 ms  10.22.128.1 
  2     7 ms     6 ms     7 ms  te0-0-2-0.nr11.b015472-1.mia01.atlas.cogentco.com [38.32.118.137] 
  3     7 ms     7 ms     8 ms  te0-0-0-17.agr62.mia01.atlas.cogentco.com [154.24.68.205] 
  4    14 ms     7 ms     7 ms  te0-5-1-11.ccr21.mia01.atlas.cogentco.com [66.28.4.217] 
  5     7 ms     7 ms     7 ms  be3081.ccr41.mia03.atlas.cogentco.com [154.54.88.226] 
  6     *        *        *     Request timed out.
  7    21 ms    24 ms    21 ms  atl-b24-link.ip.twelve99.net [62.115.113.48] 
  8    22 ms    22 ms    22 ms  atl-bb1-link.ip.twelve99.net [62.115.134.246] 
  9     *        *        *     Request timed out.
 10    37 ms    37 ms    38 ms  chi-bb1-link.ip.twelve99.net [62.115.113.75] 
 11    37 ms    37 ms    37 ms  chi-b23-link.ip.twelve99.net [62.115.126.45] 
 12    38 ms    37 ms    37 ms  blizzard-ic-348622.ip.twelve99-cust.net [62.115.178.249] 
 13     *        *        *     Request timed out.
 14    39 ms    39 ms    40 ms  137.221.69.83 
 15    39 ms    40 ms    39 ms  137.221.67.65 
 16    38 ms    38 ms    38 ms  24.105.62.129 

Trace complete.
2

Wow we have the same isp and the same issue. Call whitesky and tell them you cant connect to 24.105.62.129.

3

idk if you fixed your issue or not but i think i fixed it by flushing my DNS

4

Its temporarily fixed by that but the issue starts up again around 3 or 4. I sent them information about where the problem is and they told me it will be fixed within 2 weeks.