Initial connection delays requiring retries - Time Warner Internet

#1
This question is about "Initial connection delays requiring retries", with Time Warner Cable internet and apps. I have noticed over the last two weeks that initial connections over the Internet are failing and many times require retries/refreshes. Once the connections are made I get full bandwith. It seems to be worse at different times of the day. Usually mornings are when it is most prevalent. My father lives 11 blocks a way and is experiencing the same issue. When I do speed tests (Ookla) with it takes a very long time, usually about 10 seconds, to find a server to do the test with. With Spectrum's speed test (Internet Speed Test - Cable Speed & Bandwidth Test | Spectrum) I get "Could not connect to the test server. A firewall could be blocking the connection or the server might be having some issues. Please try again later." After a few taps of the RETRY button, the test runs at full bandwith.

I've been checking my modem/router logs and see a lot of DoS attack entries agains other IP address. I wonder if this is causing problems on Spectrum's network. Below are some of the log entries from today.

Description Count Last Occurrence Target Source
[DoS attack: Teardrop or derivative] from 122.133.109.0, port 0 1 Tue Nov 27 10:38:01 2018 36.238.74.32:0 122.133.109.0:0
[DoS attack: Ping Of Death] from 122.133.109.0, port 0 2 Tue Nov 27 10:38:01 2018 36.238.74.32:0 122.133.109.0:0
[DoS attack: Teardrop or derivative] from 122.133.109.0, port 0 15 Tue Nov 27 10:38:01 2018 36.238.74.32:0 122.133.109.0:0
[DoS attack: Illegal Fragments] from 122.133.109.0, port 0 3 Tue Nov 27 10:32:25 2018 36.238.74.32:0 122.133.109.0:0
[DoS attack: Teardrop or derivative] from 122.133.109.0, port 0 8 Tue Nov 27 10:32:10 2018 36.238.74.32:0 122.133.109.0:0
[DoS attack: Illegal Fragments] from 122.133.109.0, port 0 1 Tue Nov 27 10:32:10 2018 36.238.74.32:0 122.133.109.0:0
[DoS attack: Teardrop or derivative] from 122.133.109.0, port 0 4 Tue Nov 27 10:32:10 2018 36.238.74.32:0 122.133.109.0:0
[DoS attack: Ping Of Death] from 122.133.109.0, port 0 3 Tue Nov 27 10:30:29 2018 36.238.74.32:0 122.133.109.0:0
[DoS attack: Teardrop or derivative] from 122.133.109.0, port 0 1 Tue Nov 27 10:30:02 2018 36.238.74.32:0 122.133.109.0:0
[DoS attack: Illegal Fragments] from 122.133.109.0, port 0 1 Tue Nov 27 10:30:01 2018 36.238.74.32:0 122.133.109.0:0
[DoS attack: Teardrop or derivative] from 122.133.109.0, port 0 2 Tue Nov 27 10:30:01 2018 36.238.74.32:0 122.133.109.0:0
[DoS attack: Illegal Fragments] from 122.133.109.0, port 0 1 Tue Nov 27 10:30:01 2018 36.238.74.32:0 122.133.109.0:0
[DoS attack: Teardrop or derivative] from 122.133.109.0, port 0 1 Tue Nov 27 10:30:01 2018 36.238.74.32:0 122.133.109.0:0
[DoS attack: Illegal Fragments] from 122.133.109.0, port 0 1 Tue Nov 27 10:29:51 2018 36.238.74.32:0 122.133.109.0:0
[DoS attack: Teardrop or derivative] from 122.133.109.0, port 0 53 Tue Nov 27 10:29:49 2018 36.238.74.32:0 122.133.109.0:0
[DoS attack: Ping Of Death] from 122.133.109.0, port 0 4 Tue Nov 27 10:29:46 2018 36.238.74.32:0 122.133.109.0:0
[DoS attack: Illegal Fragments] from 122.133.109.0, port 0 1 Tue Nov 27 10:29:45 2018 36.238.74.32:0 122.133.109.0:0
[DoS attack: Ping Of Death] from 122.133.109.0, port 0 2 Tue Nov 27 10:29:45 2018 36.238.74.32:0 122.133.109.0:0
[DoS attack: Illegal Fragments] from 122.133.109.0, port 0 1 Tue Nov 27 10:29:45 2018 36.238.74.32:0 122.133.109.0:0
[DoS attack: Teardrop or derivative] from 122.133.109.0, port 0 8 Tue Nov 27 10:29:32 2018 36.238.74.32:0 122.133.109.0:0
[DoS attack: Teardrop or derivative] from 122.133.109.0, port 0 2 Tue Nov 27 10:26:47 2018 128.144.146.5:0 122.133.109.0:0
[DoS attack: Teardrop or derivative] from 122.133.109.0, port 0 1 Tue Nov 27 10:23:21 2018 184.209.235.216:0 122.133.109.0:0

Initial connection delays requiring retries?
 
Top