Hacker News Reader

Comment by ceejayoz | Hacker News Reader

When AWS is having widespread issues half the internet seems to stop working. This looks like a 500 error on the console.

Is there any actual indication of AWS issues beyond one random person's tweet?

edit: Ah, https://twitter.com/ylastic just went on a retweeting tear. Looks like us-east-1?

View on HN

Can't find a permalink, but I had this notification in our AWS console:

> Beginning at Thu, 27 Jul 2017 13:53:00 GMT, some instances are experiencing elevated packet loss in the us-east-1a Availability Zone. We are now investigating this issue.

Some of our instances weren't reachable for about 10 minutes.

At my company we are seeing issues in us-east-1 involving KMS and EC2.

Interesting - I use both those services in us-east-1 and have not experienced issues. https://status.aws.amazon.com/ also shows a sea of green, although I'm not sure this page is even functional, because even when I know AWS has been having issues it's a sea of green.

In the last major AWS outage, it stayed green because updating it depended on some services affected by the outage.

Even when they can update it, it seems to be a manual process.

I think they've scrapped the AWS dependencies there, which were awfully silly. But it doesn't really seem to update regardless, and when it does it's a cute little 'i' on the green checkmark to inform you that everything is fine except for the 'actually working' part.

After nearly 10 years working with AWS, I've learned to never trust that page.

Reply on news.ycombinator.com