Still having problems myself just now with the Roku. I am a premium member, Cox Cable. I can watch the latest episodes of Naruto it seems without issue, but the minute I go to play something else it just stops working (ie. Rio, Saint Seya, Bombshells, etc.). ISP connection looks to be fine - I can stream over my PC and iPad just fine. I think I get better results using Skyfire from my phone than on the Roku at this point.

Anything I can help test with?

Speedtest.Net Results:
Download Speed: 16079 kbps (2009.9 KB/sec transfer rate)
Upload Speed: 6777 kbps (847.1 KB/sec transfer rate)

PingTest.Net Results:


NSLookup:

Server: google-public-dns-a.google.com
Address: 8.8.8.8

Name: crunchy.vo.llnwd.net
Addresses: 68.142.118.4
68.142.118.254


PING:

Pinging crunchy.vo.llnwd.net [68.142.118.4] with 32 bytes of data:
Reply from 68.142.118.4: bytes=32 time=53ms TTL=58
Reply from 68.142.118.4: bytes=32 time=60ms TTL=58
Reply from 68.142.118.4: bytes=32 time=50ms TTL=58
Reply from 68.142.118.4: bytes=32 time=47ms TTL=58

Ping statistics for 68.142.118.4:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 47ms, Maximum = 60ms, Average = 52ms


TRACERT:

Tracing route to crunchy.vo.llnwd.net [68.142.118.4]
over a maximum of 30 hops:

1 <1 ms 1 ms 1 ms 192.168.1.1
2 11 ms 21 ms 13 ms ip68-13-176-1.om.om.cox.net [68.13.176.1]
3 9 ms 12 ms 11 ms 68.13.8.245
4 9 ms 12 ms 12 ms 68.13.8.17
5 10 ms 11 ms 10 ms mtc1dsrj01-ae4.0.rd.om.cox.net [68.13.14.5]
6 25 ms 23 ms 26 ms wichdsrj01-so010.0.rd.ks.cox.net [68.1.1.189]
7 54 ms 48 ms 58 ms tge9-2.fr4.atl1.llnw.net [69.28.172.81]
8 45 ms 45 ms 47 ms cdn-68-142-118-4.atl1.llnw.net [68.142.118.4]

Trace complete.


Here again is the video I made of the exact issue: http://www.youtube.com/watch?v=iXFZLEZOI4c

(if anything the problem is worse now than back on Feb 14th when I made the video)

Also -
I am always using Wifi with the Roku - I've just now switched to a wired connection (I guess I really did find a use for that 25ft+ cable...) and experience the same issues. Really I didn't expect anything to change but figured it was worth a shot.

I'm still having the same problem with CR on Roku that others are having: videos not loading. They hang on "retrieving" forever, kick me out to the title screen. CR plays fine on my computer and iPhone.

I'm a premium member, AT&T. My results:

Speedtest.Net Results:
Download Speed: 1.66 Mbps
Upload Speed: 0.39 Mbps

Pingtest.net results:
Ping: 58 ms
Jitter: 2 ms

NSLookup:
DNS request timed out.
timeout was 2 seconds.
Server: UnKnown
Address: 192.168.0.1

Non-authoritative answer:
Name: crunchy.vo.llnwd.net
Addresses: 208.111.160.6
208.111.161.254

Ping:
Pinging crunchy.vo.llnwd.net [208.111.160.6] with 32 bytes of data:
Reply from 208.111.160.6: bytes=32 time=73ms TTL=59
Reply from 208.111.160.6: bytes=32 time=71ms TTL=59
Reply from 208.111.160.6: bytes=32 time=57ms TTL=59
Reply from 208.111.160.6: bytes=32 time=57ms TTL=59

Ping statistics for 208.111.160.6:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 57ms, Maximum = 73ms, Average = 64ms

Tracert:
Tracing route to crunchy.vo.llnwd.net [208.111.160.6]
over a maximum of 30 hops:

1 43 ms 43 ms 43 ms bras7-l0.mrdnct.sbcglobal.net [204.60.4.43]
2 42 ms 41 ms 41 ms dist1-vlan60.mrdnct.sbcglobal.net [66.159.184.226]
3 42 ms 43 ms 42 ms bb1-10g2-0.mrdnct.sbcglobal.net [151.164.92.147]
4 57 ms 57 ms 57 ms ex3-p0-1.eqabva.sbcglobal.net [151.164.171.38]
5 86 ms 57 ms 64 ms tge5-3.fr3.iad.llnw.net [69.28.157.1]
6 59 ms 57 ms 59 ms cdn-208-111-160-6.iad.llnw.net [208.111.160.6]

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

C:\Users\Travis>nslookup crunchy.vo.llnwd.net
Server: cns.chelmsfdrdc2.ma.boston.comcast.net
Address: 68.87.71.230

Non-authoritative answer:
Name: crunchy.vo.llnwd.net
Addresses: 208.111.128.7
208.111.128.6


C:\Users\Travis>ping crunchy.vo.llnwd.net

Pinging crunchy.vo.llnwd.net [208.111.128.6] with 32 bytes of data:
Reply from 208.111.128.6: bytes=32 time=48ms TTL=55
Reply from 208.111.128.6: bytes=32 time=51ms TTL=55
Reply from 208.111.128.6: bytes=32 time=49ms TTL=55
Reply from 208.111.128.6: bytes=32 time=47ms TTL=55

Ping statistics for 208.111.128.6:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 47ms, Maximum = 51ms, Average = 48ms

C:\Users\Travis>tracert crunchy.vo.llnwd.net

Tracing route to crunchy.vo.llnwd.net [208.111.128.6]
over a maximum of 30 hops:

1 <1 ms 1 ms <1 ms 192.168.1.1
2 7 ms 7 ms 8 ms 96.162.120.1
3 10 ms 8 ms * 68.85.160.13
4 11 ms 10 ms 11 ms be-71-ar01.needham.ma.boston.comcast.net [68.87.
147.241]
5 47 ms 46 ms 47 ms pos-2-1-0-0-cr01.newyork.ny.ibone.comcast.net [6
8.86.95.29]
6 48 ms 48 ms 47 ms pos-1-2-0-0-pe01.111eighthave.ny.ibone.comcast.n
et [68.86.86.74]
7 47 ms 47 ms 47 ms 66.208.228.182
8 51 ms 49 ms 127 ms tge1-2.fr3.lga.llnw.net [69.28.171.201]
9 48 ms 47 ms 46 ms cdn-208-111-128-6.lga.llnw.net [208.111.128.6]

Trace complete.

C:\Users\Travis>
[URL=http://www.pingtest.net]

[URL=http://www.speedtest.net]

Iowa Here same problem, its a shame cause I wanna watch this on the Big screen HD not my 17inch lappy HD screen.
http://www.speedtest.net/result/1223332102.png

Watching catalog Drama series ~ Jewel in the Palace, Painter on the Wind, Dong Yi, and Jumong ~ I keep getting kicked out the first time I try an episode, and then if I try again the next day, it often works. When it works, I'm not getting any buffering on the Roku ~ even though I sometimes buffer and get dropped down from four dots to two dots in quality at Netflix's player.

(Once, however, Jewel in the Palace episode 7, it froze the Roku completely a few minutes in and I had to restart the Roku.)

Perhaps it would be available at that time if I had the patience to try and get kicked out three or four or five times, but I don't.

The most plausible explanation for the special problems of Dramas on Roku is that they have their own specific encode, and combining the lower number of Crunchyroll users using Roku and the lower number of Crunchyroll users watching Drama's and the higher bitrate for liveaction over anime, the priority given to bringing the Roku encodes of Dramas somewhere in the pipeline between Crunchyroll and Limelight and Limelight and the end user is too low. Another point of evidence in favor of this is that I have similar trouble with deeper catalog titles like Glass Maiden and the original MS Gundam, but far less often with newly release simulcasts.

Wherever the excessive lag is located in the pipeline, either Crunchyroll or Limelight, they need to be made to understand how people watch Drama series. When one episode is streaming, there has to have an automated process in place to be sure to have the next episode of the same encoding actually available to stream starting from the end of the current episode stream ~ and that should remain at a low-latency level of the storage hierarchy for the following two weeks.

Combined with this, Crunchyroll might help if they are able to track which accounts stream across both web and Roku and signal Limelight that a particular Flash encode episode access may be followed by a Roku encode access of the same episode or the following one.

If absolutely necessary to launch the stream at all, pass off to the lower resolution encode while getting the higher resolution encode in the pipeline ~ a single buffer partway into one episode followed by better resolution would be tolerable, especially if it is not going to happen again in that series as long as you keep watching the next episode sometime within a two week window.

Combining all of that, it ought to be possible to get dramatically improved perceived performance.

Finally, if writing about the issue on blogs and social networks, email limelight at media@llnw.com to ask about their response regarding the performance problems of Crunchyroll streaming Dramas over their CDN.

I have been with CR for over a year and we really like the service. It would be so awesome if the constant timeouts would stop on the roku, I do like the recent interface improvements, but it would be nice if we could add/remove favorites while on the roku instead of having to log in via PC. The Roku experience, when working, is the best by far as it is high quality, uses HDMI TV connection, has a remote and does not prevent the use of the computer. If you guys get it working, it will be all we use.

We remain optimistic and appreciative here hoping this issue gets resolved soon.





>nslookup crunchy.vo.llnwd.net
Server: UnKnown
Address: 10.0.1.1

Non-authoritative answer:
Name: crunchy.vo.llnwd.net
Addresses: 68.142.118.4
68.142.118.254

>ping crunchy.vo.llnwd.net

Pinging crunchy.vo.llnwd.net [68.142.118.254] with 32 bytes of data:
Reply from 68.142.118.254: bytes=32 time=33ms TTL=56
Reply from 68.142.118.254: bytes=32 time=42ms TTL=56
Reply from 68.142.118.254: bytes=32 time=32ms TTL=56
Reply from 68.142.118.254: bytes=32 time=30ms TTL=56

Ping statistics for 68.142.118.254:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 30ms, Maximum = 42ms, Average = 34ms

>tracert crunchy.vo.llnwd.net

Tracing route to crunchy.vo.llnwd.net [68.142.118.254]
over a maximum of 30 hops:

1 1 ms 1 ms 2 ms HELLSING-NETWOR [10.0.1.1]
2 30 ms 11 ms 37 ms cpe-174-097-252-001.nc.res.rr.com [174.97.252.1]

3 12 ms 12 ms 25 ms ten13-0-0-230.rlghnca-rtr1.nc.rr.com [66.26.32.2
10]
4 13 ms 12 ms 12 ms ge-2-3-0.rlghncpop-rtr1.southeast.rr.com [24.93.
64.164]
5 19 ms 22 ms 18 ms 107.14.19.20
6 31 ms 21 ms 21 ms ae-2-0.pr0.dca10.tbone.rr.com [66.109.6.169]
7 26 ms 28 ms 21 ms tge15-3.fr3.iad.llnw.net [69.28.158.181]
8 26 ms 24 ms 25 ms ve5.fr4.iad.llnw.net [69.28.171.214]
9 34 ms 49 ms 32 ms tge1-2.fr4.atl1.llnw.net [69.28.172.33]
10 30 ms 35 ms 36 ms ve5.fr3.atl1.llnw.net [68.142.119.193]
11 30 ms * 31 ms cdn-68-142-118-254.atl1.llnw.net [68.142.118.254
]

Trace complete.

this is intresting dont kjnow what this is about
it went to the crunchy hosting in Atlanta then went to Dallas

C:\Documents and Settings\Brian>tracert crunchy.vo.llnwd.net

Tracing route to crunchy.vo.llnwd.net [68.142.122.70]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.1.1
2 7 ms 6 ms 7 ms 10.52.128.1
3 7 ms 7 ms 7 ms ten0-3-orld59-ser2.noc.bhn.net [72.31.194.136]
4 7 ms 8 ms 7 ms 71-44-60-74.net.bhntampa.com [71.44.60.74]
5 16 ms 15 ms 13 ms 97.69.194.146
6 13 ms 14 ms 15 ms ae1s0-orld71-cbr2.noc.bhn.net [72.31.194.2]
7 22 ms 23 ms 22 ms ae-3-10.cr1.atl20.tbone.rr.com [66.109.6.104]
8 21 ms 23 ms 22 ms ae-1-0.pr0.atl20.tbone.rr.com [66.109.6.177]
9 130 ms 22 ms 23 ms 107.14.18.10
10 24 ms 25 ms 22 ms ve5.fr3.atl1.llnw.net [68.142.119.193]
11 41 ms 45 ms 49 ms tge16-1.fr3.dal.llnw.net [68.142.125.17]
12 41 ms 41 ms * cdn-68-142-122-70.dal.llnw.net [68.142.122.70]
13 42 ms 41 ms 60 ms cdn-68-142-122-70.dal.llnw.net [68.142.122.70]

Trace complete.

or have some of the servers been moved?

it stopped working at about 8:35 est

i had gotten about 4 episodes in before that


hmm seems like it went back

C:\Documents and Settings\Brian>tracert crunchy.vo.llnwd.net

Tracing route to crunchy.vo.llnwd.net [68.142.118.4]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.1.1
2 7 ms 5 ms 6 ms 10.52.128.1
3 6 ms 7 ms 7 ms ten0-3-orld59-ser2.noc.bhn.net [72.31.194.136]
4 9 ms 7 ms 7 ms 71-44-60-74.net.bhntampa.com [71.44.60.74]
5 13 ms 13 ms 13 ms 97.69.194.144
6 12 ms 13 ms 13 ms ae1s0-orld71-cbr2.noc.bhn.net [72.31.194.2]
7 21 ms 21 ms 33 ms ae-4-0.cr1.atl20.tbone.rr.com [66.109.10.14]
8 23 ms 22 ms 22 ms ae-1-0.pr0.atl20.tbone.rr.com [66.109.6.177]
9 30 ms 24 ms 25 ms 107.14.18.10
10 23 ms 22 ms 21 ms cdn-68-142-118-4.atl1.llnw.net [68.142.118.4]

Trace complete.

still not working though

agila61's comments make s sense to me because i have noticed a clear pattern of when the dramas will not load on Roku. It almost like clockwork. Early Saturday adn Sunday mornings when most people are not watching, they load without hesitation. Same goes for late afternoon until about prime time ont he west coast during the week, after which nothing loads.

This appears to be a capacity issue - either at CR or the provider. If this is anything like when my former employer was providing internet capacity to 3rd parties, it may be a contractual issue. Sometimes the 3rd party seriously underestimates the capacity it needs. Of course it may also be the provider not providing what they should be in terms of speed and capacity.

All I really know is that Netflix is getting a lot of requests from everyone I know for Kdramas, because CR by Roku really isn't reliable enough.

I'm having serious problems getting dramas to load. At first it was mainly a problem on the Roku--now they're not downloading to the computer, either.


http://www.pingtest.net/result/37930718.png

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

Same problem, Roku won't retrieve video and kicks me back to the CR episode screen. Account linked.

SpeedTest Results:
[URL=http://www.speedtest.net]



Microsoft Windows [Version 6.0.6002]
Copyright (c) 2006 Microsoft Corporation. All rights reserved.

C:\Users\Stacey>nslookup crunchy.vo.llnwd.net
Server: dns-cac-lb-01.rr.com
Address: 209.18.47.61

Non-authoritative answer:
Name: crunchy.vo.llnwd.net
Addresses: 208.111.168.6
208.111.168.7


C:\Users\Stacey>ping crunchy.vo.llnwd.net

Pinging crunchy.vo.llnwd.net [208.111.160.6] with 32 bytes of data:
Reply from 208.111.160.6: bytes=32 time=26ms TTL=56
Reply from 208.111.160.6: bytes=32 time=25ms TTL=56
Reply from 208.111.160.6: bytes=32 time=26ms TTL=56
Reply from 208.111.160.6: bytes=32 time=31ms TTL=56

Ping statistics for 208.111.160.6:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 25ms, Maximum = 31ms, Average = 27ms

C:\Users\Stacey>tracert crunchy.vo.llnwd.net

Tracing route to crunchy.vo.llnwd.net [208.111.160.6]
over a maximum of 30 hops:

1 3 ms 1 ms 1 ms 192.168.1.1
2 11 ms 14 ms 10 ms cpe-71-72-120-1.insight.res.rr.com [71.72.120.1]

3 11 ms 11 ms 9 ms gig2-13.instoh1-rtr01.insight.rr.com [65.24.192.
153]
4 11 ms 11 ms 11 ms network-065-024-192-042.insight.rr.com [65.24.19
2.42]
5 17 ms 18 ms 16 ms tge2-0-0.clevoh1-rtr0.mwrtn.rr.com [65.25.137.24
9]
6 25 ms 23 ms 56 ms ae-3-0.cr0.dca20.tbone.rr.com [66.109.6.70]
7 24 ms 25 ms 26 ms ae-1-0.pr0.dca10.tbone.rr.com [66.109.6.165]
8 37 ms 25 ms 25 ms tge15-3.fr3.iad.llnw.net [69.28.158.181]
9 26 ms 25 ms 34 ms cdn-208-111-160-6.iad.llnw.net [208.111.160.6]

Trace complete.

C:\Users\Stacey>

I've watched "Feed the Pig" over a half-dozen times while waiting for my Roku to retrieve a drama, without ever getting to watch the drama. There seems to be plenty of capacity for the ads, but not enough for the shows. I've waited two weeks, and there's been no improvement. Making me watch ads repeatedly and then not allowing me to watch the show is not going encouraging me to sign up for a premium account (which I suspect won't solve the problem). What's the name of your service provider so I know to avoid them in the future?

I am having the SAME problem with Roku as all the previous posters. Why has there been no response to this?

Ha Ha! Same here! The first couple of times they were funny, but now they are annoying. I'm with you. I won't sign up for the premium service until this issue is resolved. I haven't been able to watch much of anything without this issue. We finished watching the entire Dong Yi series and are now hooked on the comedy High Kick. But most often, we end up watching it on my iPad because of the Roku problems.

Its not an ISP at fault, it is either Crunchyroll or the CDN they use, Limelight. Netflix seems to be able to get good service out of Limelight, but maybe that's because they are a much bigger client.

And since I got the premium one year membership during the after Christmas sale, I can tell you what happens for premium members: nothing. Instead of watching an ad over and over again, nothing at all loads, and then it timeouts.

Maybe its worse for the back catalog titles ~ the ones I am watching, since I only really watch historical dramas ~ but it so, then Crunchyroll should upload all their completed series to Netflix. At least on Netflix I can watch them when I want to, not when Crunchyroll's CDN decides to deliver them to me.

I was thinking it couldn't be capacity, because I'm always having trouble 11pm or 12midnight ~ but I'm on Eastern time, so that's 8pm and 9pm Pacific Time.

I think load management is screwed up somewhere ~ because of the lower average number of Roku hits, they are getting put on the back burned by somebody. Whether its Crunchyroll or Limelight does not matter much to me. I assume that Crunchy has a high bandwidth pipe to Limelight, but maybe there is an average level of service commitment which runs across the anime and dramas and flash and Roku, and Limelight is managing their service to that average level of service, with dramas on Roku ending up on the short end of the stick.

I still reckon its worthwhile testing moving Roku encode dramas to a different CDN and see if they can give better Quality Of Service ~ let Limelight know that they have to compete on QOS on every channel, and not just "on average" across all channels.