Cannot connect to game server after login

This is the only game I have an issue with. This has been going on almost a year although sometimes I’m able to get in. After logging in and establishing server connection, it goes from entering game to “lost connection to game server” everytime. I ran Blizzard’s looking glass tool for overwatch in my region and got this result. Hope it means something to someone:

TRACEROUTE:
traceroute to 40.136.63.18 (40.136.63.18), 15 hops max, 60 byte packets
 1  Blizzard Blizzard  1.107 ms  1.096 ms  1.094 ms
 2  24.105.18.2 (24.105.18.2)  1.853 ms  1.852 ms  1.851 ms
 3  137.221.105.10 (137.221.105.10)  1.857 ms  1.858 ms  1.876 ms
 4  137.221.66.16 (137.221.66.16)  1.791 ms  1.803 ms  1.806 ms
 5  137.221.83.80 (137.221.83.80)  331.581 ms  331.614 ms  552.464 ms
 6  * * *
 7  137.221.65.1 (137.221.65.1)  13.284 ms  13.290 ms  13.390 ms
 8  137.221.65.7 (137.221.65.7)  12.756 ms  13.327 ms  13.305 ms
 9  137.221.70.34 (137.221.70.34)  13.462 ms  13.131 ms  13.249 ms
10  eqix-sv1.windstream. com (206.223.116.213)  12.420 ms  12.420 ms  12.474 ms
11  ae6-0.cr02.lsaj01-ca.us.windstream. net (40.138.83.186)  23.170 ms  23.364 ms  23.132 ms
12  ae5-0.cr01.lsaj01-ca.us.windstream. net (40.138.83.188)  23.223 ms  23.200 ms  23.230 ms
13  ae18-0.cr01.dlls02-tx.us.windstream. net (169.130.114.157)  40.538 ms  40.449 ms  40.452 ms
14  ae0.agr02.stls01-mo.us.windstream. net (40.136.112.69)  57.099 ms  57.098 ms  57.138 ms
15  te12-3.pe01.stls01-mo.us.windstream. net (40.136.115.237)  58.557 ms  58.557 ms  58.522 ms


23/09/2020 04:13:25 UTC
--------------------

TRACEROUTE:
traceroute to 40.136.63.18 (40.136.63.18), 15 hops max, 60 byte packets
 1  Blizzard Blizzard  1.240 ms  1.233 ms  1.231 ms
 2  37.244.23.3 (37.244.23.3)  1.848 ms  1.862 ms  1.863 ms
 3  24.105.62.152 (24.105.62.152)  1.851 ms  1.851 ms  1.852 ms
 4  137.221.66.10 (137.221.66.10)  2.861 ms  2.874 ms  2.938 ms
 5  * * *
 6  137.221.69.32 (137.221.69.32)  3.211 ms  2.368 ms  2.730 ms
 7  ch1-eqix.windstream. net (208.115.136.149)  1.480 ms  1.508 ms  1.482 ms
 8  ae1-0.cr02.chcg23-il.us.windstream. net (40.136.117.38)  1.539 ms  1.549 ms  1.536 ms
 9  * * *
10  ae0-0.agr01.stls01-mo.us.windstream. net (40.136.112.67)  7.709 ms  7.725 ms  7.819 ms
11  te12-4.pe01.stls01-mo.us.windstream. net (40.136.115.143)  8.243 ms  8.325 ms  8.333 ms
12  h18.63.136.40.static.ip.windstream. net (40.136.63.18)  10.692 ms  10.731 ms  10.876 ms
13  h18.63.136.40.static.ip.windstream. net (40.136.63.18)  10.885 ms  10.640 ms  10.635 ms


23/09/2020 04:13:25 UTC
--------------------

MTR:
Start: Wed Sep 23 04:13:25 2020 Blizzard  1.|-- Blizzard                             0.0%    10    0.2   0.2   0.2   0.3   0.0
  2.|-- 37.244.23.3                              0.0%    10    0.4   0.9   0.4   5.0   1.3
  3.|-- 24.105.62.152                            0.0%    10    0.7   0.8   0.5   1.0   0.0
  4.|-- 137.221.66.10                            0.0%    10   33.0   5.1   1.8  33.0   9.8
  5.|-- ???                                     100.0    10    0.0   0.0   0.0   0.0   0.0
  6.|-- 137.221.69.32                            0.0%    10   74.8  11.3   2.2  74.8  22.8
  7.|-- ch1-eqix.windstream. net                  0.0%    10    1.5   1.6   1.4   2.1   0.0
  8.|-- ae1-0.cr02.chcg23-il.us.windstream. net   0.0%    10    3.5   5.7   1.5  14.5   3.7
  9.|-- ae3.cr02.chcg02-il.us.windstream. net    70.0%    10    1.6   1.6   1.6   1.7   0.0
 10.|-- h67.112.136.40.static.ip.windstream. net  0.0%    10    7.6   9.1   7.6  22.5   4.7
 11.|-- te12-4.pe01.stls01-mo.us.windstream. net  0.0%    10    8.2  23.0   8.2 130.3  38.2
 12.|-- h18.63.136.40.static.ip.windstream. net   0.0%    10   10.6  10.7  10.6  10.7   0.0


23/09/2020 04:13:25 UTC
--------------------

MTR:
Start: Wed Sep 23 04:13:25 2020 Blizzard  1.|-- Blizzard                             0.0%    10    0.2   0.3   0.2   0.4   0.0
  2.|-- 24.105.18.2                              0.0%    10    0.7   0.6   0.5   0.8   0.0
  3.|-- 137.221.105.10                           0.0%    10    0.6   0.8   0.6   1.0   0.0
  4.|-- 137.221.66.16                            0.0%    10    0.5   2.7   0.3  14.0   4.8
  5.|-- 137.221.83.80                            0.0%    10  956.7 578.6  59.8 1164. 416.3
  6.|-- ???                                     100.0    10    0.0   0.0   0.0   0.0   0.0
  7.|-- 137.221.65.1                             0.0%    10   12.9  44.8  12.7 244.0  72.2
  8.|-- 137.221.65.7                             0.0%    10   12.9  13.3  12.6  15.4   0.7
  9.|-- 137.221.70.34                            0.0%    10   13.3  21.4  12.9  57.5  15.9
 10.|-- eqix-sv1.windstream. com                  0.0%    10   12.7  14.0  12.4  17.9   1.8
 11.|-- ae6-0.cr02.lsaj01-ca.us.windstream. net   0.0%    10   23.3  23.2  23.1  23.3   0.0
 12.|-- ae5-0.cr01.lsaj01-ca.us.windstream. net   0.0%    10   23.3  23.3  23.1  23.4   0.0
 13.|-- ae18-0.cr01.dlls02-tx.us.windstream. net 40.0%    10   40.7  40.8  40.6  41.0   0.0
 14.|-- ae0.agr02.stls01-mo.us.windstream. net    0.0%    10   57.2  60.6  57.0  90.2  10.4
 15.|-- te12-3.pe01.stls01-mo.us.windstream. net  0.0%    10   58.3  69.3  58.1 168.2  34.7
 16.|-- h18.63.136.40.static.ip.windstream. net   0.0%    10   60.7  60.6  60.6  60.7   0.0


23/09/2020 04:13:25 UTC
--------------------

Hey there,

The downstream looks great! No packet loss, relatively low latency. The works!

I think this one is either going to be software related or a problem with upstream data. Please be sure to try troubleshooting security applications and update the operating system.

If there’s still a problem after that go ahead and grab a winMTR so we can further investigate the problem. Here are the instructions:

  1. Download the tool from this page
  2. Enter the game IP into the “host” field. The IP address for our games are listed on the winMTR instructions page
  3. Start the test and play the affected game for at least 15 minutes. Ensure the problem happens while the winMTR tool is running.
  4. After recording the problem data, click “export text” and save the winMTR file in an easy to find location.
  5. Once you have that made, open the file. You’ll need to copy and paste the contents of the Text document into the post, and put four Tilde (~) marks above the winMTR. It’ll look like this:
WinMTR goes here

If you have issues pasting here, please use Pastebin and post the link (ex: Pastebin (dot) com/123456).