Amazon offers no explanation. Amazon Web Services continued functioning, with all services apparently available.
For about an hour starting around 11:30 a.m. Pacific, the Amazon.com retail home page was inaccessible to customers.
Attempts to access the site were met with a http://1.1 message on an otherwise white and unadorned screen. The site appeared to be operating normally again about 12:45 p.m. Pacific.
Several customers noted the outage on Facebook and Twitter. At 12:24 p.m. Pacific, The San Francisco technology reporting site, GigaOm, noted: "Amazon is down; Yes, you read that right." Security blogger George V. Hulme noted about 12:30 p.m. on Facebook: "Http/1.1 Service Unavailable."
"The gateway page of Amazon.com was offline to some customers for approximately 49 minutes. Other pages of the site were accessible and AWS was not impacted," said an Amazon spokesman in an email message late Thursday. The "gateway" page is a reference to the Amazon.com home page.
Amazon Web Services appeared to be up and running during that time. The AWS home page appeared on cue and key services, such as the Heroku cloud running on AWS, were still up during the period Amazon.com was inaccessible.
Editor's note: Updated to add Amazon response received late Thursday.
Multicloud Infrastructure & Application ManagementEnterprise cloud adoption has evolved to the point where hybrid public/private cloud designs and use of multiple providers is common. Who among us has mastered provisioning resources in different clouds; allocating the right resources to each application; assigning applications to the "best" cloud provider based on performance or reliability requirements.
Top IT Trends to Watch in Financial ServicesIT pros at banks, investment houses, insurance companies, and other financial services organizations are focused on a range of issues, from peer-to-peer lending to cybersecurity to performance, agility, and compliance. It all matters.
Join us for a roundup of the top stories on InformationWeek.com for the week of September 18, 2016. We'll be talking with the InformationWeek.com editors and correspondents who brought you the top stories of the week to get the "story behind the story."