601–610 of 1001 posts
Earlier quoted context omitted.
I hear that their process for updating the status page involves S3.
it would appear that you are correct "The dashboard not changing color is related to S3 issue. See the banner at the top of the dashboard for updates." https://twitter.com/awscloud/status/836656664635846656
Earlier quoted context omitted.
So, global S3 outage for more than an hour now. Still green, still talking about "US East issue". I'm amazed.
It doesn't appear to be global; my app in eu-west-1 appears unaffected. It's possible that the console won't work however as I believe that's served from us-east-1.
Increased Error Rates
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.
The dashboard not changing color is related to S3 issue.
See the banner at the top of the dashboard for updates.
[edit- looks like they do have a pretty heavy reliance on S3, per https://github.com/WhisperSystems/Signal-Server/blob/master/... and various other sources.]
Notice how Amazon.com itself is unaffected. They're a lot smarter than us.
Earlier quoted context omitted.
It's unbelievable that the status page is still showing green checkmarks, almost what, 2 hours into the outage? edit: oh, it is actually because of the outage! So if they can't get a fresh read on the service status from s3, they just optimistically assume it's green... even though the service failing to provide said read... is one of the services they're optimistically showing as green XD
Hey can't change it due to the S3 issue. See their twitter post: https://twitter.com/awscloud/status/836656664635846656
That raises many more questions about how well accounted outages have been in the past and equally reported. Then the design aspect that in itself highlights if you run things in the cloud, what fallback do you have if that goes wrong. So certainly the impact from this outage is going to echo for a while, with many questions being asked.
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…
Where are you seeing these updates?
Earlier quoted context omitted.
People were joking about this but it turns out to be true: they host the status icons on their service: https://twitter.com/awscloud/status/836656664635846656
Saw that too, sounds like a convenient excuse for being caught in a lie. AWS Employee #1: Hey, people are catching on that our status page isn't accurate AWS Employee #2: Tell them it's cause of S3
TierPoint, a large hosting service, is reporting a massive DDOS attack on their infrastructure.
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/