Upload speeds are extremely low

Start	Cox Net	Download Speed	Upload Speed	Latency	Your IP Address	Cox Market
Tue Dec 29 10:19 PM	Yes	117 Mbps	11 Mbps	12 millisec	*.*.*.*	Providence

The upload speed looks fine on the speed test, but actual practice when I stream to Twitch, upload to Youtube, or upload to a remote server, the speeds are far lower than what the speed test reports. The problem for me is that the uploads to these locations were working perfectly fine after the last time (several months ago) that I had a similar problem. I just figured that maybe there might be some infrastructure changes or something going on (hopefully not for another year again).

Edit: It is possible that there's any kind of throttling going on? I am wondering about this just because of the nature (now and before).

Here's one readout going to Youtube as I upload videos there from time to time. I ran this for over 10 minutes (2 second ping intervals).

As for Twitch, I can't really run a traceroute all the way to their ingest servers, so I use a bandwidth test tool that someone created for it. It measures both ping and the potential quality of the stream based on how consistent the upload rate is I believe (100 being best, 0 being lowest).

Here's one from testmy.net, I did a 100 MB upload to their NY server.

I also ran one from dslreports as well, it seems they have a new speedtest tool. Although, the upload doesn't seem to reflect the reality of my speed that I get when I upload to Youtube and Twitch (the two main places where I upload to), but it's probably due to them testing multiple sites/streams at once.

I would put more stock behind the DSLReports test. Your upload and latency looks good. So overall throughput is good.

How many T3 errors do you see a day? Also could you post a ping -n 50 10.4.136.1  ? I think there may a slight overhead noise issue i your node. I point to the slightly high side upstream power level and packet loss between first hop (your network?) 

On top of that I think there may me some saturation between providers to West-coast servers. I assume your east coast? How long has this issue been happening? 

@Tecknowhelp - I am in Connecticut. As noted in my original post, I had 1-2 T3 time outs per day from December 22-26. I did get one more T3 time out today, about 15 minutes ago according to the modem log. As far as I'm aware of, my upstream power levels have been at that range for as long as I can remember (around 48-50). Below is the ping -n 50 result for the first node/hop outside of the house. There is a bit of latency jitter I guess, even though it's still pretty low.

Ping statistics for 10.4.136.1
    Packets: Sent = 50, Received = 49, Lost = 1 (2% loss),
Approximate round trip times in milli-seconds:
    Minimum = 7ms, Maximum = 16ms, Average = 9ms

@ChrisL - Just to check something else, I decided to try testing my upload to my friend's Teamspeak 3 server out in Chicago, IL (I believe). At least for this one, I can easily point out that it's a problem at Level 3.

Thanks for the replies so far, I just want to see if I can narrow down the issue and resolve it in a timely manner.

Second trace shows different data. That looks to be a issue between Cox and Level3. I am in RI and don't seem to be having the problem, at least as of now. Is it intermittent? Also, two of my Level3 hops are blocking ICMP. I can download WinMTR to compare if you want.

Tracing route to server.white-fang.com [50.31.98.174]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms router.asus.com [192.168.1.1]
2 9 ms 8 ms 10 ms 10.2.48.1
3 8 ms 9 ms 7 ms 172.23.179.50
4 12 ms 9 ms 17 ms ip98-190-33-125.ri.ri.cox.net [98.190.33.125]
5 14 ms 16 ms 16 ms nyrkbprj01-ae3.0.rd.ny.cox.net [68.1.5.157]
6 * * * Request timed out.
7 * * * Request timed out.
8 37 ms 35 ms 35 ms NOZONE-INC.ear2.Chicago2.Level3.net [4.71.248.20
2]
9 34 ms 37 ms 34 ms te8-7.dist02.chi18.steadfast.net [208.100.32.59]

10 34 ms 35 ms 35 ms 70-202-67-ip40.securedserverspace.com [67.202.70
.40]
11 34 ms 35 ms 33 ms server.white-fang.com [50.31.98.174]

Trace complete.

If you're referring to the TS server, I'm not sure to be honest, since I don't use it on a regular basis. I used it as an additional testing location since I am familiar on how much speed I should be getting there.

As for Twitch/Youtube, I'm not a frequent streamer or uploader, but ever since I discovered that I have a problem with my upload, I've been testing my stream or upload at least once a day (usually at different times of the day too).

I still get some T3's each day. I'm not too sure on the count since the log in my modem seems a little weird at times, but I'll probably say that it happens a few times a day. Again, there were no configuration changes inside the house, double checked the cables to make sure they didn't get loose, etc.

Edit: This is my last T3 that popped up in the log.

I'm beginning to think that maybe there was some weather sometime late December that might have caused something to happen, but unfortunately I can't remember anything specific. The reason I am thinking this is due to my previous issue from over a year ago, where my download works fine, but upload is stuck at very low levels. I even had a tech come to the house then and he took some readings and such, but it didn't fix the problem. Eventually after about a year of waiting, the problem was "automagically" fixed (I assume it was somewhere external as I eventually gave up).

I just hope that I don't have to wait that amount of time again.

Bison said:
I still get some T3's each day.

Bison said:
there were no configuration changes inside the house,

T3's are not caused by any configuration issue. T3's are transmit errors as part of the DOCSIS process used via the coaxial. Usually caused by problems with the signal to noise(SNR) on the upstream(US). Hard to track since only Cox can see the US SNR. If noise is leaking into one the frequency for a specific US channel, you will only experiance the problem when the modem locks onto the specific channel. Also, the noise itself can be intermident, making it harder to track.

I personally have been troubleshooting T3 errors for several months, and all I can say is good luck. Getting the issue escalated to maintence is the first step, but be sure to GET THE TICKET NUMBER. I can not stress that enough. Follow up is key. Also, try to have someone look at your account and see if the issue was refereed to maintence before, and if so, what was that resolution. Many times noise issues stop on their own, so the root cause may not have been fixed and could be relevant to your current issue.

Yeah, I saw your thread of your own issue. Although it is interesting to know that noise issues can stop on their own (so it's entirely possible that my last issue really did "automagically" resolve itself).

I've been manually tracking each T3 as it appears, since my cable modem log only appears to record/overwrite the top-most entry. Compared to late December, where I was getting maybe 1-2 a day, it appears I'm getting a few/several of them every day now.

Jan 13 2016 23:07:44 3-Critical R02.0 No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=00:1b:54:c9:b6:62;CM-QOS=1.1;CM-VER=3.0;

Jan 13 2016 21:24:04 3-Critical R02.0 No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=00:1b:54:c9:b6:62;CM-QOS=1.1;CM-VER=3.0;

Jan 13 2016 20:34:14 3-Critical R02.0 No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=00:1b:54:c9:b6:62;CM-QOS=1.1;CM-VER=3.0;

Jan 13 2016 14:56:22 3-Critical R02.0 No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=00:1b:54:c9:b6:62;CM-QOS=1.1;CM-VER=3.0;