591–600 of 1001 posts
FYI to S3 customers, per the SLA, most of us are eligible for a 10% credit for this billing period. But the burden is on the customer to provide incident logs and file a support ticket requesting said credit (it must be really challenging to programmatically identify outage coverage across customers /s) https://aws.amazon.com/s3/sla/
Sysadmin: I can forgive outages, but falsely reporting 'up' when you're obviously down is a heinous transgression. Somewhere a sysadmin is having to explain to a mildly technical manager that AWS services are down and affecting business critical services. That manager will be chewing out the tech because the status site shows everything is green. Dishonest metrics are worse than bad metrics for this exact reason. Any…
When SLA's are in play and so are job performance scores and bonuses there is probably a strong incentive to fudge numbers. It can be done officially ("Ah but sub-chapter 3 of chapter X in the fine print explains this wasn't technically an outage") or unofficially.
Upon the fields of barley
You'll forget the sun in his jealous sky
As we walk in fields of green
Earlier quoted context omitted.
I don't think they intentionally kept the checkmarks there. They probably just didn't update it as quickly as developers made a post on Hacker News (not surprising, they were probably investigating).
when you start investigating an outage, that is exactly when you should change your checkmark to yellow if not red. if you're as big as AWS there should not be any more than a minute or two between when your service goes down and when you actually update your status page to show that.
This can't be only the US-EAST-1 region. I'm a european resident and most things are down for me too.
We're in US-West-2 and our ELBs are dropping 5XXs like there's no tomorrow. This is definitely cascading.
Updated: Amazon Elastic Compute Cloud (N. Virginia) Increased Error Rates less 11:38 AM PST We can confirm increased error rates for the EC2 and EBS APIs and failures for launches of new EC2 instances in the US-EAST-1 Region. We are also experiencing degraded performance of some EBS Volumes in the Region. Amazon Elastic Load Balancing (N. Virginia) Increased Error Rates more Amazon Relational Database Service (N. Vir…
From http://status.aws.amazon.com/ Update at 11:35 AM PST: We have now repaired the ability to update the service health dashboard. The service updates are below. We continue to experience high error rates with S3 in US-EAST-1, which is impacting various AWS services. We are working hard at repairing S3, believe we understand root cause, and are working on implementing what we believe will remediate the issue.
For S3, we believe we understand root cause and are working hard at repairing. Future updates across all services will be on dashboard.