3 ms·
I have in the past directed users here on HN who were complaining about https://status.aws.amazon.com https://status.aws.amazon.com to the Personal Health Dashb
by amichal 5y ago
I have in the past directed users here on HN who were complaining about https://status.aws.amazon.com https://status.aws.amazon.com to the Personal Health Dashboard at https://phd.aws.amazon.com/ https://phd.aws.amazon.com/ as well. Unfortunately even though the account I was logged into this time only has a single S3 bucket in the EU, billed through the EU and with zero direct dependancies on the US the personal health dashboard was ALSO throwing "The request processing has failed because of an unknown error" messages. Whatever the problem was this time it had global effects for the majority of users of the Console, the internet noticed for over 30 minutes before either the status page or the PHD were able to report it. There will be no explanation and the official status page logs will say there was "increased API failure rates" for an hour.
Now i guess its possible that the 1000s and 1000s of us who noticed and commented are some tiny fraction of the user base but if thats so you could at least publish a follow up like other vendors do that says something like 0.00001% of API requests failed effecting an estimated 0.001% of our users at the time.