MicrostockGroup
Agency Based Discussion => Cutcaster => Topic started by: Dreamframer on April 23, 2009, 12:10
-
I can't open Cutcaster last two days. I can't even ping it in CMD, or open it using IP address instead of www.cutcaster.com. My friend from USA is opening it normally. Does anyone else have the same problem?
-
It's all OK here!
-
I just opened it using the link on the right. Very slow to open but it got there in the end!
-
Hmmm, I'm wondering what's wrong....
-
whitechild, the site is working for me (in US). But I've noticed for quite a while that it's consistently very slow to respond (or render) and I think that's a turn-off for buyers. The site looks good and is well constructed but the pages take too long to render. Could be a hosting issue, or the way the site is built, but I'd like to see i improved.
I found I'm unable to ping it, even if I specify a 20-second timeout (ping -w 20000 cutcaster.com). This is odd, but some hosts disable ping as a security measure.
I think a tracert may have answered these questions - my results are below. It seems CutCaster is hosted by the Amazon "cloud" which is not responding to a ping, and probably explains the slow site response too. The reachability of the site depends on deployment of Amazon's "edge" servers around the world. I don't know where you are, but you should do a tracert and see if you're even finding an Amazon edge server. If Amazon isn't delivering the goods, CutCaster should know about it.
C:\tracert cutcaster.com
Tracing route to cutcaster.com [174.129.248.125]
over a maximum of 30 hops:
[.... I deleted the hops through my ISP ]
6 18 ms 30 ms 25 ms vlan104.car2.Minneapolis1.Level3.net [4.59.66.9]
7 26 ms 27 ms 22 ms ae-11-11.car1.Minneapolis1.Level3.net [4.69.136.
101]
8 42 ms 46 ms 34 ms ae-4-4.ebr1.Chicago1.Level3.net [4.69.136.106]
9 49 ms 33 ms 33 ms ae-6.ebr1.Chicago2.Level3.net [4.69.140.190]
10 43 ms 37 ms 38 ms ae-1-100.ebr2.Chicago2.Level3.net [4.69.132.114]
11 45 ms 44 ms 49 ms ae-2-2.ebr2.Washington1.Level3.net [4.69.132.70]
12 61 ms 61 ms 55 ms ae-72-72.csw2.Washington1.Level3.net [4.69.134.1
50]
13 65 ms 62 ms 53 ms ae-2-79.edge1.Washington1.Level3.net [4.68.17.80
]
14 64 ms 72 ms 56 ms AMAZONCOM.edge1.Washington1.Level3.net [4.79.20.
14]
15 * * * Request timed out.
16 * * * Request timed out.
17 * * * Request timed out.
18 * * * Request timed out.
19 * * * Request timed out.
20 * * * Request timed out.
-
I also can't ping it but the website opens very fast for me. I'm in the US too.
-
Thank you Stockastic. BTW I'm in Southern Europe.
this is mine:
Tracing route to ec2-174-129-248-125.compute-1.amazonaws.com [174.129.248.125]
over a maximum of 30 hops:
1 * * * Request timed out.
2 34 ms 23 ms 19 ms 77.46.185.1
3 28 ms 47 ms 47 ms 212.200.15.209
4 23 ms 75 ms 43 ms 212.200.16.185
5 62 ms 29 ms 22 ms 212.200.232.33
6 29 ms 31 ms 25 ms 212.200.227.249
7 83 ms 97 ms 95 ms so-0-3-0-0.fra44.ip.tiscali.net [213.200.86.217]
8 212 ms 269 ms 257 ms so-0-0-0.was11.ip.tiscali.net [213.200.81.89]
9 164 ms 169 ms 163 ms 77.67.108.34
10 215 ms 84 ms 59 ms ae-82-82.ebr2.Frankfurt1.Level3.net [4.69.140.25
]
11 187 ms 190 ms 191 ms ae-41-41.ebr2.Washington1.Level3.net [4.69.137.5
0]
12 140 ms 157 ms 159 ms ae-92-92.csw4.Washington1.Level3.net [4.69.134.1
58]
13 172 ms 180 ms 140 ms ae-4-99.edge1.Washington1.Level3.net [4.68.17.20
8]
14 162 ms 143 ms 189 ms AMAZONCOM.edge1.Washington1.Level3.net [4.79.20.
14]
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.
-
I couldn't do nothing typing C:\tracert cutcaster.com. I had to type the IP address
-
i'm in canada, and i've been uploading to john's site for the past few days. just checked for you a moment ago, and all's well. john's been really nice too, i am #4 in featured archive. (thanks John Griffin).
but no, whitechild, i think it's probably your ISP .
is there anything you need from there? i can look for you , in the meantime.
send me PM if needed, ok ?
-
You're hitting Amazon, but only by IP, so it looks like the problem is in DNS. Try nslookup to see if the name is resolved - my results are below. If the problem is name resolution, it could be at several levels, including your local ISP.
Can you open the site as http://174.129.248.125 ?
C:\Users\jim>nslookup cutcaster.com
Server: UnKnown
Address: 192.168.30.1
Non-authoritative answer:
Name: cutcaster.com
Address: 174.129.248.125
-
Oh, thank you tan510! :) No need for that right now. I hope everything will back to normal.
-
right now I tried to open it again using IP address, and it's half opened. It was very slow and it suddenly stopped
-
Yikes thanks for letting me know about this. I am looking into this with the developer and will post some info but it is opening fine on my end.
I am hoping that a large FTP we are doing isn't causing the slowness but I will start to work on that during the nighttime (US time) so it wont effect the rest of the site. Let me know if you have any other suggestions guys for what it is and i will relay the j information to our developers. thanks a ton for letting me know about this.
john
-
Hi John, I just replied to your email. :)
-
you're good whitechild. thanks for all that info. i'll get this sorted out for you
-
John, by "slow" I mean a consistent 5-10 seconds to get the main page displayed, and I've noticed this for a couple of weeks at least. By comparison Shutterstock, for example, comes up just about instantly. In today's attention-deficit world, people start to avoid sluggish sites without even thinking about it.
I'm a software developer and if you find a clear reason for the slow access, I'd be interested to know it. Apparently CutCaster is hosted by Amazon and I'd like to know how that's working out. I use Amazon S3 for backup storage of my images but didn't know until recently that they were hosting sites in their "cloud".
-
The main page opens slowly for me too. However, my studio page opens almost instantly:
http://www.cutcaster.com/studio/view
-
goldenangel, your studio page took 10 seconds for me. But once I've opened the CC main page, my own studio page pops right up. So it depends on whether you've already hit the main page, I think.
-
ill let you know stockastic. so far ec2 at amazon has been good. that is their computing cloud.
-
goldenangel, your studio page took 10 seconds for me. But once I've opened the CC main page, my own studio page pops right up. So it depends on whether you've already hit the main page, I think.
stockastic, the link that i gave is a common link to anyone's studio page. I have it bookmarked so almost never open the main page. Still, the studio page opens almost instantly.
-
Try www.octgate.com. Enter the CC url and it will show you an interesting breakdown of the time spent loading the page and everything it pulls in - graphics, thumbnails, javascript files, css.
When I tried it, about 8 seconds were spent waiting for the first byte of the main page; after that, everything happened pretty quickly. So at first glance it seems like Amazon's page latency is the sticking point. I'm not really an expert so I shouldn't point the finger at Amazon, but that's my initial reading of what octgate shows. I wish I could just paste in a screen capture here...
-
Stockastic, that link opens some Czech website :)
-
Oops - here's the correct URL:
http://www.octagate.com/service/SiteTimer/?Target=AJAX
-
Very interesting link stockastic, thank you!
-
check out the page load now for the homepage. should be a ton faster now.
-
John,
For me at least, the main page has a long waiting period, followed by a pretty fast loading once this waiting is over. However, it was waiting for 10 seconds at least before loading. The studio page loads fast, no waiting period.
-
is that when you are logged in or logged out when you come to the page. what is it like when you are not logged into the site when you go the www.cutcaster.com site. thanks
-
I see the difference, and octagate.com shows that long wait for the intial page is gone. Was this an Amazon thing?
-
is that when you are logged in or logged out when you come to the page. what is it like when you are not logged into the site when you go the www.cutcaster.com site. thanks
That was when I was logged in. However I still see delay of the main page even when logged out while there is virtually no delay for www.cutcaster.com/studio/view
I should mention that I'm doing it now from home while before it was from work so should not be related to my ISP.
-
fine here as well
-
I take back my previous post - it still takes 10 seconds for the main page to render in my browser. But now the site timer at octagate.com shows quick access, whereas the other day it showed 8 seconds until the first byte was returned. Why the difference? The octagate server is in Stockholm and I'm in the US. Does access time for an Amazon-hosted site depend on which "edge" server you're getting?
-
check out the page load now for the homepage. should be a ton faster now.
From the Southern Philippines:
cutcaster comes up fast in the browser, but of course builds much slower than in a developed country at 24kbps.
I always block the landing page adframes and slideshows to increase speed.
Works fine, although traceroute looks bad.
Tracing route to cutcaster.com [174.129.248.125]
over a maximum of 30 hops:
1 8 ms 12 ms 16 ms 192.168.224.1
2 10 ms 14 ms 19 ms 203.111.229.241
3 48 ms 40 ms 35 ms 121.54.3.130
4 39 ms 35 ms 41 ms daikin-gwy01.meridiantelekoms.net [203.87.132.57
]
5 53 ms 54 ms 40 ms 124.83.5.101.pldt.net [124.83.5.101]
6 34 ms 37 ms 46 ms 58.71.0.157
7 45 ms 38 ms 36 ms 58.71.0.143
8 108 ms 126 ms 109 ms p16-5-2-2.a20.tokyjp01.jp.ra.gin.ntt.net [203.10
5.72.185]
9 155 ms 112 ms 117 ms xe-2-0-0.r20.tokyjp01.jp.bb.gin.ntt.net [61.213.
162.109]
10 113 ms 112 ms 122 ms ae-3.r20.osakjp01.jp.bb.gin.ntt.net [129.250.4.2
10]
11 246 ms 245 ms 231 ms as-2.r20.snjsca04.us.bb.gin.ntt.net [129.250.2.1
64]
12 299 ms 299 ms 312 ms as-1.r21.asbnva01.us.bb.gin.ntt.net [129.250.2.1
66]
13 331 ms 337 ms 307 ms xe-6-1.r00.asbnva02.us.bb.gin.ntt.net [129.250.3
.29]
14 304 ms * * xe-9-4.r05.asbnva01.us.ce.gin.ntt.net [168.143.2
32.74]
15 * 309 ms * 72.21.197.40
16 * 426 ms * 72.21.197.39
17 * * * Request timed out.
18 * * * Request timed out.
-
check out the page load now for the homepage. should be a ton faster now.
John, here in Halifax,NS , Canada it was never a problem with loading your site. but now it's almost instant with the new look. cheers.
-
I can open it now :)