IIRC, they also provide IPv6, too. Good to see more players.
Checked, and doublechecked, not just me
www.amazon.com returns:
Http/1.1 Service Unavailable
Anyone have a URL for a network/etc status page, or info on the outage?
Been that way for a while this morning.
-donn
Confirmed from L3/Tampa, 64.31.159.157
My mtr trace deadends at ae-11-79.car1.Washington3.Level3...
[outages], perhaps?
Cheers,
-- jra
I get that also with http://www.amazon.com, but do get the site using
http://www.amazon.com/tag/unavailable and then all links on the page though
click to the error - although the images on the page are all fine.
Chris
- --
Chris Stone, MCSE
Vice President, CTO
AxisInternet, Inc.
http://www.axint.net
DSL, dialup, hosting, email filtering, co-location, online backup
Phone: +1 303 592 2947 x302 (office) +1 303 570 6947 (cell)
- -------------------------------------------------------------------------
c>net article says: http://news.cnet.com/8301-10784_3-9962010-7.html?tag=nefd.top
https works for some pages
Lasher, Donn wrote:
Checked, and doublechecked, not just me
www.amazon.com returns:
Http/1.1 Service Unavailable
Anyone have a URL for a network/etc status page, or info on the outage?
Been that way for a while this morning.-donn
The web services still seem to be running and the co.uk site is up
and to pile on...
http://www.downforeveryoneorjustme.com/www.amazon.com
down as of - 2008-06-06 14:33:38 - now.
www.amazon.com returns:
Http/1.1 Service Unavailable
Anyone have a URL for a network/etc status page, or info on
the outage? Been that way for a while this morning.
Apparently, Amazon has fallen over, and cannot get up.
Even worse, the page they're displaying is actually a HTTP 200 response code(OK/no error), with no "Don't cache this" header - which means their error page is considered cacheable by some browsers/proxies. So, you may find users who tried to visit Amazon while they were down are still seeing it down long after they fix it.
Lesson to high profile websites: add these to your error pages so you don't have people complaining you're still down long after you're fixed.
* Don't return a 200 response code. Use 500 or 503. Nothing from 2xx or 4xx.
* Add a "Cache-control: no-cache, must-revalidate, max-age=0" header, as well as an "Expires: 0" header for good measure.
* If your server is really borked and you can't add headers at all, add '<META HTTP-EQUIV="Pragma" CONTENT="no-cache">' to the <head> section. That's not as good, but helps at least on the browser end.
* If possible, add a timestamp to the page somewhere (even if it's in an HTML comment) so you can troubleshoot with users still seeing the error.
-- Kevin
500 bucks per second.. that hurts.
https seems to work.
-wil
I've no idea what Amazon uses for Load Balancers, but I'm pretty sure
that error message is the default error message served up by a Netscaler
LB if no web services are available in the pool...
-andy
Good guess. AFAIK Amazon uses mostly Netscaler, with some homegrown
stuff and a few F5 boxes.
Maybe they should buy time on their own EC2 if they are short of webservers. 
The staus page http://status.aws.amazon.com/ shows them "Green and Clean"
Tuc
The actual headers returned are:
Server: NS_6.1
Content-Length: 62
Connection: close
503 Service Unavailable
Fred Reimer, CISSP, CCNP, CQS-VPN, CQS-ISS
Senior Network Engineer
Coleman Technologies, Inc.
954-298-1697
down.
-- j
This is rather suspicious (and confirmed by three other people):
I see a 503 actually.
When down:
iWil:~ wschultz$ curl www.amazon.com
HTTP/1.1 503 Service Unavailable
Server: NS_6.1
Content-Length:62
Connection: close
iWil:~ wschultz$ wget -S www.amazon.com
--12:21:26-- http://www.amazon.com/
=> `index.html'
Resolving www.amazon.com... 72.21.206.5
Connecting to www.amazon.com|72.21.206.5|:80... connected.
HTTP request sent, awaiting response...
HTTP/1.1 503 Service Unavailable
Server: NS_6.1
Content-Length:62
Connection: close
12:21:26 ERROR 503: Service Unavailable.
-wil
They took someone's advice, because it 503s now
David