Management console seems to be accessible fine to me, maybe it's just the aws.amazon.com website that's down.
Odd that a major landing page like aws.amazon.com isn't super HA. At a previous $work, the "marketing" page (ie: main dot com site) was horribly mis-managed and had countless outages due to various embarrassing reasons. Every time it was down, customers complained that the product was down (it wasn't, but people used the dot com page to get to the login page).
Which means people suggesting one another to compare their downtime with AWS' should stop suggesting it, as you cannot rely on their data at all.
The only thing that was down was the marketing home page at aws.amazon.com, which is not a “service” and is not on the SHD. All of the actual services are fine, hence the green.
Because everything works fine? So a landing page does not work you need to put defcon 3?
How on earth is putting a little red X or whatever next to the service that isn't working, when it isn't working, defcon 3?
Landing page is not on the aws status page.
And if it was, how is marking it as down a defcon 3 situation? My point was more that your original comment is a gross exaggeration.