Hacker News Reader

Comment by coldcode | Hacker News Reader

My feeling is this is an AWS issue. Our services hosted in AWS are not working either.

Downdetector indicates a possible correlation between Slack issues and AWS reports, eventhough Slack peaks at 13960 problems and AWS at 111:

- https://downdetector.com/status/slack/

- https://downdetector.com/status/aws-amazon-web-services/

Most people that are affected by AWS outages wouldn't report it as such...

I have also been having intermittent issues with Twitter also this morning (can't load tweets etc) and was wondering if it was connected.

Naaah, Twitter always fails to load for me. It's more surprising if it loads from the first attempt.

I thought Slack was not on AWS, but Oracle.

You may be thinking of Zoom, who signed a massive Oracle contract.

What issues are you seeing on AWS?

The dashboards are all green. (which doesn't mean that much ... I'm aware...)

Do you have more info like services, regions etc? I see all green checks on the AWS Status page.

Down detector shows quite a lot of issues across a broad spectrum of services, including AWS and Google.

Our prod systems seem to be working, but our lower environments seems to be not working. I don't know enough about where these things come from. I wonder if the real problem is regional. Some connections work and some don't.

> I see all green checks on the AWS Status page.

I'm sure you know this already, but that status page isn't worth the cycles on your CPU, you would be better served asking the toaster if AWS is functioning properly than checking that status page.

Of course, yeah, but at least you can sometimes see a yellow and infer it really means red :/.

yellow requires an issue that every customer is aware of and red requires a thermonuclear strike.

If one's smart toaster depends on AWS one might very well do that.

Which AZ?

Availability zones are unique for each account. So my zone A could be your zone C, for example.

Woah, thanks for clarifying--I had no idea!

I never knew this, but I think it makes sense. Is there any documentation that explains why this is the case? I suspect it is to distribute bias to the first option, but I'd love to read about it.

[edit] Nevermind, I just needed the right combination of terms to find it: https://docs.aws.amazon.com/ram/latest/userguide/working-wit...

This is so everyone doesn't launch in one zone, "us-east-1a".

Reply on news.ycombinator.com