Upstream issues getting worse

Question

Having issues with T3 timeouts and packet loss since Monday. It's getting worse. Now seeing multiple T3 timeouts per hour causing average of 3-5% packet loss up to maximum of 10% packet loss. Modem and cable are both almost brand new. Nothing has changed on my end. This appears to be an issue with the Cox network infrastructure. I've had similar problems before and they fixed themselves after a while, but I need a reliable connection ASAP. Please advise of any known issues and ETA for repair.
Downstream signals and error counts are excellent. Upstream power levels are normal (38-40 dBmV). This appears to be an intermittent issue with the upstream connection, possibly due to RF ingress.

dave9 · Accepted Answer

Final update: my issue has been fully resolved. Cox followed up with me, and it was exactly what I thought it was (RF ingress on the node). This was repaired free of charge.
So if you're having similar problems, call for a tech and don't be scared off by the talk of a $75 fee. Look at it this way: if it's a Cox problem, you'll get your problem fixed and won't have to keep asking for help on the forums. And if it's a problem in your equipment, you can get it fixed for $75 which is a very low fee for on-site technical services. So either way you get your problem fixed. It's good to post here so you can get advice from others, but once you've ruled out your own equipment, call for a tech and get your problem fixed.

allan · Answer

@Dave9, Your modem is reporting some time out errors. Are there any splitters or signal amps on the cable line going to the modem? -Allan, Cox Support Forums Moderator

dave9 · Answer

No, it's a straight connection all the way to the demarc. All indoor cables have been replaced. Everything was working perfectly until Monday.

jonathanj · Answer

@Dave9

Since there aren't any splitters or amp we may need to schedule a technician out. Please email your full name and address to cox.help@cox.com. Also, include a link to this thread.

Jonathan J                                   
Cox Moderator

dave9 · Answer

E-mail sent. This morning I was experiencing up to 25% upstream packet loss, but 0% downstream packet loss. Please note this important data point that the packet loss appears to be upstream only.

dave9 · Answer

No reply to my e-mail yet, but here's more information showing 11% average and 23% peak upstream packet loss but 0% downstream packet loss. This affects any service that depends on upstream data (video conference, audio conference, gaming, etc.) As mentioned before, this seems to have started on Monday.
Upstream test:Accepted connection from (redacted), port 59453[&nbsp; 5] local (redacted) port 5201 connected to (redacted) port 64253[ ID] Interval&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Transfer&nbsp;&nbsp;&nbsp;&nbsp; Bandwidth&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Jitter&nbsp;&nbsp;&nbsp; Lost/Total Datagrams[&nbsp; 5]&nbsp;&nbsp; 0.00-1.00&nbsp;&nbsp; sec&nbsp; 2.64 MBytes&nbsp; 22.1 Mbits/sec&nbsp; 1.346 ms&nbsp; 34/372 (9.1%)[&nbsp; 5]&nbsp;&nbsp; 1.00-2.00&nbsp;&nbsp; sec&nbsp; 3.31 MBytes&nbsp; 27.8 Mbits/sec&nbsp; 0.825 ms&nbsp; 35/459 (7.6%)[&nbsp; 5]&nbsp;&nbsp; 2.00-3.00&nbsp;&nbsp; sec&nbsp; 3.26 MBytes&nbsp; 27.3 Mbits/sec&nbsp; 0.813 ms&nbsp; 35/452 (7.7%)[&nbsp; 5]&nbsp;&nbsp; 3.00-4.00&nbsp;&nbsp; sec&nbsp; 2.62 MBytes&nbsp; 22.0 Mbits/sec&nbsp; 1.645 ms&nbsp; 103/439 (23%)[&nbsp; 5]&nbsp;&nbsp; 4.00-5.00&nbsp;&nbsp; sec&nbsp; 3.11 MBytes&nbsp; 26.1 Mbits/sec&nbsp; 1.529 ms&nbsp; 81/479 (17%)[&nbsp; 5]&nbsp;&nbsp; 5.00-6.00&nbsp;&nbsp; sec&nbsp; 3.26 MBytes&nbsp; 27.3 Mbits/sec&nbsp; 0.824 ms&nbsp; 39/456 (8.6%)[&nbsp; 5]&nbsp;&nbsp; 6.00-7.00&nbsp;&nbsp; sec&nbsp; 3.31 MBytes&nbsp; 27.8 Mbits/sec&nbsp; 1.383 ms&nbsp; 39/463 (8.4%)[&nbsp; 5]&nbsp;&nbsp; 7.00-8.00&nbsp;&nbsp; sec&nbsp; 3.31 MBytes&nbsp; 27.8 Mbits/sec&nbsp; 1.333 ms&nbsp; 34/458 (7.4%)[&nbsp; 5]&nbsp;&nbsp; 8.00-9.00&nbsp;&nbsp; sec&nbsp; 3.22 MBytes&nbsp; 27.0 Mbits/sec&nbsp; 1.578 ms&nbsp; 47/459 (10%)[&nbsp; 5]&nbsp;&nbsp; 9.00-10.00&nbsp; sec&nbsp; 3.25 MBytes&nbsp; 27.3 Mbits/sec&nbsp; 0.748 ms&nbsp; 43/459 (9.4%)[&nbsp; 5]&nbsp; 10.00-10.14&nbsp; sec&nbsp;&nbsp; 384 KBytes&nbsp; 21.7 Mbits/sec&nbsp; 1.877 ms&nbsp; 4/52 (7.7%)- - - - - - - - - - - - - - - - - - - - - - - - -[ ID] Interval&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Transfer&nbsp;&nbsp;&nbsp;&nbsp; Bandwidth&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Jitter&nbsp;&nbsp;&nbsp; Lost/Total Datagrams[&nbsp; 5]&nbsp;&nbsp; 0.00-10.14&nbsp; sec&nbsp; 0.00 Bytes&nbsp; 0.00 bits/sec&nbsp; 1.877 ms&nbsp; 494/4548 (11%)
Downstream test:Connecting to host (redacted), port 5201Reverse mode, remote host (redacted) is sending[&nbsp; 4] local (redacted) port 53197 connected to (redacted) port 5201[ ID] Interval&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Transfer&nbsp;&nbsp;&nbsp;&nbsp; Bandwidth&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Jitter&nbsp;&nbsp;&nbsp; Lost/Total Datagrams[&nbsp; 4]&nbsp;&nbsp; 0.00-1.01&nbsp;&nbsp; sec&nbsp; 3.59 MBytes&nbsp; 29.9 Mbits/sec&nbsp; 0.110 ms&nbsp; 0/459 (0%)[&nbsp; 4]&nbsp;&nbsp; 1.01-2.01&nbsp;&nbsp; sec&nbsp; 3.58 MBytes&nbsp; 30.0 Mbits/sec&nbsp; 0.133 ms&nbsp; 0/458 (0%)[&nbsp; 4]&nbsp;&nbsp; 2.01-3.01&nbsp;&nbsp; sec&nbsp; 3.57 MBytes&nbsp; 29.8 Mbits/sec&nbsp; 0.132 ms&nbsp; 0/457 (0%)[&nbsp; 4]&nbsp;&nbsp; 3.01-4.00&nbsp;&nbsp; sec&nbsp; 3.58 MBytes&nbsp; 30.3 Mbits/sec&nbsp; 0.127 ms&nbsp; 0/458 (0%)[&nbsp; 4]&nbsp;&nbsp; 4.00-5.01&nbsp;&nbsp; sec&nbsp; 3.58 MBytes&nbsp; 29.8 Mbits/sec&nbsp; 0.134 ms&nbsp; 0/458 (0%)[&nbsp; 4]&nbsp;&nbsp; 5.01-6.01&nbsp;&nbsp; sec&nbsp; 3.58 MBytes&nbsp; 29.8 Mbits/sec&nbsp; 0.127 ms&nbsp; 0/458 (0%)[&nbsp; 4]&nbsp;&nbsp; 6.01-7.01&nbsp;&nbsp; sec&nbsp; 3.57 MBytes&nbsp; 30.2 Mbits/sec&nbsp; 0.117 ms&nbsp; 0/457 (0%)[&nbsp; 4]&nbsp;&nbsp; 7.01-8.02&nbsp;&nbsp; sec&nbsp; 3.58 MBytes&nbsp; 29.7 Mbits/sec&nbsp; 0.114 ms&nbsp; 0/458 (0%)[&nbsp; 4]&nbsp;&nbsp; 8.02-9.01&nbsp;&nbsp; sec&nbsp; 3.58 MBytes&nbsp; 30.3 Mbits/sec&nbsp; 0.119 ms&nbsp; 0/458 (0%)[&nbsp; 4]&nbsp;&nbsp; 9.01-10.02&nbsp; sec&nbsp; 3.58 MBytes&nbsp; 29.7 Mbits/sec&nbsp; 0.123 ms&nbsp; 0/458 (0%)- - - - - - - - - - - - - - - - - - - - - - - - -[ ID] Interval&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Transfer&nbsp;&nbsp;&nbsp;&nbsp; Bandwidth&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Jitter&nbsp;&nbsp;&nbsp; Lost/Total Datagrams[&nbsp; 4]&nbsp;&nbsp; 0.00-10.02&nbsp; sec&nbsp; 36.1 MBytes&nbsp; 30.3 Mbits/sec&nbsp; 0.116 ms&nbsp; 0/4624 (0%)

Forum Discussion

Upstream issues getting worse

8 Replies

Related Content

Packet loss due to upstream channels dropping

Morning Boot Issue

How to get COX to fix the low upstream power being provided to my address.

Downstream very slow, upstream fast.

Upstream Issues

Recent Discussions

The connection to smtp.cox.net failed !??!

Successful COX to Yahoo email transition with Thunderbird

Is there a maximum number or data size for e-mail messages transferring to Mac Mail via imap?

Successful Email transition to Yahoo: using Thunderbird on Windows

Problems with Email on Yahoo