Connectivity Issue

Here is my looking glass report. I would appreciate any insights in regards to the recent connectivity issue I have been having;

PING:
PING 50.90.121.129 (50.90.121.129) 56(84) bytes of data.
64 bytes from 50.90.121.129: icmp_seq=1 ttl=51 time=74.6 ms
64 bytes from 50.90.121.129: icmp_seq=2 ttl=51 time=63.5 ms
64 bytes from 50.90.121.129: icmp_seq=3 ttl=51 time=62.5 ms
64 bytes from 50.90.121.129: icmp_seq=4 ttl=51 time=63.6 ms

— 50.90.121.129 ping statistics —
4 packets transmitted, 4 received, 0% packet loss, time 2997ms
rtt min/avg/max/mdev = 62.598/66.116/74.669/4.961 ms

08/06/2018 11:51:23 UTC

TRACEROUTE:
traceroute to 50.90.121.129 (50.90.121.129), 15 hops max, 60 byte packets
1 24.105.30.3 (24.105.30.3) 0.787 ms 0.803 ms 1.064 ms
2 * * *
3 137.221.66.2 (137.221.66.2) 1.268 ms 1.350 ms 1.421 ms
4 137.221.68.66 (137.221.68.66) 1.226 ms 1.226 ms 1.226 ms
5 137.221.68.32 (137.221.68.32) 0.857 ms 1.061 ms 1.067 ms
6 ae34.pr1.lax10.tbone.rr. com (66.109.9.160) 0.736 ms 0.720 ms 0.711 ms
7 bu-ether17.tustca4200w-bcr00.tbone.rr. com (107.14.19.55) 52.556 ms 52.588 ms 52.583 ms
8 be4.clmkohpe01r.midwest.rr. com (107.14.19.37) 48.616 ms 48.659 ms 48.664 ms
9 bu-ether16.chctilwc00w-bcr00.tbone.rr. com (66.109.6.226) 52.005 ms 52.039 ms 52.041 ms
10 24.27.236.3 (24.27.236.3) 58.300 ms 58.330 ms 57.695 ms
11 72-31-203-109.net.bhntampa. com (72.31.203.109) 55.440 ms 55.473 ms 55.500 ms
12 ten0-1-0-0.INDP11-ser2.bhn. net (72.31.203.67) 55.838 ms 55.618 ms 55.662 ms
13 72-31-203-133.net.bhntampa. com (72.31.203.133) 55.215 ms 55.195 ms 55.193 ms
14 050-090-121-129.res.spectrum. com (50.90.121.129) 63.911 ms 64.320 ms 64.323 ms
15 050-090-121-129.res.spectrum. com (50.90.121.129) 66.186 ms 66.199 ms 62.267 ms

08/06/2018 11:51:23 UTC

MTR:
Start: Fri Jun 8 11:51:23 2018
HOST: Blizzard Loss% Snt Last Avg Best Wrst StDev
1.|-- 24.105.30.3 0.0% 10 0.5 0.6 0.5 0.7 0.0
2.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0
3.|-- 137.221.66.2 0.0% 10 1.4 1.4 1.3 1.5 0.0
4.|-- 137.221.68.66 0.0% 10 1.2 1.2 1.1 1.3 0.0
5.|-- 137.221.68.32 0.0% 10 0.9 1.0 0.9 1.1 0.0
6.|-- ae34.pr1.lax10.tbone.rr. com 0.0% 10 8.5 5.1 0.8 26.3 8.3
7.|-- bu-ether17.tustca4200w-bcr00.tbone.rr. com 0.0% 10 53.3 52.7 50.0 55.8 1.7
8.|-- be4.clmkohpe01r.midwest.rr. com 0.0% 10 53.8 53.2 49.3 56.2 2.2
9.|-- bu-ether16.chctilwc00w-bcr00.tbone.rr. com 0.0% 10 49.7 51.6 48.6 54.9 1.8
10.|-- 24.27.236.3 0.0% 10 56.3 58.3 55.2 61.6 1.9
11.|-- 72-31-203-109.net.bhntampa. com 0.0% 10 55.5 55.5 55.5 55.6 0.0
12.|-- ten0-1-0-0.INDP11-ser2.bhn. net 0.0% 10 55.8 55.9 55.8 56.1 0.0
13.|-- 72-31-203-133.net.bhntampa. com 0.0% 10 55.2 55.3 55.2 55.3 0.0
14.|-- 050-090-121-129.res.spectrum. com 0.0% 10 64.4 63.7 62.7 65.0 0.5

08/06/2018 11:51:23 UTC

Do you live in the carribbean by chance? The last few hubs reporting back are Florida hubs so it makes me wonder, If so, there is a trending issue with a network provider in that area and I would encourage you to follow the steps in this thread: