Latency Spikes and constant packet loss icon for past 2 or so months

See title. Recently when playing overwatch, regardless of the servers i play on I am constantly showing the packet loss icon and connection issue icon in the top left side of my screen. My ping will spike up and down all game when this happens. For example from a 90, all the sudden up to 100 or 110, then it goes back down. I have checked all of the cables on my end, updated drivers, and everything u can think of I have probably already done it (currently studying ccent and i have my sec+ and cissp so i know a little bit about networking if it helps)

I feel the problems too in game, for example if i play zarya and i hold left click into a stationary target, for example a rein that is frozen from mei’s ulti, i can actually hear my beam disconnecting even if im aiming dead center on the target(and visually see the damage not occur).

I am mainly playing from Japan on SEA servers, and normally i can get a decent 86-90 solid latency indicator that doesnt fluctuate too much in game even if i mainly connect to singapore servers in ranked matches. I play sometimes on korea servers with similar ping but slightly lower latency (around 70-75) but i have packet loss there as well. I rarely ever get a japanese server game. When i play strictly on NA, i get the packet loss too.

I am wondering if there is an issue with the undersea cables or cable damage in Japan since the last big earthquake we had a few days ago up in hokkaido. We have also been having alot of typhoon disasters which im thinking could have affected something. I have a popular tier 1 isp in Japan (ocn provider which uses the ntt lines) and i have a bandwidth plan of 100mb dl/ul(even though i know this technically doesnt matter when it comes to latency, thought i would mention it anyways).

Here is the packet loss I received from korea servers on the looking glass. Mind you i see packet loss no matter the server i play on ( japan, korea, or even NA with my NA friends):

TRACEROUTE:
traceroute to 124.98.249.61 (124.98.249.61), 15 hops max, 60 byte packets
1 Blizzard Blizzard 0.279 ms 0.259 ms 0.246 ms
2 117.52.34.2 (117.52.34.2) 0.531 ms 0.678 ms 0.743 ms
3 117.52.161.193 (117.52.161.193) 0.834 ms 0.892 ms 0.955 ms
4 137.221.66.100 (137.221.66.100) 1.890 ms 1.897 ms 1.895 ms
5 137.221.84.68 (137.221.84.68) 2.428 ms 2.431 ms 2.430 ms
6 137.221.84.32 (137.221.84.32) 0.551 ms 0.632 ms 0.606 ms
7 110.45.174.217 (110.45.174.217) 0.404 ms 0.431 ms 0.442 ms
8 110.45.129.77 (110.45.129.77) 0.480 ms 0.476 ms 0.425 ms
9 117.52.0.217 (117.52.0.217) 1.298 ms 1.301 ms 1.166 ms
10 61.43.224.209 (61.43.224.209) 1.620 ms 1.618 ms 1.514 ms
11 1.208.146.118 (1.208.146.118) 1.816 ms 1.771 ms 1.753 ms
12 1.208.106.246 (1.208.106.246) 55.899 ms 1.213.104.58 (1.213.104.58) 85.575 ms 1.208.106.246 (1.208.106.246) 55.640 ms
13 ae-0.ocn.osakjp02.jp.bb.gin.ntt.netx (61.200.80.10) 55.672 ms 48.649 ms 48.629 ms
14 153.149.219.145 (153.149.219.145) 28.588 ms 28.379 ms ae-9.r24.osakjp02.jp.bb.gin.ntt.netx (129.250.7.79) 60.447 ms
15 ae-1.r03.osakjp02.jp.bb.gin.ntt.netx (129.250.7.31) 61.037 ms 125.170.97.73 (125.170.97.73) 38.432 ms 38.492 ms

13/09/2018 10:37:31 UTC

PING:
PING 124.98.249.61 (124.98.249.61) 56(84) bytes of data.

— 124.98.249.61 ping statistics —
4 packets transmitted, 0 received, 100% packet loss, time 3001ms

13/09/2018 10:37:31 UTC

MTR:
Start: Thu Sep 13 10:37:31 2018 Blizzard 1.|-- Blizzard 0.0% 10 0.4 0.3 0.3 0.4 0.0
2.|-- 117.52.34.130 0.0% 10 0.6 0.8 0.5 2.2 0.5
3.|-- 117.52.161.209 0.0% 10 0.8 1.0 0.8 1.1 0.0
4.|-- 137.221.66.98 0.0% 10 4.4 1.6 0.6 5.1 1.7
5.|-- 137.221.84.66 0.0% 10 6.0 6.5 0.9 24.0 6.7
6.|-- 137.221.84.36 0.0% 10 0.7 0.7 0.7 0.8 0.0
7.|-- 110.45.174.213 0.0% 10 1.9 2.3 0.5 6.4 2.4
8.|-- 61-111-34-101.kidc.netx 0.0% 10 0.6 0.6 0.5 0.7 0.0
9.|-- 117.52.1.217 0.0% 10 1.3 2.0 1.2 6.7 1.7
10.|-- 61.42.234.253 0.0% 10 1.4 3.4 1.3 15.5 4.3
11.|-- 1.208.147.118 0.0% 10 1.6 1.5 1.5 1.6 0.0
12.|-- 1.208.106.246 10.0% 10 55.4 66.0 41.8 95.3 18.4
13.|-- ae-1.r31.tokyjp05.jp.bb.gin.ntt.netx 20.0% 10 86.8 70.7 46.9 87.5 17.6
14.|-- 125.170.96.33 0.0% 10 33.3 52.8 31.6 66.7 14.4
15.|-- ae-2.r02.osakjp02.jp.bb.gin.ntt.netx 0.0% 10 36.8 51.2 36.8 67.3 11.9
16.|-- 153.149.218.106 0.0% 10 84.8 73.4 53.7 93.7 14.7
17.|-- 122.1.245.54 0.0% 10 86.0 51.4 36.7 86.0 23.4
18.|-- 125.170.97.73 0.0% 10 86.0 59.1 46.9 86.8 18.8
19.|-- 125.170.97.130 0.0% 10 37.9 72.1 37.9 95.8 29.3
20.|-- 60.37.54.74 0.0% 10 38.8 44.3 38.2 94.7 17.7
21.|-- 153.149.137.14 20.0% 10 96.1 96.4 96.0 96.8 0.0
22.|-- 118.23.96.138 30.0% 10 47.8 50.5 47.5 66.9 7.3
23.|-- 122.1.173.138 30.0% 10 48.0 48.1 47.2 51.2 1.3

24.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0

13/09/2018 10:37:31 UTC

NOTE on some of the nodes i had to add an x at the end so it would actually let me post the address here in the forums. Just minus the x if you look it up.

Below is a recent WinMTR pulled from the practice range on a pse1 server. Looks like packet loss on almost every node. this was taken at 12:05 am on Japan time :frowning:

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

Host - % Sent Recv Best Avrg Wrst Last
ntt.setup - 0 114 114 1 2 14 1
122.1.173.138 - 6 95 90 7 17 31 17
122.1.173.158 - 5 99 95 8 19 31 17
118.23.96.137 - 6 95 90 9 21 38 20
153.149.137.9 - 5 99 95 9 19 34 19
60.37.54.69 - 7 91 85 10 22 60 20
ae-5.r03.tokyjp05.jp.bb.gin.ntt.netx - 3 103 100 17 28 43 29
ae-4.r30.tokyjp05.jp.bb.gin.ntt.netx - 30 54 38 23 30 40 34
ae-2.r00.tokyjp08.jp.bb.gin.ntt.netx - 5 99 95 17 28 44 29
ae-1.a00.tokyjp03.jp.bb.gin.ntt.netx - 3 104 101 17 29 70 27
ae-0.amazon.tokyjp03.jp.bb.gin.ntt.netx - 5 99 95 17 30 54 26
No response from host - 100 23 0 0 0 0 0
No response from host - 100 23 0 0 0 0 0
54.239.52.95 - 3 103 100 18 33 58 34
52.95.30.8 - 7 91 85 18 29 54 29
No response from host - 100 23 0 0 0 0 0
54.239.43.114 - 1 111 110 78 89 108 92
52.93.8.42 - 1 111 110 78 89 109 87
52.93.11.19 - 1 111 110 79 90 111 84
52.93.11.18 - 2 107 105 79 91 112 95
52.93.8.51 - 5 99 95 81 92 115 93
203.83.223.31 - 6 95 90 80 91 116 94
No response from host - 100 23 0 0 0 0 0
No response from host - 100 23 0 0 0 0 0
No response from host - 100 23 0 0 0 0 0
No response from host - 100 23 0 0 0 0 0
No response from host - 100 23 0 0 0 0 0
No response from host - 100 23 0 0 0 0 0
No response from host - 100 23 0 0 0 0 0
No response from host - 100 23 0 0 0 0 0
________________________________________________ ______ ______ ______ ______ ______ ______

Your ISP is likely causing the issue. In your WinMTR, the first few hops before attempting to reach Blizzard are dropping 5-7% of packets. It could be remaining damage from the natural disasters, but you’ll have to reach out to them to find out more information and to resolve this.

Thanks for the reply. Totally forgot about this. I just decided i have to live with it i guess. No matter which isp i switch to out here , its all the same. bad routing and extreme congestion… i need to go back to the usa lol

It’s not much better here when it comes to routing lately. So many natural disaster events happening means a lot of re-routing and repairs.