4 ms·
I'll take the opportunity to once again complain about how AWS's status page is a UX clusterfuck. Pretty much the entire us-east-1 region is unreliable, that n
by yuvadam 11y ago
I'll take the opportunity to once again complain about how AWS's status page is a UX clusterfuck.
Pretty much the entire us-east-1 region is unreliable, that needs to be glaring from the page. Instead, I need to browse hundreds of happy green checkmarks to find out what is/n't broken by their unreasonable standard.
What a fucking joke.
- deskamess 11y agoNot even consistent... Amazon DynamoDB (N. Virginia) Increased API error rates : Red icon. Amazon Redshift (N. Virginia) Increased API Error Rates : Green icon with check mark. Two recommendations: - No green with check mark (info). Change that to yellow/orange. At this point you are not fooling anyone that green with a check mark is not yellow. There can be no green if it is service impacting (reduced availability, performance, broken, etc - anything other than the norm) - Default sort should be by status : sort order is red-yellow-green. Need to know whats broken up-top.
- yuvadam 11y agoGoes without saying that Heroku is a great example of how it should be done - https://status.heroku.com/ https://status.heroku.com/
- idan 11y ago<3
- robotfelix 11y agoUnfortunately I'd have to disagree. Production applications belonging to paying customers are completely down - I don't think "Elevated Build and API Error Rates" quite does it justice. Note: The applications in question have had zero interactions (deploys, restarts, scaling, etc.) which might have caused their dynos to be unallocated/re-provisioned within Heroku's own service.
- vijaydev 11y agoWrote a simple script to hide all the green statuses https://gist.github.com/vijaydev/c0a670e79dcf7657cb2e https://gist.github.com/vijaydev/c0a670e79dcf7657cb2e