We've been conversing lately in the CES thread about differences in download speeds versus our ISP's account limits. Many of us have accounts that offer 75-250 Mbps. Many of those are getting download speeds from K which are a substantial portion of, if not maxing out, our account settings, at least the guys who have accounts up to about 100 Mbps. Guys who have 75 Meg accounts are getting at least mid-high 60s from K. I am supposed to be getting 105/10, and every speed test I've done in the last couple of days from this computer, from a variety of test servers across the country, has validated that ability, but I am seeing K download rates on a per movie average of no better than about 37, and as low as 16.
So, I think it would be good to start a thread dedicated to the variability of downloads that some (me for sure, but there have to be others) are seeing when we get content from The Store. I have been on the phone with K a couple of times today, and with my ISP's escalated support a couple of times, and we've made some early progress.
I am sending in logs for a couple of trace routes that I did today, but in order to validate my theory, I need some comparative data, so I have a request for the class.
Everyone, whether you get downloads at nearly 100 Mbps or 20 Mbps, who can do a trace route would be immensely useful. All you have to do is:
If you have a PC:
1. Open the command prompt of your (Windows) computer
2. At the prompt, type in tracert www.kaleidescape.com and hit enter.
Let the results happen. It will stop after 30 hops.
If you have a Mac:
Take the following steps to run a traceroute on Macintosh OS X:
Double-click the Macintosh hard drive.
Double-click the Applications folder.
Double-click the Utilities folder.
Double-click the Network Utility icon to open the Network Utility window.
Click the Traceroute tab
Then repeat (on either machine) with tracert store.kaleidescape.com and hit enter.
Let the results happen.
Easy way for the next step is to capture the screen for both results so we can see the hops. If you'd rather not have ALL the hops, back to you, showing, just please send me the ones with names in the suffix, like comcast.net, or att.net or cogentco.com, etc. Leave out the first one or two if you're "security conscious".
The last one, I suspect, will end with something like pnap.net, with an address of 66.151.144.92 or very similar, which would indicate we are getting very close to the K servers. Those are hidden behind firewalls, so we can't ping them directly.
E-mail the results to me please.
My goal is to work out from the K server vicinity back towards the endpoints, and compare data rates on the client end with the routes that the data take. Once the data leaves K, it all goes out some common paths, and then begins to diverge at some point. Guys like House72 (Raj) and Poindexter who live outside the front door of the K facility will provide some useful data, and guys who live in places like Atlanta and Miami can offer some excellent data. The more commonality that is discovered, the easier it will be to whittle down to the actual culprit.
This is kind of a treasure hunt, and unfortunately you guys are not going to directly receive any treasure (I am sorry for that!) but it would be a magnanimous gesture, and would be helping your fellow man to achieve a better (Kaleidescape) life. If it helps even one other person resolve this critical, life-altering issue, it will be worth it.
So, I think it would be good to start a thread dedicated to the variability of downloads that some (me for sure, but there have to be others) are seeing when we get content from The Store. I have been on the phone with K a couple of times today, and with my ISP's escalated support a couple of times, and we've made some early progress.
I am sending in logs for a couple of trace routes that I did today, but in order to validate my theory, I need some comparative data, so I have a request for the class.
Everyone, whether you get downloads at nearly 100 Mbps or 20 Mbps, who can do a trace route would be immensely useful. All you have to do is:
If you have a PC:
1. Open the command prompt of your (Windows) computer
2. At the prompt, type in tracert www.kaleidescape.com and hit enter.
Let the results happen. It will stop after 30 hops.
If you have a Mac:
Take the following steps to run a traceroute on Macintosh OS X:
Double-click the Macintosh hard drive.
Double-click the Applications folder.
Double-click the Utilities folder.
Double-click the Network Utility icon to open the Network Utility window.
Click the Traceroute tab
Then repeat (on either machine) with tracert store.kaleidescape.com and hit enter.
Let the results happen.
Easy way for the next step is to capture the screen for both results so we can see the hops. If you'd rather not have ALL the hops, back to you, showing, just please send me the ones with names in the suffix, like comcast.net, or att.net or cogentco.com, etc. Leave out the first one or two if you're "security conscious".
The last one, I suspect, will end with something like pnap.net, with an address of 66.151.144.92 or very similar, which would indicate we are getting very close to the K servers. Those are hidden behind firewalls, so we can't ping them directly.
E-mail the results to me please.
My goal is to work out from the K server vicinity back towards the endpoints, and compare data rates on the client end with the routes that the data take. Once the data leaves K, it all goes out some common paths, and then begins to diverge at some point. Guys like House72 (Raj) and Poindexter who live outside the front door of the K facility will provide some useful data, and guys who live in places like Atlanta and Miami can offer some excellent data. The more commonality that is discovered, the easier it will be to whittle down to the actual culprit.
This is kind of a treasure hunt, and unfortunately you guys are not going to directly receive any treasure (I am sorry for that!) but it would be a magnanimous gesture, and would be helping your fellow man to achieve a better (Kaleidescape) life. If it helps even one other person resolve this critical, life-altering issue, it will be worth it.