Options

Not getting data from smugmug.s3.amazonaws.com

PBolchoverPBolchover Registered Users Posts: 909 Major grins
edited November 13, 2007 in SmugMug Support
I'm trying to view http://cmac.smugmug.com/gallery/3799272#219256548-S-LB
but my browser is timing out at the "Transferring data from smugmug.s3.amazonaws.com" stage

My traceroute is
Tracing route to s3-2-w.amazonaws.com [207.171.183.117]
over a maximum of 30 hops:

  1     7 ms     9 ms     9 ms  73.214.32.1
  2     7 ms     7 ms     8 ms  68.85.250.161
  3     8 ms    11 ms     8 ms  68.85.244.90
  4     7 ms     9 ms     7 ms  68.85.244.93
  5     8 ms     7 ms     8 ms  68.85.244.97
  6    10 ms    11 ms     9 ms  te-3-3.car2.Houston1.Level3.net [4.79.90.5]
  7    15 ms    11 ms     9 ms  ae-11-11.car1.Houston1.Level3.net [4.69.132.233]
  8    26 ms    18 ms    18 ms  ae-5-5.ebr1.Dallas1.Level3.net [4.69.132.230]
  9     *       20 ms    18 ms  ae-1-100.ebr2.Dallas1.Level3.net [4.69.132.46]
 10    39 ms     *       41 ms  ae-2.ebr1.Denver1.Level3.net [4.69.132.105]
 11    30 ms    49 ms    54 ms  ae-1-100.ebr2.Denver1.Level3.net [4.69.132.38]
 12    70 ms    72 ms    57 ms  ae-2.ebr2.Seattle1.Level3.net [4.69.132.53]
 13    59 ms    65 ms    58 ms  ae-22-52.car2.Seattle1.Level3.net [4.68.105.35]
 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.
and my ping results say
Pinging s3-2-w.amazonaws.com [207.171.191.252] with 32 bytes of data:

Request timed out.
Request timed out.
Request timed out.
Request timed out.

Ping statistics for 207.171.191.252:
    Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),
(My ISP is Comcast in Houston, if that makes any difference)

Comments

  • Options
    AndyAndy Registered Users Posts: 50,016 Major grins
    edited November 11, 2007
    This is a connectivity issue from you to us, I would guess it'll resolve itself, they usually are quite temporary. Can you try again? If it persists, write to our help desk with a fresh traceroute, okay? Thanks.
  • Options
    PBolchoverPBolchover Registered Users Posts: 909 Major grins
    edited November 11, 2007
    Andy wrote:
    Can you try again? If it persists, write to our help desk with a fresh traceroute, okay?

    Have done so.
  • Options
    BaldyBaldy Registered Users, Super Moderators Posts: 2,853 moderator
    edited November 13, 2007
    Andy wrote:
    This is a connectivity issue from you to us, I would guess it'll resolve itself, they usually are quite temporary.
    Actually, I think it's to Amazon. We feed the videos directly from Amazon S3 and this is the first time I've heard of someone not being able to get to them.

    Investigating.
  • Options
    PBolchoverPBolchover Registered Users Posts: 909 Major grins
    edited November 13, 2007
    It turns out that the issue was mainly due to an old version of Quicktime. The data was making it to my computer, but Quicktime was silently dumping it. (For reference, version 6.5 of the Quicktime plug-in will claim to be up-to-date when, in fact, it is not the most recent version.)

    As a separate issue, it looks as if pings and traceroutes are being blocked on the path in question. But the actual data is getting through...
  • Options
    BaldyBaldy Registered Users, Super Moderators Posts: 2,853 moderator
    edited November 13, 2007
    PBolchover wrote:
    It turns out that the issue was mainly due to an old version of Quicktime. The data was making it to my computer, but Quicktime was silently dumping it. (For reference, version 6.5 of the Quicktime plug-in will claim to be up-to-date when, in fact, it is not the most recent version.)

    As a separate issue, it looks as if pings and traceroutes are being blocked on the path in question. But the actual data is getting through...
    Interesting. Thanks for the info. We soft launched this because we were afraid there would be some issues like this we had to learn.
Sign In or Register to comment.