High ping, tracert, general connectivity issues these past 2 weeks

[defi12]

I've included tracert, modem log, and upstream/downstream information below. Let me know if any more information is needed.

Can anyone please help me in figuring out what's going on? Up until recently I haven't had any problems whatsoever with my internet connection but now I'm experiencing insanely high ping (from 200ms up to 2000ms) and RTT while playing Overwatch. At first I thought it was just on the Overwatch server end but after running ping and tracert from cmd, that doesn't seem to be the case. And as of this past weekend, I've been experiencing a lot of timeouts when simply browsing websites and having Skype audio calls. This issue has been happening on a consistent basis since about 2 weeks ago. I'm connected via ethernet.

I'm on an internet-only plan, no cable splitter in the apartment. The coax cable is hooked up to modem, my computer is hooked up to the modem via ethernet cable (there's also a wifi router connected to the modem but like I said, my computer is connected directly to the modem through an ethernet cable).

Any help would be very appreciated!

tracert information:

Tracing route to google.com [209.85.144.101]
over a maximum of 30 hops:

  1   857 ms  1024 ms   253 ms  192.168.0.1
  2   155 ms    43 ms    38 ms  cpe-24-165-176-1.neo.res.rr.com [24.165.176.1]
  3   210 ms    97 ms   147 ms  tge7-5.clhgohcc03h.midwest.rr.com [24.164.106.145]
  4   900 ms   175 ms    79 ms  be22.mcdnohbg01r.midwest.rr.com [24.33.103.84]
  5    47 ms    39 ms    85 ms  be14.pltsohae01r.midwest.rr.com [65.29.1.87]
  6   216 ms    37 ms    75 ms  be25.clmkohpe01r.midwest.rr.com [65.29.1.28]
  7   194 ms    47 ms    98 ms  bu-ether35.chctilwc00w-bcr00.tbone.rr.com [107.14.19.60]
  8   394 ms   163 ms   103 ms  bu-ether11.chcgildt87w-bcr00.tbone.rr.com [66.109.6.20]
  9   347 ms    40 ms    39 ms  216.3.52.41
 10   131 ms    43 ms   115 ms  216.3.52.62
 11    39 ms    39 ms    40 ms  216.239.40.102
 12    43 ms    48 ms    45 ms  209.85.254.238
 13    53 ms    48 ms    46 ms  209.85.143.171
 14   262 ms    65 ms    86 ms  216.239.48.154
 15   258 ms    73 ms    86 ms  216.239.49.145
 16     *        *        *     Request timed out.
 17     *        *        *     Request timed out.
 18     *        *        *     Request timed out.
 19     *        *        *     Request timed out.
 20     *        *        *     Request timed out.
 21     *        *        *     Request timed out.
 22     *        *        *     Request timed out.
 23     *        *        *     Request timed out.
 24   196 ms    48 ms    40 ms  qv-in-f101.1e100.net [209.85.144.101]

Trace complete.

Here is the modem event log (I started copying the log information after July 27th of this year):

Mon Sep 12 16:48:00 2016	Critical (3)	Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=44:e1:37:d2:38:8f;CMTS-MAC=00:01:5c:31:3b:d1;CM-QOS=1.1;CM-VER=3.0;
Mon Sep 12 13:15:44 2016	Notice (6)	TLV-11 - unrecognized OID;CM-MAC=44:e1:37:d2:38:8f;CMTS-MAC=00:01:5c:31:3b:d1;CM-QOS=1.1;CM-VER=3.0;
Mon Sep 12 13:15:43 2016	Error (4)	Missing BP Configuration Setting TLV Type: 17.9;CM-MAC=44:e1:37:d2:38:8f;CMTS-MAC=00:01:5c:31:3b:d1;CM-QOS=1.1;CM-VER=3.0;
Mon Sep 12 13:15:43 2016	Error (4)	Missing BP Configuration Setting TLV Type: 17.8;CM-MAC=44:e1:37:d2:38:8f;CMTS-MAC=00:01:5c:31:3b:d1;CM-QOS=1.1;CM-VER=3.0;
Time Not Established	Warning (5)	DHCP WARNING - Non-critical field invalid in response ;CM-MAC=44:e1:37:d2:38:8f;CMTS-MAC=00:01:5c:31:3b:d1;CM-QOS=1.0;CM-VER=3.0;
Time Not Established	Notice (6)	WiFi Interface [wl0] set to Channel 11 (Side-Band Channel:N/A) - Reason:INIT
Mon Sep 12 08:01:41 2016	Critical (3)	Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=44:e1:37:d2:38:8f;CMTS-MAC=00:01:5c:31:3b:d1;CM-QOS=1.1;CM-VER=3.0;
Time Not Established	Critical (3)	No Ranging Response received - T3 time-out
Sun Sep 11 14:36:47 2016	Critical (3)	Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=44:e1:37:d2:38:8f;CMTS-MAC=00:01:5c:31:3b:d1;CM-QOS=1.1;CM-VER=3.0;
Fri Sep 09 23:56:23 2016	Critical (3)	Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=44:e1:37:d2:38:8f;CMTS-MAC=00:01:5c:31:3b:d1;CM-QOS=1.1;CM-VER=3.0;
Fri Sep 09 19:17:54 2016	Critical (3)	Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=44:e1:37:d2:38:8f;CMTS-MAC=00:01:5c:31:3b:d1;CM-QOS=1.1;CM-VER=3.0;
Fri Aug 26 09:19:15 2016	Critical (3)	Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=44:e1:37:d2:38:8f;CMTS-MAC=00:01:5c:31:3b:d1;CM-QOS=1.1;CM-VER=3.0;
Time Not Established	Critical (3)	No Maintenance Broadcasts for Ranging opportunities received - T2 time-out;CM-MAC=44:e1:37:d2:38:8f;CMTS-MAC=00:01:5c:31:3b:d1;CM-QOS=1.0;CM-VER=3.0;
Time Not Established	Critical (3)	No Ranging Response received - T3 time-out
Time Not Established	Critical (3)	No Ranging Response received - T3 time-out
Time Not Established	Critical (3)	No Maintenance Broadcasts for Ranging opportunities received - T2 time-out;CM-MAC=44:e1:37:d2:38:8f;CMTS-MAC=00:01:5c:31:3b:d1;CM-QOS=1.0;CM-VER=3.0;
Time Not Established	Critical (3)	No Ranging Response received - T3 time-out
Time Not Established	Critical (3)	No Ranging Response received - T3 time-out
Time Not Established	Critical (3)	No Ranging Response received - T3 time-out

The modem shows this for channel information:

Downstream Bonded Channels
Channel	Lock Status	Modulation	Channel ID	Frequency	Power	SNR	Correctables	Uncorrectables
1	Locked	QAM256	1	657000000 Hz	11.2 dBmV	37.3 dB	0	0
2	Locked	QAM256	2	663000000 Hz	10.9 dBmV	37.2 dB	0	0
3	Locked	QAM256	3	669000000 Hz	10.9 dBmV	37.1 dB	0	0
4	Locked	QAM256	4	675000000 Hz	11.1 dBmV	37.7 dB	0	0
5	Locked	QAM256	5	681000000 Hz	11.0 dBmV	37.7 dB	0	0
6	Locked	QAM256	6	687000000 Hz	12.0 dBmV	36.6 dB	0	0
7	Locked	QAM256	7	693000000 Hz	11.8 dBmV	36.8 dB	0	0
8	Locked	QAM256	8	699000000 Hz	11.8 dBmV	36.8 dB	0	0

Upstream Bonded Channels
Channel	Lock Status	US Channel Type	Channel ID	Symbol Rate	Frequency	Power
1	Locked	ATDMA	8	2560 Ksym/sec	37000000 Hz	41.2 dBmV
2	Locked	TDMA	5	2560 Ksym/sec	19400000 Hz	41.2 dBmV
3	Locked	ATDMA	6	5120 Ksym/sec	24200000 Hz	41.2 dBmV
4	Locked	ATDMA	7	5120 Ksym/sec	30600000 Hz	41.2 dBmV

[MsRaye]

This line says you have an issue with yourlocal ethernet connection

1   857 ms  1024 ms   253 ms  192.168.0.1

 That should be <2ms. for a wired connection and maybe 20-40 ms for a wireless one.

 What modem do you have and where/ how exactly are the router and computer connected to it?

[defi12]

My modem is a Motorola/Arris Surfboard SBG6580. It's a modem and wifi router but I wound up getting a standalone router about a week ago so I could get a stronger signal to reach the back of the apartment.

My computer is connected to the modem through one of the ethernet ports on the back. The router is connected through another ethernet port on the back of the modem. So the modem has coax and two ethernet cables connected to it.

[MsRaye]

If the 6580 is in bridged mode that's a problem. recheck ping with the second router unplugged.

 I hope they're not on the same rf channel with the same DHCP gateways and start

Could also be a bad ethernet cable or nic port setting

however some sort of coaxial issue is causing the T2-3-4 errors as well.

 So there's at least 2 things wrong

[defi12]

I unplugged the second router power cable and ethernet connection to the modem. I don't know if it's on the same RF channel as the modem/router. When I got it last Thursday, I just plugged it in, connected to the new network on my laptop, went to 192.168.1.1, and changed the default passwords for the network and router access. Didn't configure anything else.

EDIT: I checked the modem settings. It does not appear to be in bridged mode (according to Wireless> Bridging settings).

Here's the tracert now:

Tracing route to google.com [209.85.144.113]
over a maximum of 30 hops:

1 <1 ms 2 ms 1 ms 192.168.0.1
2 658 ms 390 ms 387 ms cpe-24-165-176-1.neo.res.rr.com [24.165.176.1]
3 418 ms 382 ms 364 ms tge7-5.clhgohcc03h.midwest.rr.com [24.164.106.145]
4 404 ms 393 ms 356 ms be22.mcdnohbg01r.midwest.rr.com [24.33.103.84]
5 413 ms 344 ms 335 ms be14.pltsohae01r.midwest.rr.com [65.29.1.87]
6 34 ms 22 ms 15 ms be25.clmkohpe01r.midwest.rr.com [65.29.1.28]
7 32 ms 29 ms 31 ms bu-ether45.chctilwc00w-bcr00.tbone.rr.com [107.14.19.36]
8 30 ms 31 ms 31 ms bu-ether11.chcgildt87w-bcr00.tbone.rr.com [66.109.6.20]
9 26 ms 26 ms 27 ms 216.3.52.41
10 26 ms 26 ms 26 ms 216.3.52.62
11 27 ms 27 ms 25 ms 216.239.40.102
12 27 ms 27 ms 25 ms 209.85.254.238
13 29 ms 28 ms 29 ms 209.85.143.171
14 36 ms 37 ms 38 ms 216.239.48.154
15 37 ms 37 ms 37 ms 216.239.49.145
16 * * * Request timed out.
17 * * * Request timed out.
18 * * * Request timed out.
19 * * * Request timed out.
20 * * * Request timed out.
21 * * * Request timed out.
22 * * * Request timed out.
23 * * * Request timed out.
24 38 ms 37 ms 37 ms qv-in-f113.1e100.net [209.85.144.113]

Trace complete.

[MsRaye]

That's baffling.... 1 is  now good 2 on up is bad

Where are you? Northfield or Twinsburg?

 192.168.1.1 should work behind 192.168.0.1

but if both are on the same wireless channel, maybe not... You do have different SSID's in them, correct?

[defi12]

Cleveland Heights.
Yeah, both have different SSIDs. The second router is still completely unplugged though, so I don't think there'd be any interference from it?

[MsRaye]

You're right by 7 severance  circlewhere the main head end is... Do they still have a service desk there?

Do you own that modem or renting it? I'd get another if a rental.

Did anything change since the outing early this morning?   Is that when the tracert's went up?

 Your tracert routing is flakey as well as mine.... Everything is now routed thru clv hgts when I used to be routed out of MCDN (macedonia) I'm on a Twinsburg node, my lines like yours are 30+ years old, you're on old Viacom street lines.

[Julia_R]

I would be interested to see what happens if you plug the router back in and 

try another traceroute. 

Does that first hop skyrocket again? 

Regards,
Julia R.
Social Media Customer Care
Moderator-Community Forums

[defi12]

I'm not sure if they have a service desk. I was thinking about calling to see if they could look into the coaxial issues you mentioned earlier.
I own the router but was thinking about purchasing a new one in case there's something going on with the one I have. It's probably close to 3 or 4 years old at this point anyway.

Since yesterday/Monday I've still been having ping issues though they're less severe now (nothing in the 2000ms range). I've tried playing Overwatch and some other online games and monitoring the ping in each of them. Compared to this past weekend to the beginning of this month, I've at least managed to have brief periods where ping went down to the usual ~30 ms I'd experienced before these issues came up (as opposed to the 200 ms minimum I experienced this past weekend). Seconds or a minute later, it would spike back up to around 500 ms. I've pasted a tracert below.

I've noticed that I've been getting more timeouts over ethernet and wifi though, and my network indicator will say I have no internet access even though the modem up/down and internet connection lights are active.

The second router is still unplugged-- I'll report back with another tracert when I plug it back in later today.

tracert:

Tracing route to google.com [172.217.3.14]
over a maximum of 30 hops:

1 5 ms <1 ms <1 ms 192.168.0.1
2 54 ms 41 ms 36 ms cpe-24-165-176-1.neo.res.rr.com [24.165.176.1]
3 23 ms 132 ms 32 ms tge7-5.clhgohcc03h.midwest.rr.com [24.164.106.145]
4 18 ms 16 ms 21 ms be22.mcdnohbg01r.midwest.rr.com [24.33.103.84]
5 23 ms 26 ms 25 ms be14.pltsohae01r.midwest.rr.com [65.29.1.87]
6 29 ms 27 ms 28 ms be25.clmkohpe01r.midwest.rr.com [65.29.1.28]
7 47 ms 30 ms 38 ms bu-ether35.chctilwc00w-bcr00.tbone.rr.com [107.14.19.60]
8 40 ms 35 ms 39 ms bu-ether11.chcgildt87w-bcr00.tbone.rr.com [66.109.6.20]
9 30 ms 34 ms 29 ms 216.3.52.41
10 37 ms 40 ms 27 ms 216.3.52.54
11 27 ms 29 ms 29 ms 216.239.56.188
12 27 ms 30 ms 29 ms 72.14.237.133
13 51 ms 51 ms 50 ms 108.170.236.240
14 53 ms 73 ms 50 ms 216.239.40.226
15 50 ms 50 ms 50 ms 209.85.245.177
16 51 ms 48 ms 65 ms lga15s42-in-f14.1e100.net [172.217.3.14]

Trace complete.

Actually, here's a second one I ran while keeping Overwatch open in the background. I kept an eye on the ping monitor in-game and started a tracert when I saw it was in the 30ms range. Somewhere in the middle of the tracert it climbed up to around 180ms according to the in-game indicator and then dropped back down to around 60ms by the time the tracert ended.

Tracing route to google.com [172.217.3.14]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.0.1
2 44 ms 27 ms 27 ms cpe-24-165-176-1.neo.res.rr.com [24.165.176.1]
3 23 ms 31 ms 123 ms tge7-5.clhgohcc03h.midwest.rr.com [24.164.106.145]
4 36 ms 14 ms 22 ms be22.mcdnohbg01r.midwest.rr.com [24.33.103.84]
5 20 ms 21 ms 16 ms be14.pltsohae01r.midwest.rr.com [65.29.1.87]
6 20 ms 31 ms 22 ms be25.clmkohpe01r.midwest.rr.com [65.29.1.28]
7 29 ms 30 ms 31 ms bu-ether35.chctilwc00w-bcr00.tbone.rr.com [107.14.19.60]
8 40 ms 30 ms 31 ms bu-ether11.chcgildt87w-bcr00.tbone.rr.com [66.109.6.20]
9 28 ms 31 ms 32 ms 216.3.52.41
10 28 ms 29 ms 29 ms 216.3.52.54
11 42 ms 30 ms 29 ms 216.239.56.188
12 432 ms 386 ms 466 ms 72.14.237.133
13 52 ms 53 ms 54 ms 108.170.236.240
14 52 ms 53 ms 53 ms 216.239.40.226
15 65 ms 63 ms 51 ms 209.85.245.177
16 99 ms 49 ms 49 ms lga15s42-in-f14.1e100.net [172.217.3.14]