Slow real world speed - Good speedtest.net speeds

traceroute to 71.38.200.100 (71.38.200.100), 30 hops max, 60 byte packets
 1 192.168.41.1 (192.168.41.1)  0.331 ms  0.434 ms  0.536 ms
 2  10.114.100.1 (10.114.100.1)  7.549 ms  13.302 ms  13.310 ms
 3  100.127.69.138 (100.127.69.138)  13.327 ms  13.391 ms  13.409 ms
 4  72.215.229.22 (72.215.229.22)  14.599 ms  14.517 ms  14.579 ms
 5  ae57.bar2.Phoenix1.Level3.net (4.28.82.53)  14.645 ms  14.646 ms  14.512 ms
 6  ae-1-60.edge1.LosAngeles9.Level3.net (4.69.144.10)  23.724 ms  21.719 ms ae-                                                3-80.edge1.LosAngeles9.Level3.net (4.69.144.138)  21.874 ms
 7  ae-2-70.edge1.LosAngeles9.Level3.net (4.69.144.74)  21.746 ms ae-1-60.edge1.                                                LosAngeles9.Level3.net (4.69.144.10)  19.076 ms ae-3-80.edge1.LosAngeles9.Level3                                                .net (4.69.144.138)  18.660 ms
 8  los-brdr-01.inet.qwest.net (63.146.27.33)  21.795 ms  18.640 ms  20.146 ms
 9  * * *
10  71.222.249.122 (71.222.249.122)  51.042 ms  50.814 ms  50.925 ms

traceroute to 107.2.39.56 (107.2.39.56), 30 hops max, 60 byte packets
 1  192.168.41.1 (192.168.41.1)  0.312 ms  0.411 ms  0.544 ms
 2  10.114.100.1 (10.114.100.1)  11.285 ms  11.272 ms  11.270 ms
 3  100.127.69.138 (100.127.69.138)  11.611 ms  11.603 ms  12.211 ms
 4  72.215.229.22 (72.215.229.22)  16.766 ms  12.738 ms  12.737 ms
 5  langbprj01-ae3.0.rd.la.cox.net (68.1.5.137)  25.067 ms  25.007 ms  24.962 ms
 6  te-0-5-0-3-pe02.600wseventh.ca.ibone.comcast.net (173.167.57.109)  26.139 ms  24.313 ms  24.268 ms
 7  hu-1-0-0-1-cr02.losangeles.ca.ibone.comcast.net (68.86.88.13)  25.007 ms hu-0-5-0-3-cr02.losangeles.ca.ibone.comcast.net (68.86.83.29)  25.546 ms hu-0-5-0-2-cr02.losangeles.ca.ibone.comcast.net (68.86.83.25)  24.641 ms
 8  be-7922-ar02.pimaco.az.pima.comcast.net (68.86.93.118)  35.228 ms  35.400 ms  35.323 ms
 9  be-1-sur02.snyder.az.pima.comcast.net (68.87.172.18)  35.726 ms  35.914 ms  35.938 ms
10  te-0-1-1-ten01.snyder.az.pima.comcast.net (68.87.172.174)  34.830 ms  35.909 ms te-0-1-0-ten01.snyder.az.pima.comcast.net (69.139.177.142)  35.568 ms

Here are a couple of places I've tried to send files to (sftp and ftp both respond with similar speeds). I have yet to see any speeds close to my advertised speed on anything other than a speed test. Thank you.

I have had the same issues as you for months, and let me just say that you are in for a world of frustration, however let me share what I have learned over the past 3 months.

The reason why you are seeing good speed tests and awful real world speeds are the fact that speed tests are using multiple TCP streams to try and saturate your bandwidth.  In the real world, when you are uploading a file or live streaming, you are using a single TCP stream.  You should be able to mostly max out your available bandwidth with a single stream, however it seems that you are having the same issues as I am.

First of all, navigate to a single stream speed testing site such as testmy.net.  Run a 25MB upload only speed test and post the screenshot here.

If you are getting anything less than the 10mbit speeds consistently, call Cox and open up a ticket for your slow upload.  It is very important for you to ask for a Cox technician, NOT a subcontractor.  The subcontractors do not have the necessary equipment to diagnose an issue on your node.  Have the technician run a MER/BER rate test on your tap.  If it fails, he will open up a ticket with the maintenance team to get somebody out there to look at your node.

It took me a total of 6 tech visits and 3 maintenance tickets to get my issue resolved since the fixes only temporarily worked.  Keep with it and make sure that they stick through the issue.

Thanks noah, it was actually your post that led me here to give this a go.

That's why I wanted to prepare you for your upcoming months of frustration.  5 technician visits since January and my issue still isn't permanently resolved.  I have Ultimate internet and should be getting up to 30Mbps upload speed.  Earlier today, I consistently ran tests and received 20-29Mbps.  Tonight, this is the average speed that I am receiving:

I am sick and tired of fighting with Cox.  I have given up 5 weekend days waiting for technicians only for them to tell me "the signals look normal to me".  What is it going to take for this to gain visibility to somebody that can do something about this?

Another one taken tonight.  This is less than 20% of the speeds that I am paying for!!!

Yes, multiple FTP transfers appear to "stack" and if I combine the transfer results, the total speed is faster than the results I posted earlier. This is not that useful though, I need the speed for single transfers.

I've tested the application locally, and there is no speed throttling by the ftp server at all.

Also, the speed test results that I posted earlier show that even outside the application, I am receiving very slow upload speeds.

Did you read noahs post? Just because I can tack on multiple slow connections to achieve an acceptable speed, does not change the fact that any normal transfer scenarios will be drastically slower. Is this how cox is going to scoot around this issue? I cannot open up multiple connection for a single 4GB ISO that I need to transfer to a customer site.

Ok, I found an ftp client that will allow a multithread transfer for a single file. However, even with that I'm only getting about 5mb/s. Still half of what I would expect to be seeing. Even a speedtest.net test yields similar results.