I'm having similar issues since 9.4; experiencing heavy packet loss. I looked up the server address on Reddit and ran a couple traceroutes to check, and it looks like tracert consistently times out twice on the final hop to the WoWS server, assuming I have the address correct.   Tracert results posted below. C:\Windows\System32>tracert login1.worldofwarships.com Tracing route to login1.worldofwarships.com [162.213.60.65]
over a maximum of 30 hops:   1     1 ms     1 ms     1 ms  192.168.0.1
  2     9 ms     9 ms    10 ms  CPE00fc8d34e3e3-CM00fc8d34e3e0.cpe.net.cable.rogers.com [174.112.172.1]
  3    11 ms     9 ms    10 ms  67.231.221.73
  4    14 ms    12 ms    10 ms  209.148.236.177
  5    18 ms    23 ms   199 ms  209.148.231.77
  6    18 ms    15 ms    14 ms  9301-cgw01.ym.rmgt.net.rogers.com [209.148.229.229]
  7    27 ms    27 ms    31 ms  209.148.237.17
  8    27 ms    29 ms    29 ms  be-203-pe01.350ecermak.il.ibone.comcast.net [75.149.228.121]
  9    26 ms    26 ms    27 ms  be-10563-cr02.350ecermak.il.ibone.comcast.net [68.86.82.157]
 10    49 ms    49 ms    50 ms  be-10521-cr02.1601milehigh.co.ibone.comcast.net [68.86.85.170]
 11    52 ms    52 ms    56 ms  be-12021-cr01.champa.co.ibone.comcast.net [68.86.84.225]
 12    78 ms    74 ms    74 ms  be-11020-cr02.sunnyvale.ca.ibone.comcast.net [68.86.84.9]
 13    81 ms    77 ms    75 ms  be-11025-cr01.9greatoaks.ca.ibone.comcast.net [68.86.87.158]
 14    82 ms    76 ms    71 ms  be-12578-pe04.9greatoaks.ca.ibone.comcast.net [68.86.88.18]
 15     *        *        *     Request timed out.
 16     *        *        *     Request timed out.
 17    89 ms    83 ms    82 ms  sv4-sl-a65.fe.core.pw [162.213.60.65] Trace complete.