3027 cr points
Send Message:  
 Offline
|
beardfist wrote:
Could you try running those tests again with the correct address: v1.lln.crunchyroll.com
Sure, I was just going by the instructions on the pages, those instructions should be updated.
Spoiler Alert! Click to show or hide
nslookup v1.lln.crunchyroll.com
Server: www.asusnetwork.net
Address: 10.1.1.1
Non-authoritative answer:
Name: crunchy.vo.llnwd.net
Address: 69.164.22.253
Aliases: v1.lln.crunchyroll.com
ping -t v1.lln.crunchyroll.com
Pinging crunchy.vo.llnwd.net [69.164.22.253] with 32 bytes of data:
Reply from 69.164.22.253: bytes=32 time=24ms TTL=58
Reply from 69.164.22.253: bytes=32 time=23ms TTL=58
Reply from 69.164.22.253: bytes=32 time=22ms TTL=58
Reply from 69.164.22.253: bytes=32 time=36ms TTL=58
Reply from 69.164.22.253: bytes=32 time=30ms TTL=58
Reply from 69.164.22.253: bytes=32 time=67ms TTL=58
Reply from 69.164.22.253: bytes=32 time=23ms TTL=58
Request timed out.
Reply from 69.164.22.253: bytes=32 time=306ms TTL=58
Reply from 69.164.22.253: bytes=32 time=324ms TTL=58
Request timed out.
Reply from 69.164.22.253: bytes=32 time=24ms TTL=58
Reply from 69.164.22.253: bytes=32 time=40ms TTL=58
Reply from 69.164.22.253: bytes=32 time=30ms TTL=58
Reply from 69.164.22.253: bytes=32 time=28ms TTL=58
Reply from 69.164.22.253: bytes=32 time=23ms TTL=58
Reply from 69.164.22.253: bytes=32 time=23ms TTL=58
Reply from 69.164.22.253: bytes=32 time=23ms TTL=58
Reply from 69.164.22.253: bytes=32 time=22ms TTL=58
Reply from 69.164.22.253: bytes=32 time=31ms TTL=58
Reply from 69.164.22.253: bytes=32 time=43ms TTL=58
Reply from 69.164.22.253: bytes=32 time=25ms TTL=58
Reply from 69.164.22.253: bytes=32 time=23ms TTL=58
Reply from 69.164.22.253: bytes=32 time=25ms TTL=58
Reply from 69.164.22.253: bytes=32 time=22ms TTL=58
Reply from 69.164.22.253: bytes=32 time=23ms TTL=58
Reply from 69.164.22.253: bytes=32 time=23ms TTL=58
Reply from 69.164.22.253: bytes=32 time=24ms TTL=58
Reply from 69.164.22.253: bytes=32 time=25ms TTL=58
Reply from 69.164.22.253: bytes=32 time=26ms TTL=58
Reply from 69.164.22.253: bytes=32 time=25ms TTL=58
Reply from 69.164.22.253: bytes=32 time=29ms TTL=58
Reply from 69.164.22.253: bytes=32 time=68ms TTL=58
Reply from 69.164.22.253: bytes=32 time=23ms TTL=58
Reply from 69.164.22.253: bytes=32 time=22ms TTL=58
Reply from 69.164.22.253: bytes=32 time=418ms TTL=58
Reply from 69.164.22.253: bytes=32 time=22ms TTL=58
Reply from 69.164.22.253: bytes=32 time=46ms TTL=58
Reply from 69.164.22.253: bytes=32 time=33ms TTL=58
Reply from 69.164.22.253: bytes=32 time=30ms TTL=58
Reply from 69.164.22.253: bytes=32 time=31ms TTL=58
Reply from 69.164.22.253: bytes=32 time=38ms TTL=58
Reply from 69.164.22.253: bytes=32 time=26ms TTL=58
Ping statistics for 69.164.22.253:
Packets: Sent = 43, Received = 41, Lost = 2 (4% loss),
Approximate round trip times in milli-seconds:
Minimum = 22ms, Maximum = 418ms, Average = 52ms
tracert v1.lln.crunchyroll.com
Tracing route to crunchy.vo.llnwd.net [69.164.22.253]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms www.asusnetwork.net [10.1.1.1]
2 * * * Request timed out.
3 15 ms 15 ms 15 ms rd1so-ge12-0-0-21.cg.shawcable.net [64.59.129.242]
4 41 ms 36 ms 34 ms 66.163.74.193
5 38 ms 23 ms 22 ms ri1bb-fe0-1-0.vc.shawcable.net [66.163.69.38]
6 31 ms 24 ms 25 ms ve7.fr3.yvr2.llnw.net [68.142.125.49]
7 26 ms 24 ms 23 ms cdn-69-164-22-253.yvr.llnw.net [69.164.22.253]
Trace complete.
Looks like some latency and packet loss to Vancouver.
|
3027 cr points
Send Message:
Offline
|
Looks like the latency and dropped packets are from the final hop in that traceroute, I did pinging of all the things along the stream and they were all fine, except for the last one.
Spoiler Alert! Click to show or hide
ping -t 66.163.69.38
Pinging 66.163.69.38 with 32 bytes of data:
Reply from 66.163.69.38: bytes=32 time=27ms TTL=60
Reply from 66.163.69.38: bytes=32 time=52ms TTL=60
Reply from 66.163.69.38: bytes=32 time=52ms TTL=60
Reply from 66.163.69.38: bytes=32 time=25ms TTL=60
Reply from 66.163.69.38: bytes=32 time=34ms TTL=60
Reply from 66.163.69.38: bytes=32 time=32ms TTL=60
Reply from 66.163.69.38: bytes=32 time=57ms TTL=60
Reply from 66.163.69.38: bytes=32 time=55ms TTL=60
Reply from 66.163.69.38: bytes=32 time=31ms TTL=60
Reply from 66.163.69.38: bytes=32 time=28ms TTL=60
Reply from 66.163.69.38: bytes=32 time=28ms TTL=60
Reply from 66.163.69.38: bytes=32 time=28ms TTL=60
Reply from 66.163.69.38: bytes=32 time=46ms TTL=60
Reply from 66.163.69.38: bytes=32 time=43ms TTL=60
Reply from 66.163.69.38: bytes=32 time=42ms TTL=60
Reply from 66.163.69.38: bytes=32 time=52ms TTL=60
Reply from 66.163.69.38: bytes=32 time=25ms TTL=60
Reply from 66.163.69.38: bytes=32 time=25ms TTL=60
Reply from 66.163.69.38: bytes=32 time=48ms TTL=60
Reply from 66.163.69.38: bytes=32 time=23ms TTL=60
Reply from 66.163.69.38: bytes=32 time=24ms TTL=60
Reply from 66.163.69.38: bytes=32 time=45ms TTL=60
Reply from 66.163.69.38: bytes=32 time=42ms TTL=60
Reply from 66.163.69.38: bytes=32 time=33ms TTL=60
Reply from 66.163.69.38: bytes=32 time=32ms TTL=60
Reply from 66.163.69.38: bytes=32 time=56ms TTL=60
Reply from 66.163.69.38: bytes=32 time=54ms TTL=60
Reply from 66.163.69.38: bytes=32 time=28ms TTL=60
Reply from 66.163.69.38: bytes=32 time=51ms TTL=60
Reply from 66.163.69.38: bytes=32 time=35ms TTL=60
Reply from 66.163.69.38: bytes=32 time=35ms TTL=60
Reply from 66.163.69.38: bytes=32 time=65ms TTL=60
Reply from 66.163.69.38: bytes=32 time=25ms TTL=60
Ping statistics for 66.163.69.38:
Packets: Sent = 33, Received = 33, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 23ms, Maximum = 65ms, Average = 38ms
Control-C
^C
ping -t 68.142.125.49
Pinging 68.142.125.49 with 32 bytes of data:
Reply from 68.142.125.49: bytes=32 time=42ms TTL=59
Reply from 68.142.125.49: bytes=32 time=41ms TTL=59
Reply from 68.142.125.49: bytes=32 time=40ms TTL=59
Reply from 68.142.125.49: bytes=32 time=40ms TTL=59
Reply from 68.142.125.49: bytes=32 time=46ms TTL=59
Reply from 68.142.125.49: bytes=32 time=39ms TTL=59
Reply from 68.142.125.49: bytes=32 time=37ms TTL=59
Reply from 68.142.125.49: bytes=32 time=22ms TTL=59
Reply from 68.142.125.49: bytes=32 time=38ms TTL=59
Reply from 68.142.125.49: bytes=32 time=43ms TTL=59
Reply from 68.142.125.49: bytes=32 time=57ms TTL=59
Reply from 68.142.125.49: bytes=32 time=29ms TTL=59
Reply from 68.142.125.49: bytes=32 time=28ms TTL=59
Reply from 68.142.125.49: bytes=32 time=26ms TTL=59
Reply from 68.142.125.49: bytes=32 time=25ms TTL=59
Reply from 68.142.125.49: bytes=32 time=26ms TTL=59
Reply from 68.142.125.49: bytes=32 time=48ms TTL=59
Reply from 68.142.125.49: bytes=32 time=34ms TTL=59
Reply from 68.142.125.49: bytes=32 time=29ms TTL=59
Reply from 68.142.125.49: bytes=32 time=25ms TTL=59
Reply from 68.142.125.49: bytes=32 time=23ms TTL=59
Reply from 68.142.125.49: bytes=32 time=28ms TTL=59
Reply from 68.142.125.49: bytes=32 time=41ms TTL=59
Reply from 68.142.125.49: bytes=32 time=78ms TTL=59
Reply from 68.142.125.49: bytes=32 time=24ms TTL=59
Reply from 68.142.125.49: bytes=32 time=22ms TTL=59
Reply from 68.142.125.49: bytes=32 time=38ms TTL=59
Reply from 68.142.125.49: bytes=32 time=43ms TTL=59
Reply from 68.142.125.49: bytes=32 time=34ms TTL=59
Reply from 68.142.125.49: bytes=32 time=34ms TTL=59
Ping statistics for 68.142.125.49:
Packets: Sent = 30, Received = 30, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 22ms, Maximum = 78ms, Average = 36ms
Control-C
^C
ping -t 69.164.22.253
Pinging 69.164.22.253 with 32 bytes of data:
Reply from 69.164.22.253: bytes=32 time=83ms TTL=58
Reply from 69.164.22.253: bytes=32 time=24ms TTL=58
Reply from 69.164.22.253: bytes=32 time=29ms TTL=58
Reply from 69.164.22.253: bytes=32 time=35ms TTL=58
Reply from 69.164.22.253: bytes=32 time=25ms TTL=58
Reply from 69.164.22.253: bytes=32 time=23ms TTL=58
Reply from 69.164.22.253: bytes=32 time=24ms TTL=58
Reply from 69.164.22.253: bytes=32 time=1546ms TTL=58
Reply from 69.164.22.253: bytes=32 time=917ms TTL=58
Reply from 69.164.22.253: bytes=32 time=297ms TTL=58
Reply from 69.164.22.253: bytes=32 time=420ms TTL=58
Reply from 69.164.22.253: bytes=32 time=292ms TTL=58
Reply from 69.164.22.253: bytes=32 time=293ms TTL=58
Reply from 69.164.22.253: bytes=32 time=297ms TTL=58
Reply from 69.164.22.253: bytes=32 time=299ms TTL=58
Reply from 69.164.22.253: bytes=32 time=294ms TTL=58
Reply from 69.164.22.253: bytes=32 time=295ms TTL=58
Reply from 69.164.22.253: bytes=32 time=296ms TTL=58
Reply from 69.164.22.253: bytes=32 time=298ms TTL=58
Reply from 69.164.22.253: bytes=32 time=353ms TTL=58
Reply from 69.164.22.253: bytes=32 time=306ms TTL=58
Reply from 69.164.22.253: bytes=32 time=330ms TTL=58
Reply from 69.164.22.253: bytes=32 time=362ms TTL=58
Request timed out.
Reply from 69.164.22.253: bytes=32 time=352ms TTL=58
Reply from 69.164.22.253: bytes=32 time=301ms TTL=58
Reply from 69.164.22.253: bytes=32 time=297ms TTL=58
Reply from 69.164.22.253: bytes=32 time=310ms TTL=58
Reply from 69.164.22.253: bytes=32 time=399ms TTL=58
Reply from 69.164.22.253: bytes=32 time=314ms TTL=58
Reply from 69.164.22.253: bytes=32 time=294ms TTL=58
Reply from 69.164.22.253: bytes=32 time=292ms TTL=58
Reply from 69.164.22.253: bytes=32 time=296ms TTL=58
Reply from 69.164.22.253: bytes=32 time=134ms TTL=58
Reply from 69.164.22.253: bytes=32 time=45ms TTL=58
Reply from 69.164.22.253: bytes=32 time=48ms TTL=58
Reply from 69.164.22.253: bytes=32 time=41ms TTL=58
Reply from 69.164.22.253: bytes=32 time=82ms TTL=58
Reply from 69.164.22.253: bytes=32 time=30ms TTL=58
Reply from 69.164.22.253: bytes=32 time=32ms TTL=58
Reply from 69.164.22.253: bytes=32 time=25ms TTL=58
Reply from 69.164.22.253: bytes=32 time=27ms TTL=58
Ping statistics for 69.164.22.253:
Packets: Sent = 42, Received = 41, Lost = 1 (2% loss),
Approximate round trip times in milli-seconds:
Minimum = 23ms, Maximum = 1546ms, Average = 255ms
Control-C
I also ran some parallel tests where I continuously pinged the second last server and the final server. The second last one was constant during the times while the last one had packet loss. It was a very common pattern on pinging the last one for ping times to jump up to 1 second, (then some packet loss sometimes), then sit up and 300ms for a while, then drop back down to 25ms range.
Pinging the last server ( v1.lln.crunchyroll.com) has super high jitter then, swinging up and down from 25 to 300ms with the odd 1+ second and lost packet thrown in for good measure.
Ping statistics for 69.164.22.253:
Packets: Sent = 331, Received = 327, Lost = 4 (1% loss),
Approximate round trip times in milli-seconds:
Minimum = 22ms, Maximum = 1658ms, Average = 97ms
Control-C |
|
Customer Support Manager
20692 cr points
Send Message: 32 / M / San Francisco
Offline
|
Spoiler Alert! Click to show or hide stay_dead wrote:
I'm experiencing intermittent but consistent video stuttering. It doesn't matter which show, and it doesn't matter if it's 1080P or 720P, usually 5-10 times per show it will stutter and pause, I usually have to click a few seconds earlier in the video and it is fine for another few minutes.
The requested info:
Computer Info:
Windows 7 - 64 bit
Latest Firefox and Chrome
Flash: You have version 11,5,502,146 installed
Processor Type: i7-2600K @ 3.4GHz
Graphics Card Type. Nvidia GTX670
Amount or RAM. 16GB
Amount of free space on your C: or OS partition: 70GB
nslookup:
nslookup cp150757.edgefcs.net
Server: www.asusnetwork.net
Address: 10.1.1.1
Non-authoritative answer:
Name: a156.vi5g5.akafms.net
Addresses: 24.244.3.95
24.244.3.87
24.244.3.93
24.244.3.94
24.244.3.92
24.244.3.79
24.244.3.85
Aliases: cp150757.edgefcs.net
a156.v1507570.c150757.b3.vi5.akamaistream.net
ping:
ping cp150757.edgefcs.net
Pinging a156.vi5g5.akafms.net [24.244.3.95] with 32 bytes of data:
Reply from 24.244.3.95: bytes=32 time=12ms TTL=125
Reply from 24.244.3.95: bytes=32 time=9ms TTL=125
Reply from 24.244.3.95: bytes=32 time=9ms TTL=125
Reply from 24.244.3.95: bytes=32 time=9ms TTL=125
Ping statistics for 24.244.3.95:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 9ms, Maximum = 12ms, Average = 9ms
tracert (I always get request timed out for the first hop onto my ISP):
tracert cp150757.edgefcs.net
Tracing route to a156.vi5g5.akafms.net [24.244.3.95]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms www.asusnetwork.net [10.1.1.1]
2 * * * Request timed out.
3 13 ms 15 ms 15 ms rd1so-ge12-0-0-21.cg.shawcable.net [64.59.129.242]
4 8 ms 11 ms 9 ms 24.244.3.95
Trace complete.
Speedtest and Pings:
I don't think I could get any closer of a server to hit, though I have tried using various DNS providers to try and hit different servers with varying success (but never elimination of the problem).
If I could actually just get the IP addresses of the servers with the lowest load or most bandwidth I could edit my hosts file myself rather than randomly changing my dns...
Out of curiosity. What platform is this on?
|
3027 cr points
Send Message:
Offline
|
Windows 7 - 64 bit
Latest Firefox and Chrome
Flash: You have version 11,5,502,146 installed
Processor Type: i7-2600K @ 3.4GHz
Graphics Card Type. Nvidia GTX670
Amount or RAM. 16GB
Amount of free space on your C: or OS partition: 70GB
http://www.crunchyroll.com/forumtopic-627053/help-with-video-playback-problems?fpid=42347037
|
|
Customer Support Manager
20692 cr points
Send Message: 32 / M / San Francisco
Offline
|
Spoiler Alert! Click to show or hide stay_dead wrote:
Windows 7 - 64 bit
Latest Firefox and Chrome
Flash: You have version 11,5,502,146 installed
Processor Type: i7-2600K @ 3.4GHz
Graphics Card Type. Nvidia GTX670
Amount or RAM. 16GB
Amount of free space on your C: or OS partition: 70GB
http://www.crunchyroll.com/forumtopic-627053/help-with-video-playback-problems?fpid=42347037[/ quote]
Hurrr, totally overpassed that in looking at results.
If you're having issues on your PC then the initial test results were the correct ones to run.
I'm not getting the location that you're streaming from just that it's in 'Canada'.
Everything looks like it should be fine. Can you please explain exactly what issues you're encountering when watching in HD?
|
3027 cr points
Send Message:
Offline
|
Basically every few minutes it'll stutter and then pause. If I scroll back a few seconds it'll usually go fine again for a while, then do it again.
Feels exactly like on youtube or similar where it shows the amount it's buffered, and if the connection is slow and your playback reaches as far as its buffered.
I've actually been able to watch a few things over the past couple of days with no issues, so it might be during busy times only.
EDIT: Ah spoke too soon, back again tonight.
|
34182 cr points
Send Message:
Offline
|
This may help some people experiencing stuttering. For me, the problem only occurs for shows that are available in 1080p, and any shows that aren't don't lag at all. For shows that are more than about four months old and available in 1080p, I haven't found any way to fix the problem. For shows newer than that, switching to 720p completely stops any stuttering from happening. The quality is identical as well, since CR just up-scales the 710p.
So basically, you still can't watch anything older than four months and younger than 14, but you can watch newer stuff by switching to 720p.
|
48024 cr points
Send Message: 25 / M / Tempe, Arizona, USA
Offline
|
I've been experiencing the same issues other people have been talking about in these recent pages, but it's not limited to just old content but new as well, I get stuttering and freezing every minute or less. This is also a recent problem for me as CR has been working great for me as long as I can remember, they must be having a recent issues with the servers.
|
51239 cr points
Send Message: 52 / M / U.S.A.
Offline
|
Just a reminder to everyone:
It is helpful if you state what country or region you are in when reporting problems.
This is especially true if your profile doesn't list this information. Streaming issues can often be restricted to a specific region, so identifying where you are helps call out any such patterns to others that are reading this.
For larger countries, noting the specific state, province, or area of the country would also be helpful.
|
6048 cr points
Send Message: 24
Offline
|
I've had this problem a couple of times and recently it's been particularly active. What'll happen is that I'll be watching a video and about halfway through the video will suddenly stop and skip to the next episode like it does at the very end of the video. Thing is, I'm not done watching that video when it skips.
Location: USA southeast.
|
16013 cr points
Send Message: 27 / M
Offline
|
The Crunchyroll PS3 app won't play the newly released episodes. The loading circle appears but then gets stuck briefly before staying on the same screen. I can play all previous episodes, just not ones that were released the past couple days. I can play those episodes on the website, so this is strictly a PS3 app issue. Let me know if I need to post this in a different place.
Location: USA northeast.
Thank you.
|
3027 cr points
Send Message:
Offline
|
Bjaker wrote:
I'm not getting the location that you're streaming from just that it's in 'Canada'.
Everything looks like it should be fine. Can you please explain exactly what issues you're encountering when watching in HD?
I'm in Calgary Alberta Canada and according to iplocation.net the IP 24.244.3.95 (which is what cp150757.edgefcs.net resolves to) which is a 3 hour drive from Calgary (though who knows if that's actually right, but I'm one hop away from that server after my local ISP gateway so it can't get any better than that.
Are there a list of other edge IP addresses, you guys seem to suggest messing around with DNS servers to try and get different content servers, it'd be easier if I just had a list of IPs and I can try different ones myself rather than randomly trying different DNS servers.
Happening again tonight trying to watch Shin Sekai Yori. I'm paying for a service that I don't feel I get any value out of if I have to go down to 480P just to watch.
|
16017 cr points
Send Message: 25 / M
Offline
|
Currently located in USA, Texas
Download speed: 30 Mbps
Upload speed: 4.27 Mbps
Intel (R) Core (TM) i5-2500 CPU
3.30 GHz
RAM: 8.00 GB
64-bit
Everything seems to be running on my end but lately I've been having issues watching videos. They'll start out horribly, pause, stutter, etc.
|
3027 cr points
Send Message:
Offline
|
I can't even watch 30 seconds straight tonight.
|
21 cr points
Send Message: 37 / M
Offline
|
Can anyone tell me why I haven't been able to play any CR video (at all) for 3 days on one of my two ROKU? THe other ROKU can sometimes play something. Not often. Even though I have a 20mb download speed and both ROKU can play anything from other streaming sites.
CR staff seems to half troubleshoot but never finishes the job. Maybe they been spending too much time with panasonic rather then keeping what they have running.
Sadly, unless the issue is resolved I'll be forced to turn CR into every authority I can for false advertising. Utterly horrible service and streaming consistency.
Oh...and I trouble shot with ROKU as well...nothing wrong on their end and the same vids do play on my PC and Iphone
|
Post Reply
Help with Video Playback Problems 
