9 ms·

I've been getting the "We're sorry!" error for at least 15 minutes. No idea about regions or anything, I was just about to look up their docs about moving accou

I've been getting the "We're sorry!" error for at least 15 minutes. No idea about regions or anything, I was just about to look up their docs about moving accounts between orgs etc. Anyone affected? Edit: Seems to be flapping between the 'sorry' error and a blank page. Thoughts and prayers with the SREs, if they call 'em that over there.

bierjunge 5y ago
Same here. And as always, AWS status page [0] is completely green and useless. [0] https://status.aws.amazon.com/ https://status.aws.amazon.com/
- my123 5y ago
  Management console seems to be accessible fine to me, maybe it's just the aws.amazon.com website that's down.
  - raffraffraff 5y ago
    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).
- Thaxll 5y ago
  Because everything works fine? So a landing page does not work you need to put defcon 3?
  - ziddoap 5y ago
    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?
    - Thaxll 5y ago
      Landing page is not on the aws status page.
      - ziddoap 5y ago
        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.
- johnisgood 5y ago
  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.
- reidfromhome 5y ago
  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.

9 ms·

I've been getting the "We're sorry!" error for at least 15 minutes. No idea about regions or anything, I was just about to look up their docs about moving accou

by raffraffraff 5y ago

bierjunge 5y ago
Same here. And as always, AWS status page [0] is completely green and useless. [0] https://status.aws.amazon.com/ https://status.aws.amazon.com/
- my123 5y ago
  Management console seems to be accessible fine to me, maybe it's just the aws.amazon.com website that's down.
  - raffraffraff 5y ago
    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).
- Thaxll 5y ago
  Because everything works fine? So a landing page does not work you need to put defcon 3?
  - ziddoap 5y ago
    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?
    - Thaxll 5y ago
      Landing page is not on the aws status page.
      - ziddoap 5y ago
        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.
- johnisgood 5y ago
  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.
- reidfromhome 5y ago
  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.