Slow "Real World" upload speeds despite good speedtest.net results - SLOW AGAIN!!!

I am experiencing this same exact thing. At first, I thought it was my hosting provider, but I cannot uploaded above 0.16 Mbps via FTP. This despite a cox.com speed test which shows a 12 Mbps upload speed.

I've tested with various hosting providers.

Traceroute shows there is an issue with 100.127.70.194.

I am experiencing the same. FINALLY proof its their networks' fault it seems, since many of us experience it.

I am a twitch streamer, meaning I stream videos of myself live on the internet. When upload speeds are ridiculously slow and unstable like they have been lately, I am missing out on a source of revenue!

I think that thread was marked solved because of your post 
"Just an update. A few days in and upload speeds are consistently over 20mbps. Thank you everyone again for all of your help with this!"

What modem and router do you have now? I know you were having issues with the SB6190. New modem? What are your modem's signal levels?

Also, in your last thread, in your modem logs:

"Telnet user logged in from IP address 192.168.100.101."

Who is that telneting in? I though local telnet was disabled. Is that someone from Cox? 

Last, do you have any of the maintenance tickets from last time? I think the issue before was a issue with noise causing a low SNR overall, effecting BER which can cause packet loss. Basically SNR is the strength of the power level compared to the noise at the first layer of the OSI model. BER is the amount of packets sent compared to the amount failed, which related to uncorrectables on the downstream. Having the ticket number for the previous issue not only give you data on possible relations, but it will help them back track where they were last investigating the issue.

I had this issue for weeks.  It took 2 technician visits only for them to realize that there was noise on the line somewhere down the line.  It worked perfectly for almost 3 weeks and now we're back to slow speeds.

noah82 said:
I had this issue for weeks.  

Not sure what you mean by this. Are you going to do another post answering my questions? Did you only want to troubleshoot with a moderator? I read your previous posts, so I know the history. The question is how to troubleshoot from here. I had a problem with my internet that took 4 months to fix, sometimes going weeks being fine. Cable internet issues are complex. Need data to troubleshoot them.

@Tecknowhelp

I tried a few different modems during my last troubleshooting stint, but the one that I ultimately kept was the Arris 6183 since Cox was having issues with the 6190.

The ticket numbers that I have were work order number 77148189 and escalation number ksr2622131.

Hopefully this helps.  If there's any more information that I can give please let me know.

For some reason I'm not getting email notifications on this thread even though I've subscribed to it.  I answered your questions in another response.  Sorry for that delay.

noah82 said:
The ticket numbers that I have were work order number 77148189 and escalation number ksr2622131.

I wasn't asking for it for me, but asking if you had it or not, which you do. I would suggest calling Cox and asking for their Customer Advocate Department(CAD) and give them that info, along with general info and see if they can re-escalate it to field without having to send a technician to your house to get the ball rolling again. It will depend on how/why the previous ticket was closed. 

And just to confirm, your still seeing packet latency when connected direct to the modem? Or did that go away with the SB6183?

@Tecknowhelp

Would it be possible to have a good upload speed test, yet upload over time (either FTP or streaming media from my house to my iPad) be horrible?

Yes. When you do a upload speed, your measuring the time it takes to send bigger and bigger chunks of data to a test server. That test server is hosted by different groups depending on location. So you might live in CA, and get great upload to the test server in NV but speeds to a server in Texas is bad. Some of this is caused by peering congestion, but also if the traffic is somewhere on Cox's network. See here for a map of their backbones. I would find out the IP of where your streaming to/from and try a tracert and pathping. You can also try speed test to servers physically close to where you are trying to stream from. 

Also, FTP doesn't have the same kind of error correction as TCP or other protocols.  How are you transferring the data? As in what protocol and what clients at each end?

<<Only issue is with upload speeds - so that is what is referenced here>>

I am in Arizona. Cox.com speed test is pretty consistent (12 Mbps in Phoenix market, 9.3 Mbps in Providence market). Speed tests from other providers (Ookla, Speakeasy) show acceptable results.

Issue comes when I try to upload a large file.

First example is FTP. I have tried about 8 different FTP servers (located in Los Angeles, Phoenix, Austin, Boston, Atlanta, and other international locations). After an initial burst of around 100 KB/s (0.8 Mbps), it steadily drops to around 20 KB/s (0.16 Mbps).

Second example is streaming video from my home to remote device (either iPad, Roku, or other). Download speed for those devices are fine, however extreme buffering occurs and the quality is reduced to unwatchable. It's my upload speed that is causing the issue there (evidence in server logs that record upload speeds).

Called Cox to discuss. They said there was no issue.

Traceroute appears to consistently have an issue with the second hop:

traceroute to cox.com (68.99.123.161), 64 hops max, 72 byte packets
 1  192.168.1.1 (192.168.1.1)  0.489 ms  0.318 ms  0.285 ms
 2  * * *
 3  100.127.70.194 (100.127.70.194)  11.822 ms  9.257 ms  10.142 ms
 4  70.169.73.160 (70.169.73.160)  12.846 ms  11.927 ms  10.197 ms
 5  dukedsrj01-ae4.0.rd.at.cox.net (68.1.1.121)  54.192 ms  56.395 ms  54.553 ms
 6  68.1.15.234 (68.1.15.234)  55.710 ms  56.156 ms  56.023 ms
 7  68.99.123.4 (68.99.123.4)  56.259 ms  53.823 ms  55.880 ms
 8  ww2.cox.com (68.99.123.161)  54.441 ms  54.380 ms  57.058 ms

Modem signal levels seem fine.

@techknowhelp

I don't think that this is a backbone or a peering issue.  I use both FTP, testmy.net, and an HTTPS file transfer from my office (Cox Metro E) to my house 11 miles away.  Before Saturday of last week, I had no problems uploading at 20mbps.  Yesterday I was uploading a file and saw the slowdown.  Here's some tests today:

Testmy.net - San Jose server:

HTTPS transfer from my office to my house:

Right after Cox fixed this issue 3 weeks ago, these are the speeds that I was getting (and should be getting now but am not):

I ran a traceroute from my home to my office.  I can't exceed 6mbps upload to any destination including Cox's own network.

Traceroute has started…

traceroute to x.x.x.x (x.x.x.x), 64 hops max, 72 byte packets
1 10.0.0.1 (10.0.0.1) 0.517 ms 0.477 ms 0.390 ms
2 10.169.40.1 (10.169.40.1) 6.305 ms 7.403 ms 6.102 ms
3 elcncmtk06-gex030000.sd.sd.cox.net (68.6.11.230) 6.590 ms 6.815 ms 9.635 ms
4 elcnsysc01-tec-141.sd.sd.cox.net (68.6.8.58) 12.424 ms 8.003 ms 7.950 ms
5 escnhbrc01-gex0324.sd.sd.cox.net (68.6.8.63) 20.349 ms 9.096 ms 9.354 ms
6 wsip-70-167-162-50.sd.sd.cox.net (70.167.162.50) 8.099 ms 9.077 ms 7.953 ms
7 xxxxx.com (x.x.x.x) 10.013 ms 7.996 ms 7.934 ms

traceroute to ftp.powweb.com (65.254.250.100), 64 hops max, 72 byte packets
 1  192.168.1.1 (192.168.1.1)  0.514 ms  0.291 ms  0.282 ms
 2  * * *
 3  100.127.70.194 (100.127.70.194)  9.465 ms  9.865 ms  9.530 ms
 4  70.169.73.160 (70.169.73.160)  10.356 ms  9.846 ms  9.689 ms
 5  ae56.bar1.phoenix1.level3.net (4.31.188.61)  11.416 ms  10.945 ms  10.340 ms
 6  ae-3-80.edge1.losangeles9.level3.net (4.69.144.138)  21.202 ms  19.896 ms  20.247 ms
 7  ae-3-80.edge1.losangeles9.level3.net (4.69.144.138)  20.368 ms  18.656 ms  22.808 ms
 8  xo-level3.losangeles9.level3.net (4.68.110.206)  21.288 ms  33.587 ms  22.354 ms
 9  207.88.14.217.ptr.us.xo.net (207.88.14.217)  103.172 ms  103.759 ms  105.302 ms
10  te0-5-4-0.rar3.denver-co.us.xo.net (207.88.12.85)  102.147 ms  102.678 ms  105.162 ms
11  te-4-1-0.rar3.chicago-il.us.xo.net (207.88.12.21)  104.479 ms  102.344 ms  103.761 ms
12  ae0d0.mcr2.cambridge-ma.us.xo.net (216.156.0.30)  101.100 ms  102.702 ms  114.591 ms
13  ae1d0.mcr1.cambridge-ma.us.xo.net (216.156.1.13)  99.816 ms  99.609 ms  106.817 ms
14  216.55.5.134 (216.55.5.134)  87.823 ms  86.833 ms  88.672 ms
15  65-254-250-100.yourhostingaccount.com (65.254.250.100)  87.113 ms  86.760 ms  90.515 ms

traceroute to 8a9.faf.myftpupload.com (50.63.112.1), 64 hops max, 72 byte packets
 1  192.168.1.1 (192.168.1.1)  0.448 ms  0.301 ms  0.235 ms
 2  * * *
 3  100.127.70.194 (100.127.70.194)  9.388 ms  9.571 ms  9.501 ms
 4  70.169.73.160 (70.169.73.160)  11.481 ms  11.107 ms  22.910 ms
 5  langbprj02-ae6.0.rd.la.cox.net (68.1.5.139)  24.001 ms  24.342 ms  27.492 ms
 6  ip70-167-151-79.at.at.cox.net (70.167.151.79)  25.644 ms  24.880 ms  24.565 ms
 7  be39.trmc0215-01.ars.mgmt.phx3.gdg (184.168.0.73)  34.608 ms  36.146 ms  36.783 ms
 8  be39.trmc0215-01.ars.mgmt.phx3.gdg (184.168.0.73)  33.467 ms  32.557 ms  35.132 ms
 9  ip-97-74-255-129.ip.secureserver.net (97.74.255.129)  221.881 ms  33.418 ms  33.039 ms
10  p3nlhg764c1764.shr.prod.phx3.secureserver.net (50.63.112.1)  35.967 ms  34.470 ms  45.079 ms

Traceroute has started…

traceroute to 168.144.253.56 (168.144.253.56), 64 hops max, 72 byte packets
 1  192.168.1.1 (192.168.1.1)  0.475 ms  0.373 ms  0.253 ms
 2  * * *
 3  100.127.70.196 (100.127.70.196)  11.942 ms  8.885 ms  17.060 ms
 4  72.215.229.108 (72.215.229.108)  10.504 ms  10.288 ms  10.013 ms
 5  ae57.bar2.phoenix1.level3.net (4.28.82.53)  10.340 ms  11.338 ms  12.216 ms
 6  ae-3-80.edge1.losangeles6.level3.net (4.69.144.144)  19.007 ms  22.423 ms  21.761 ms
 7  ae-3-80.edge1.losangeles6.level3.net (4.69.144.144)  21.053 ms  19.856 ms  18.426 ms
 8  be3036.rcr21.lax04.atlas.cogentco.com (154.54.14.129)  20.260 ms  19.711 ms  21.843 ms
 9  be2017.ccr22.lax01.atlas.cogentco.com (154.54.0.238)  22.686 ms  20.257 ms  18.610 ms
10  be2066.ccr22.iah01.atlas.cogentco.com (154.54.7.53)  50.897 ms  47.629 ms  47.955 ms
11  be2443.ccr22.dfw01.atlas.cogentco.com (154.54.44.230)  48.137 ms  49.667 ms  47.597 ms
12  be2433.ccr22.mci01.atlas.cogentco.com (154.54.3.214)  57.780 ms  58.048 ms  57.129 ms
13  be2832.ccr42.ord01.atlas.cogentco.com (154.54.44.170)  68.104 ms  69.082 ms  69.307 ms
14  be2718.ccr22.cle04.atlas.cogentco.com (154.54.7.130)  83.279 ms  84.706 ms  86.960 ms
15  be2597.ccr22.yyz02.atlas.cogentco.com (154.54.31.90)  82.897 ms  83.490 ms  84.065 ms
16  te0-0-2-3.agr11.yyz02.atlas.cogentco.com (154.54.3.90)  81.145 ms  81.554 ms  81.482 ms
17  38.122.69.58 (38.122.69.58)  83.134 ms  82.918 ms  84.942 ms
18  168.144.253.56 (168.144.253.56)  84.155 ms  82.808 ms  82.783 ms