dslreports logo
site
 
    All Forums Hot Topics Gallery
spc

spacer




how-to block ads


Search Topic:
uniqs
13542
share rss forum feed


Draco

join:2006-06-18
Slate Hill, NY

Twitch.tv Issues (Chime in!)

Figured I would plop this post here and see how you may fare on watching streams on twitch.tv after 4:00 PM (EST) to around midnight or 1 AM EST. (Yes you reading this post! Even if you don't have TWC!)

Here's an example:
»www.twitch.tv/draco_/c/2139496
(TWC Hudson Valley NY, 30/5... when can we have 10 Mbps up?)

FYI, I can cast (read: upload) just fine to Twitch in upwards to 4 Mbps regularly without much issue for my 1080p cast. So the upstream route is absolutely fine to their ingest servers. Watching streams is a whole 'nother matter and that route appears completely broken. Sometimes the throughput appears lacking, but other times it sharply fluctuates and causes *any* bitrate pushed by that caster to stall completely. Very similar to YouTube videos as of late that are stalling out from downloading or just having varied speeds.

Also, just putting this forward: Traceroutes are pointless since they do not reach the destination. This has been going on for months now. Opening a VPN to Japan (therefore changing the route) appears to resolve the issue. I've heard even TWC in Texas and Ohio have had similar ongoing problems. And yes, this has been posted multiple times on help.twitch.tv as well.

Either way, just wanted to open some specific discussion to any fellow viewers on TWC having similar problems. Chime on in! Let us know if you're experiencing the same! Where you're watching from and when? I would love for TWC to chime in and help or work with Twitch or the route to them, but I sadly don't see that happening unless more people speak up on this. So this is my attempt to spark a flame to this issue.



kilrathi
Premium
join:2005-04-22
Rockaway Park, NY

I stream a lot using xsplit and to twitch, I find that virginia 2nd server works the best.



Draco

join:2006-06-18
Slate Hill, NY

said by kilrathi:

I stream a lot using xsplit and to twitch, I find that virginia 2nd server works the best.

Well yes, that ingest server was best for a long time, but as of recently the NY one must have had some improvements. For the past 4-5 months now it has been best at any bitrate.

But what has your experience been with watching streams at night?

iansltx

join:2007-02-19
Austin, TX
kudos:2
Reviews:
·Time Warner Cable
·Verizon Online DSL
·Comcast

At times the LoL LCS stream gets jerky at 720p+ on my 50M connection, though less than it has been in the past. Still an issue at peak times though, to the point that I'll SSH tunnel to SoftLayer to fix the issue (and the issue usually gets fixed when I do that).



ZinZio

@rr.com
reply to Draco

TWC Columbus Ohio
Between 6pm - 1am (Peak hours)
30d/5u speed tests

I have the same prob. Video lags every 2-3 secs. I have called TWC many times and they tell me its not their problem. I don't know what to do!


coolcat120

join:2007-04-13
reply to Draco

Yep same here. I can stream my self no problem but watching any stream on 720p and sometimes 480 as well, it lags. I also have 30/5 and its very frustrating. I am from Erie PA and its happening to me right now watching the Giantbomb TNT.



Draco

join:2006-06-18
Slate Hill, NY

1 edit

So I went and sent a tweet on over to @TWC_Help on Twitter. This morning I got a reply regarding providing a trace to them when the issue is occurring:

quote:
@draco355 Our apologies for the impairment. If you'd like to run trace routes when this is occurring, we can check for any latency within our network. Please DM your account information as well. ^BP
While it's a first step, lets see where they go with this.

So, I'm going to kindly ask for everyone's help in the matter.

At around 9 PM tonight on 4/13 (or if you read this late, 4/14), please run an mtr or a traceroute to: live.twitch.tv and paste your results here in a code block. (You can stop at the hops that don't respond and give asterisks.)

The main issue with this traceroute will be the fact that it will not reach the destination to provide valuable data about the hops between level3 and twitch.tv, which is where I suspect the problem is. Maybe the return route from twitch's CDN have a different path? Either way, please paste your routes here if you witness the issue after 5PM. I would like to reply to them with a good collection of info. Whether they dismiss it as not their problem is up to them. Only engineers on TWC's network can really help in this matter, whether it's their network or level3 or... well, they (TWC's RNOC or GNOC) have the contacts and the power to do *something* for us I hope.

Example (4PM):
C:\>tracert live.twitch.tv
 
Tracing route to live.twitch.tv [199.9.253.203]
over a maximum of 30 hops:
 
  1    <1 ms    <1 ms    <1 ms  gw.lalilulelo.lan [192.168.0.1]
  2    40 ms    22 ms    23 ms  cpe-69-206-168-1.hvc.res.rr.com [69.206.168.1]
  3     7 ms     9 ms     9 ms  gig-0-3-lbrtnywdn-ubr2.hvc.rr.com [24.164.161.105]
  4    18 ms    15 ms    15 ms  24-164-160-16.hvc.rr.com [24.164.160.16]
  5    18 ms    38 ms    14 ms  bun6-nycmnytg-rtr002.nyc.rr.com [24.29.148.250]
  6    53 ms    47 ms    56 ms  107.14.19.24
  7    13 ms    12 ms    14 ms  ae-1-0.pr0.nyc30.tbone.rr.com [66.109.6.161]
  8    14 ms    13 ms    15 ms  ae9.edge3.Newark1.Level3.net [4.68.63.21]
  9    26 ms    19 ms    18 ms  ae-32-52.ebr2.Newark1.Level3.net [4.69.156.62]
 10    20 ms    18 ms    19 ms  ae-4-4.ebr2.Washington1.Level3.net [4.69.132.101]
 11    19 ms    17 ms    18 ms  ae-72-72.csw2.Washington1.Level3.net [4.69.134.150]
 12    21 ms    18 ms    18 ms  ae-2-70.edge2.Washington4.Level3.net [4.69.149.80]
 13     *        *        *     Request timed out.
 14  ^C
 
-------------

Also as an added note, I did a tcptraceroute which went a little farther. Whether or not it helps in this situation on the other hand... (well at least it exposes "JUSTIN.TV.edge2.Washington4.Level3.net" and I kind of wonder if that's a saturation point on part of level3 or not.)

draco@zeus:~$ sudo tcptraceroute live.twitch.tv
traceroute to live.twitch.tv (199.9.250.246), 30 hops max, 60 byte packets
 1  gw.lalilulelo.lan (192.168.0.1)  0.440 ms  0.623 ms  0.815 ms
 2  cpe-69-206-168-1.hvc.res.rr.com (69.206.168.1)  20.982 ms  20.905 ms  20.674 ms
 3  gig-0-3-lbrtnywdn-ubr2.hvc.rr.com (24.164.161.105)  11.006 ms  10.954 ms  10.893 ms
 4  24-164-160-16.hvc.rr.com (24.164.160.16)  20.273 ms  20.148 ms  20.381 ms
 5  bun6-nycmnytg-rtr002.nyc.rr.com (24.29.148.250)  20.906 ms  20.841 ms  20.778 ms
 6  ae-4-0.cr0.nyc30.tbone.rr.com (66.109.6.78)  19.968 ms  17.508 ms  23.009 ms
 7  ae-1-0.pr0.nyc30.tbone.rr.com (66.109.6.161)  17.117 ms  12.313 ms  17.341 ms
 8  ae9.edge3.Newark1.Level3.net (4.68.63.21)  16.062 ms  14.349 ms *
 9  ae-32-52.ebr2.Newark1.Level3.net (4.69.156.62)  19.409 ms  21.312 ms  16.940 ms
10  ae-4-4.ebr2.Washington1.Level3.net (4.69.132.101)  17.363 ms  16.926 ms  20.167 ms
11  ae-72-72.csw2.Washington1.Level3.net (4.69.134.150)  20.126 ms ae-92-92.csw4.Washington1.Level3.net (4.69.134.158)  17.348 ms  17.374 ms
12  ae-4-90.edge2.Washington4.Level3.net (4.69.149.208)  15.057 ms ae-2-70.edge2.Washington4.Level3.net (4.69.149.80)  17.116 ms ae-4-90.edge2.Washington4.Level3.net (4.69.149.208)  13.616 ms
13  JUSTIN.TV.edge2.Washington4.Level3.net (4.53.114.178)  13.767 ms  15.257 ms  17.345 ms
14  * * *
15  * * *
16  live3.justin.tv (199.9.250.246)  91.202 ms  92.308 ms  92.405 ms
 


mackey
Premium
join:2007-08-20
kudos:12

If you have root on a linux box you can see those missing hops:
(6 pm EDT, 3 pm PDT, from a Comcast connection though):

traceroute -T live.twitch.tv
traceroute to live.twitch.tv (199.9.250.245), 30 hops max, 40 byte packets
 1  174.54.160.1 (174.54.160.1)  15.476 ms  16.290 ms  27.537 ms
 2  te-0-0-0-3-sur01.montville.pa.pitt.comcast.net (68.85.43.9)  17.140 ms  17.169 ms  17.163 ms
 3  te-0-12-0-3-ar03.lowerpaxton.pa.pitt.comcast.net (69.139.194.65)  18.759 ms  19.625 ms  19.640 ms
 4  be-2-ar03.pittsburgh.pa.pitt.comcast.net (68.85.75.125)  25.875 ms  26.769 ms  26.705 ms
 5  he-4-14-0-0-cr01.newyork.ny.ibone.comcast.net (68.86.94.185)  33.363 ms  34.312 ms  34.406 ms
 6  xe-7-2-3.edge1.NewYork2.Level3.net (4.71.186.49)  31.813 ms  58.428 ms  63.973 ms
 7  vlan51.ebr1.NewYork2.Level3.net (4.69.138.222)  64.943 ms  64.991 ms  64.736 ms
 8  4.69.132.89 (4.69.132.89)  64.840 ms  64.698 ms  64.550 ms
 9  ae-62-62.csw1.Washington1.Level3.net (4.69.134.146)  64.210 ms  64.270 ms ae-82-82.csw3.Washington1.Level3.net (4.69.134.154)  63.920 ms
10  ae-3-80.edge2.Washington4.Level3.net (4.69.149.144)  31.230 ms ae-4-90.edge2.Washington4.Level3.net (4.69.149.208)  29.907 ms  28.336 ms
11  JUSTIN.TV.edge2.Washington4.Level3.net (4.53.114.178)  65.725 ms  57.856 ms  62.632 ms
12  live2.justin.tv (199.9.250.245)  167.097 ms  167.063 ms  166.922 ms
 

Edit: heh, you edited and posted the TCP thing while I was making this...
/M

coolcat120

join:2007-04-13
reply to Draco

Copyright (c) 2009 Microsoft Corporation.  All rights reserved.
 
C:\>tracert live.twitch.tv
 
Tracing route to live.twitch.tv [199.9.250.245]
over a maximum of 30 hops:
 
  1     8 ms     7 ms     6 ms  192.168.1.1
  2    78 ms    49 ms    69 ms  cpe-76-189-160-1.neo.res.rr.com [76.189.160.1]
  3    54 ms    15 ms    16 ms  tge1-4.hbckpa1-swt402.neo.rr.com [24.164.115.49]
 
  4    19 ms    52 ms    22 ms  tge1-3.mcdnoh1-swt402.neo.rr.com [24.164.117.25]
 
  5    40 ms    21 ms    20 ms  tge2-1.clvhoh1-rtr1.neo.rr.com [24.164.117.125]
 
  6    20 ms    21 ms    40 ms  tge2-1.clvhoh1-rtr1.neo.rr.com [24.164.117.125]
 
  7    26 ms    23 ms    23 ms  tge0-9-0-1.clevohek-ccr03.midwest.rr.com [24.164
.117.128]
  8    28 ms    23 ms    55 ms  network-065-029-001-032.midwest.rr.com [65.29.1.
32]
  9    67 ms    47 ms    63 ms  ae-3-0.cr0.dca20.tbone.rr.com [66.109.6.70]
 10    61 ms    47 ms    48 ms  ae-1-0.pr0.dca10.tbone.rr.com [66.109.6.165]
 11    72 ms    95 ms    79 ms  ash-bb1-link.telia.net [80.239.132.177]
 12     *        *        *     Request timed out.
 13     *     justintv-ic-152597-ash-bb1.c.telia.net [213.248.73.98]  reports: D
estination net unreachable.
 
Trace complete.
 

TebTeb

join:2009-01-28
Columbus, OH
Reviews:
·Time Warner Cable
reply to Draco

From my TWC 50Mbps connection:
Tracing route to live.twitch.tv [199.9.249.151]
over a maximum of 30 hops:

1 1 ms 1 ms 1 ms 192.168.0.1
2 * * * Request timed out.
3 16 ms 15 ms 15 ms ae0-1258.cr02.clmkohpe.midohio.rr.com [184.59.24
3.125]
4 12 ms 15 ms 15 ms network-065-029-001-034.midwest.rr.com [65.29.1.
34]
5 18 ms 23 ms 23 ms ae-4-0.cr0.chi30.tbone.rr.com [66.109.6.68]
6 19 ms 17 ms 17 ms ae-1-0.pr0.chi10.tbone.rr.com [66.109.6.155]
7 39 ms 83 ms 34 ms ae18.edge2.Chicago2.Level3.net [4.68.111.33]
8 34 ms 32 ms 36 ms vl-3502-ve-116.ebr1.Chicago2.Level3.net [4.69.15
8.6]
9 35 ms 32 ms 39 ms ae-1-51.edge3.Chicago3.Level3.net [4.69.138.136]

10 * * * Request timed out.
11 * * * Request timed out.
12 * * * Request timed out.
13 * ^C

VPN to a server hosted in London UK:
Tracing route to live.twitch.tv [199.9.250.247]
over a maximum of 30 hops:

1 112 ms 113 ms 120 ms 10.32.0.1
2 114 ms 114 ms 114 ms 154.51.136.62
3 114 ms 113 ms 114 ms te0-5-0-2.mpd22.lon13.atlas.cogentco.com [149.11
.45.69]
4 114 ms 113 ms 115 ms te0-0-0-1.ccr22.lon01.atlas.cogentco.com [154.54
.57.158]
5 115 ms 117 ms 116 ms level3.lon01.atlas.cogentco.com [130.117.15.246]

6 117 ms 115 ms 114 ms vl-3502-ve-116.csw1.London1.Level3.net [4.69.166
.133]
7 114 ms 114 ms 112 ms ae-1-51.edge5.London1.Level3.net [4.69.139.75]
8 * * * Request timed out.
9 * * * Request timed out.
10 ^C


dude34221

join:2002-06-13
Athens, OH

2 edits
reply to Draco

have you tried this if you use chrome? »help.twitch.tv/customer/portal/a···h-player

have you looked over this? its about TWC specifically.
»help.twitch.tv/customer/portal/q···led-isp-

if no avail with above, have you gotten a new public IP from your ISP? Sometimes this will yield different routing. If you have same ip/static cable internet, it can be changed on demand by changing MAC address. if you need additional help let me know

trace from twc Athens, OH. SE Ohio. don't use youtube. 30/5 plan, always get full speeds elsewhere. signal levels within 3 to 5db of spec/perfect. 2:30am est

C:\Documents and Settings\New Cpu>tracert live.twitch.tv

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

1 10 ms 12 ms 11 ms 10.163.64.1
2 18 ms 24 ms 23 ms ae0-1753.cr02.clmkohpe.midohio.rr.com [184.59.24
3.103]
3 35 ms 39 ms 33 ms network-065-029-001-034.midwest.rr.com [65.29.1.
34]
4 34 ms 51 ms 39 ms ae-9-0.cr0.chi30.tbone.rr.com [107.14.19.16]
5 43 ms 31 ms 30 ms ae-1-0.pr0.chi10.tbone.rr.com [66.109.6.155]
6 31 ms 31 ms 29 ms ae18.edge2.Chicago2.Level3.net [4.68.111.33]
7 40 ms 41 ms 36 ms vl-3603-ve-227.ebr2.Chicago2.Level3.net [4.69.15
8.58]
8 35 ms 30 ms 39 ms ae-2-52.edge3.Chicago3.Level3.net [4.69.138.168]

9 * * * Request timed out.
10 * * * Request timed out.


dude34221

join:2002-06-13
Athens, OH
reply to Draco

EDIT: »www.proxfree.com/youtube-proxy.php looks like it could have a great chance to work



Jpaso32

@rr.com
reply to Draco

Hey draco, we talked in cosmos twitch chat and you sent me this link. Any progress on this video stuttering problem?


elusus

join:2009-06-29
reply to Draco

I'm glad I'm not the only one experiencing this problem. I did find a temporary workaround tho. I connect to my vpn thats in the colocrossing buffalo datacenter and I can watch twitch.tv lag free most of the time. Looks like they have better peering to the twitch servers than TWC.

We have to get TWC to fix this! I went ahead and tweeted @TWC_Help as well.

Here's my tracert.
1 1 ms 1 ms 1 ms 192.168.0.1
2 31 ms 37 ms 19 ms cpe-72-229-44-1.nyc.res.rr.com [72.229.44.1]
3 11 ms 8 ms 10 ms gig-0-3-0-26-nycmnyw-rtr2.nyc.rr.com [24.168.138.53]
4 12 ms 15 ms 15 ms bun100.nycmnytg-rtr001.nyc.rr.com [184.152.112.149]
5 14 ms 15 ms 24 ms bun6-nycmnytg-rtr002.nyc.rr.com [24.29.148.250]
6 15 ms 15 ms 14 ms 107.14.19.24
7 17 ms 11 ms 11 ms 107.14.19.153
8 * 9 ms 11 ms xe-4-2-0.edge4.frankfurt1.level3.net [4.68.63.121]
9 16 ms 16 ms 14 ms ae-32-52.ebr2.Newark1.Level3.net [4.69.156.62]
10 17 ms 13 ms 16 ms ae-4-4.ebr2.Washington1.Level3.net [4.69.132.101]
11 17 ms 13 ms 17 ms ae-82-82.csw3.Washington1.Level3.net [4.69.134.154]
12 13 ms 16 ms 17 ms ae-3-80.edge2.Washington4.Level3.net [4.69.149.144]
13 * * * Request timed out.
14 * * * Request timed out.
15 * * * Request timed out.



Draco

join:2006-06-18
Slate Hill, NY
reply to Jpaso32

said by Jpaso32 :

Hey draco, we talked in cosmos twitch chat and you sent me this link. Any progress on this video stuttering problem?

No luck yet on any front. I made a post on help.twitch.tv on Sunday, but it hasn't gone past their moderation and I don't expect it to. I also haven't heard back from TWC (or their twitter) on anything.

As for the rest of you guys replying on this thread, thanks for throwing down your traceroutes... and keep it coming! I'm going to keep this thread alive as long as I can. And will be pestering TWC as well as Twitch continuously... as should you, referencing this thread, of course.

Also, in regards to your suggestions "dude343321", I appreciate the effort but what you provided has nothing that will help resolve the problem at hand permanently (or at all).


Draco

join:2006-06-18
Slate Hill, NY
reply to Draco

6 PM hits, Youtube was previously loading many 1080p videos fine, and now throughput plummets to nothing with large stalls and makes every video unwatchable.

Twitch videos buffering non-stop... every single one.

Coincidence? I'm really confused and frustrated at this point.



Taiya

@insightbb.com

Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.

C:\Users\Kristine>tracert live.twitch.tv

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

1 5 ms 2 ms 4 ms 192.168.1.1
2 * * * Request timed out.
3 38 ms 31 ms 56 ms 74-128-16-77.dhcp.insightbb.com [74.128.16.77]
4 10 ms 23 ms 31 ms tge0-10-0-2.lsvqkydb-ccr01.mwrtn.rr.com [65.29.2
5.112]
5 28 ms 32 ms 30 ms network-065-189-140-166.mwrtn.rr.com [65.189.140
.166]
6 32 ms 39 ms 39 ms ae-3-0.cr0.dca20.tbone.rr.com [66.109.6.70]
7 30 ms 33 ms 35 ms so-1-1-1.a0.alb75.tbone.rr.com [66.109.1.49]
8 107 ms 78 ms 84 ms ash-bb1-link.telia.net [80.239.167.237]
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 * justintv-ic-152597-ash-bb1.c.telia.net [213.248.73.98] reports: D
estination net unreachable.

Trace complete.

C:\Users\Kristine>



Taiya

@insightbb.com
reply to Draco

Yep, same for me. Completely unwatchable on any resolution and unable to stream from mid-day until about 1am EST on a 20/1 connection. Absolutely ridiculous.


coolcat120

join:2007-04-13

1 edit
reply to Draco

Copyright (c) 2009 Microsoft Corporation.  All rights reserved.
 
C:\>tracert live.twitch.tv
 
Tracing route to live.twitch.tv [199.9.253.82]
over a maximum of 30 hops:
 
  1     4 ms     1 ms     1 ms  192.168.1.1
  2    95 ms    27 ms    29 ms  cpe-76-189-160-1.neo.res.rr.com [76.189.160.1]
  3    11 ms    31 ms    28 ms  tge1-4.hbckpa1-swt402.neo.rr.com [24.164.115.49]
 
  4    19 ms    19 ms    15 ms  tge1-1.mcdnoh1-swt402.neo.rr.com [24.164.115.71]
 
  5    15 ms    13 ms    53 ms  tge1-8.mcdnoh1-swt401.neo.rr.com [24.164.117.117
]
  6    38 ms    17 ms    18 ms  tge1-7.kentoh1-swt401.neo.rr.com [24.164.117.181
]
  7    23 ms    55 ms    39 ms  tge0-9-0-0.pltsohae-ccr03.midwest.rr.com [24.164
.117.183]
  8    41 ms    31 ms    23 ms  network-065-029-001-028.midwest.rr.com [65.29.1.
28]
  9    36 ms    71 ms    39 ms  ae-9-0.cr0.chi30.tbone.rr.com [107.14.19.16]
 10    87 ms     *       56 ms  ae-2-0.a0.buf00.tbone.rr.com [66.109.1.42]
 11     *        *        *     Request timed out.
 12    43 ms    43 ms    43 ms  vl-3602-ve-226.ebr2.Chicago2.Level3.net [4.69.15
8.54]
 13    59 ms    47 ms    55 ms  ae-2-52.edge3.Chicago3.Level3.net [4.69.138.168]
 
 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.
 

EDIT: I got a tweet back after letting them know of this thread and they said:

"None of the traceroutes in that thread are showing problems on the TWC backbone. Our techs are still investigating. ^PS"


Zorn

@rr.com

Mine has the same problem so its not just you coolcat same ip in chicago and then it times out



Zinzio

@rr.com
reply to Draco

Well I have been working with both Twitch and TW cable and it doesn't appear a resolution is in site..

This is what Twitch has replied to me with..
--
Jason M replied:
Hi,

The issue is the bandwidth between TWC and Level3 (our CDN). Basically, this is a fixed bandwidth path. Thus, as demand grows during peak hours, your fighting for resources with everyone else. Level3 serves more than us, thus the fight for these resources is beyond Twitch's control. We will continue to try to get the best service (and rates) to allow more of our customers to have lag-free experiences.

FYI: Turbo will not improve this issue.
Regards,

Jason M.
Twitch Customer Support
--

So basically until Level3 stops throttling TWC, the problems will remain. I had a friend that lives down the street that (who has Wide Open West as an ISP) do a tracert to twitch.tv and he is not being routed through Level3, he also doesn't experience any lag.

I have spoken again with TWC and threatened to cancel my service, they escalated the issue to a national support team but i have yet to hear any resolution back (pending now for about 2 weeks.) My best advice is to get another ISP if you can.



Smith6612
Premium,MVM
join:2008-02-01
North Tonawanda, NY
kudos:24
Reviews:
·Verizon Online DSL
·Frontier Communi..

said by Zinzio :

So basically until Level3 stops throttling TWC, the problems will remain. I had a friend that lives down the street that (who has Wide Open West as an ISP) do a tracert to twitch.tv and he is not being routed through Level3, he also doesn't experience any lag.

I have spoken again with TWC and threatened to cancel my service, they escalated the issue to a national support team but i have yet to hear any resolution back (pending now for about 2 weeks.) My best advice is to get another ISP if you can.

Level3 isn't throttling Time Warner. As the tech stated, TWC customers are fighting for the pipe alongside others, or the problem is perhaps with the pipes from/to Time Warner to/from Level3 being overloaded and you have Time Warner customers from specific regions fighting for the data. As much as Level3's network tends to be shoddy in some parts of the world, they do carry a lot of traffic in perspective as a Tier 1 provider. So many folks use them.


kywirelessgu
Premium
join:2004-01-25
Nicholasville, KY
reply to Draco

I'm a former insight customer (now TWC) and I've been having this problem for several months now.

Twitch is unwatchable at all resolutions.

I wish more of the tournaments used multiple streaming companies. I don't have as many problems with Azubu or youtube live streams.
--
the answers to all lifes questions... »www.google.com


networkman98

join:2003-05-21
Advance, NC
reply to Smith6612

Yes, Smith6612 is correct here. If there is saturation on a link, there is not much that can be done with it except for backbone teams to get together and troubleshoot the issue. I've seen specific problems with TWC customers using Level 3 DNS servers and there being packet loss on a link between Level 3 and TWC. There is nothing that TWC can do directly because it's on Level 3's end. Do a traceroute or pingplotter and you will typically see no issue with TWC's network all the way out it's own backbone.

Many ISPs (not including AT&T or Verizon), if not all, get their access to the Internet backbone through Level 3 as they are a Tier 1 provider. They merged with Global Crossing which was the other largest Tier 1 provider outside of Level 3.



Draco

join:2006-06-18
Slate Hill, NY

1 edit
reply to Draco

...and what needs to be done is TWC's NOC opening a ticket with Level3/GBLX to track said issues regarding congestion on that route that are effecting usage. Only they can do it, not non-customers of Level3.

The question is if TWC even cares to do so?

I will add that all this weekend I've been in NJ on a VZ FIOS line and streaming just fine as per the norm. I've done bitrates from 2 to 8 Mbps just fine. Though here's a kicker: All weekend after 3-4PM it has been horrible to watch not only my own stream over 2 Mbps, but others as well. So this is behaving just the same on a 75/25 connection on another provider. The route from here goes through alter.net and telia.net where it then times out (like normal).

Very bizarre.



DrDrew
That others may surf
Premium
join:2009-01-28
SoCal
kudos:15

There's a long standing conflict between L3 and ISPs about this traffic..

The common arguements are: L3 says it's transit and the ISP pays for bandwidth. The ISPs say it's CDN traffic and L3 should pay for bandwidth.

»publicknowledge.org/blog/netflix···-level-3
--
Two is one, one is none. If it's important, have a back up... 99.999% availability just isn't enough sometimes.



Sieger

@voxility.net

I was having the same issue at NY. I was able to fix it by using one of the free VPN services("http://www.vpnbook.com/"). Now i can watch at 1080+ no problem when i could barely watch 360p before



Jeb

@rr.com
reply to Draco

Re: Twitch.tv Issues

Same problem here. used to watch everything on twitch in 1080p no problem. now I cant watch any VOD whatsoever and streams lag horribly. no answers, just solidifying the fact that this is an enormous and horribly real problem.


piyokos8

join:2010-03-20
reply to Draco

Re: Twitch.tv Issues (Chime in!)

Get a VPN service with a NY local server like StrongVPN. Costs a bit of money but I can't watch streams on Twitch.tv without it. Also resolved some occasional streaming issues with Youtube.



Heroxoot

@24.100.102.x
reply to Draco

Ever since TWC bought insight communication in feb 2013 I have had nothing but lag on twitch. I have tried every fix I can find. Blocking different IPs and such. Nothing works. Nothing helps. I even upgraded to 50/5 from 15/1 because TWC told me I had a lack of bandwidth with 6 people on my internet. Was never a problem before they bought insight.