Slower than Normal Uploads to Twitch.tv?

Never had any issues watching streams on Twitch. Im avid follower of Day[9] . Also, do you play warframe? Name rings a bell. 

First, what kind of modem do you have? And when you say you get 20Mbps, is that upload or download?

I don't have any issues with watching streams.  I'm just having problems streaming myself.

I have a Cisco DPC3010 modem that I received from Cox.  Using the speed test tool through Cox, I get my advertised speeds of 130 Mbps down and 20 Mbps up.

And I actually played Warframe for a little bit.  Not anymore, however.

Also, back in October of last year (about the time the upgrades rolled out), these were my results from Speedtest.

Now days, I can barely break 5 Mbps upload to either test location.

Don't feel like a throughput issue. Maybe latency? Try Pingtest.net.

Also try a trace to twitch. See here for instructions. Post results.

Here are my Pingtest results for a server in Dallas, TX.

Here are my Pingtest results for a server in Bixby, OK.

Here are the results from the Twitch.tv latency checker.

Here are the results from the trace route to the Twitch servers.

Well, these are odd Speedtest results, now that I can actually perform the tests since I'm home.  Three different results from three different servers located in Dallas, TX.

http://www.speedtest.net/result/3329677900.png

http://www.speedtest.net/result/3329679282.png

http://www.speedtest.net/result/3329680626.png

The data all looks good. 

Anyone have any ideas? 

Additionally, here are some pathpings to the Twitch servers:

http://i.imgur.com/3herwH5.png

http://i.imgur.com/g8y7voN.png

Those pathpings look pretty normal too. Unless there servers were 100% down at that time, thats probably ICMP deprioritization, which is normal at the last hop of Coxs.

One thing I have noticed on the forums is lots of people asking abour the PS4 and the included twitch streaming. Did your problem happen around the time the PS4 got popular? I wonder if its a issue with their servers, or atleast their ISP/Peer or something.

Maybe try this? If this works, atleast we know the problem, low throughput. Also maybe try this? Mostly used for download problems, but the VPN should work both ways, so if throughput is good, but routing is bad, VPN should show us.

Also, have you checked your settings with your streamer, are you using Xplit?

I'm having the same problem. I have Cox ultimate tier and streamed at 720p 3500kbps at 60fps with no problems whatsoever from December, 2013 until the weekend of Feb 21st.. I have had 4 technicians out here since then. They have replaced, wiring on the outside of the house, checked all the internal wiring, replaced the node on the street (which I'm the only house connected to) and gave me a loaner modem to try out.

I went from having an awesome stream to not being able to stream through an evening.

I'm starting to think Cox is throttling my upload to twitch servers or something...

I am going insane not being able to figure out what the problem is. Most speed tests return everything fine, but twitch streaming has taken a dump 3 weeks ago.

I don't think Cox purposely throttles connections, I just don't think they have the systems in place. Instead I think alot of issues is caused by technical problems, like congestion, between Cox and what ever peer or ISP twitch uses. Thats why I asked for tracert, but it didn't show any lantency, which is usually a sign of congestion.

Im curious if OP tried any of my ideas with a VPN. If we know a path that works, and one that doesn't from the same location, it would rule alot of things out and help to isolate.

Im having the same problem.  Im paying for premier even with 2 people playing league oflegends and me streaming 720p(since alot of viewers cant load 1080 fast enough and i dont want to buy a capture card so i can record 2 sets and send out 1080 and 720)  im supposed to be getting 50/10 and im getting 30 down and 3 up. I drop frames like crazy I cant stream.  A tech came out and told me my modem was to old which is B.S. because I had a cox business package before i moved and i was getting 160 down and 80 up on the same modem and now i cant even get FOUR.

Watching steams from twitch is one thing, but I'm also starting to have problems uploading. I used to be able to broadcast at 1920x1200@3500 no problem, lately I'm getting 2Mbit up and 30Mbit down from speedtest.net so I cant even broadcast decently anymore. If twitch had an upload option to upload pre-recorded files that's one thing (they don't) but live broadcasting is another and I can't upload to youtube anymore cause of their hatred towards gamers lately. You can't tell me it's my network as I have shielded cat 6 I made myself (to spec I might add) and I can upload files from my main PC to my own home servers at 85MByte+/sec (gigabit network with custom mtu), when I used to broadcast just fine a month or 2 ago and now dropped to abysmal speeds though no configuration changes on my side.

ingestion server info from (https://support.xsplit.com/forum/viewtopic.php?t=1597)

I stream to the Los Angeles server (closest to me) and here is my Tracert

PS C:\Windows\System32\WindowsPowerShell\v1.0> tracert 199.9.255.86

Tracing route to media47.justin.tv [199.9.255.86]
over a maximum of 30 hops:

1 1 ms 1 ms <1 ms Router [172.24.96.1]
2 * * * Request timed out.
3 12 ms 9 ms 10 ms 172.21.1.154
4 15 ms 16 ms 15 ms 72.215.229.20
5 14 ms * 12 ms 70.169.75.157
6 43 ms 25 ms 27 ms langbbrj01-ae2.rd.la.cox.net [68.1.1.14]
7 * * * Request timed out.
8 * * * Request timed out.
9 * * * Request timed out.
10 * * * Request timed out.
11 * * * Request timed out.
12 * * * Request timed out.
13 * * * Request timed out.
14 * * * Request timed out.
15 * * * Request timed out.
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 * * * Request timed out.
25 * * * Request timed out.
26 * * * Request timed out.
27 * * * Request timed out.
28 * * * Request timed out.
29 * * * Request timed out.
30 * * * Request timed out.

Trace complete.

Having the same problems since last week. I have no issues watching streams, or doing anything else.

However, trying to stream myself, I am dropping between 30-90% of frames, and that's even with dropping stream quality to less than 900 kb/s. Twitch is telling me that I'm not sending at a constant bit rate (from dashboard, refreshing after stream start to get quality report from Twitch.)

Every tracert I run to any Twitch ingest server times out (best so far is to London - which doesn't time out until after it's on the L3 network in London).

Common last hops before constant time outs are 68.1.2.109 and fed1dsrj02-xe010.1.rd.sd.cox.net - from there all my packets drop into the ether. My computer has more than enough power to stream at a higher bitrate than I have upload. My realistic upload speed (from testmy.net; a little more realistic than Okla's SpeedTest and not "gamed" by internal testing to Cox internal network servers) shows about 2 Mbps. Before this started, I had no problems streaming 1080p at 30 fps at 1.5 Mbps rate - now I can't, and I've had connection issues with dropping during streams. (Nothing else, just the connection to the Twitch ingest servers.) JTV Ping shows good connections. I'm in the green for about half a minute before frames start dropping.

Here's tracert results to live-dfw.twitch.tv (normally a good ingest). Twitch status shows all ingest servers up and running well. There have been no equipment changes, no configuration changes (except for me dropping bit rate to try and get something out), and the wiring from the street drop to my ethernet port have not changed.

Tracing route to live-dfw.twitch.tv [199.9.254.25]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  Me
  2    17 ms     7 ms     7 ms  My Cable Modem
  3     9 ms     9 ms     7 ms  ip68-1-11-14.at.at.cox.net [68.1.11.14]
  4    52 ms    66 ms    52 ms  fed1dsrj02-xe010.1.rd.sd.cox.net [68.1.0.
  5     *        *        *     Request timed out.
  6     *        *        *     Request timed out.
  7     *        *        *     Request timed out.
  8     *        *        *     Request timed out.
  9     *        *        *     Request timed out.
 10     *        *        *     Request timed out.
 11     *        *        *     Request timed out.
 12     *        *        *     Request timed out.
 13     *        *        *     Request timed out.
 14     *        *        *     Request timed out.
 15     *        *        *     Request timed out.
 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     *        *        *     Request timed out.
 25     *        *        *     Request timed out.
 26     *        *        *     Request timed out.
 27     *        *        *     Request timed out.
 28     *        *        *     Request timed out.
 29     *        *        *     Request timed out.
 30     *        *        *     Request timed out.

Trace complete.

Look, I don't expect great things in Pensacola besides the Blue Angels, but this is failing to meet even my low expectations for cable ISP connections.

Further line of inquiry - I have a Motorola Surfboard SB6121 modem. According do the stats page, "Firmware Build Time: Mar 12 2013 17:48:19" - this would be the same day that my issues began. (I also did not do anything to get updated Firmware.) This is a DOCSIS 3.0 modem - I only mention that because looking around suggests there's been some issues with modems getting the wrong configuration.

D'oh. That would be Mar 12 last year. Although it did start around that time this year, the firmware is probably not involved.