Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

AWS us-east-1 down

news.ycombinator.com

Post reply on HN
Print view View original

251–260 of 331 posts

Re: AWS us-east-1 down

#251

Post by bawolff »

perlgeek wrote: post #107
kroltan wrote: post #60

Earlier quoted context omitted.

Semi-related: if you ever feel the need to report times to a global audience, not only make sure to always report the timezone (even if it is the same as the user's), but also use UTC offsets rather than timezone names. Life is too short to remember what each timezone name means and converting to it, UTC offsets are much easier on the mental calculator.

It's also not too complicated to add a few lines of javascript that show the datet/time in the user's local time zone (via Date.getTimezoneOffset) as well.

Honestly this is the worst when there is no timezone marker and some times are in browser time and others arent

Re: AWS us-east-1 down

#253

Post by jjk166 »

andersrs wrote: post #242
throaway87c10f0 wrote: post #164

Mysterious lack of "AWS is bad for the internet because it is so centralized" dialog up in here. edit: for those that would downvote: HN _just_ yesterday: https://news.ycombinator.com/item?id=36295352 https://news.ycombinator.com/item?id=36295305

It's a mob mentality. Safety in numbers. "Oh well, my site is down but so is my neighbour's so nobody will be that mad about it."

which is legitimate - if only you're down then you're losing business to your competitors and failing those who rely upon you; if everyone's down it's a wash. And frankly it's not like you're going to have significantly better uptime by going against the crowd.

Re: AWS us-east-1 down

#254

Post by bombcar »

bawolff wrote: post #251
perlgeek wrote: post #107

Earlier quoted context omitted.

It's also not too complicated to add a few lines of javascript that show the datet/time in the user's local time zone (via Date.getTimezoneOffset) as well.

Honestly this is the worst when there is no timezone marker and some times are in browser time and others arent

Or when logged times in the past change depending on today’s daylight savings setting.

Re: AWS us-east-1 down

#255

Post by p_l »

jjice wrote: post #89
thedigitalone wrote: post #80

Toast POS is down 100%, don't go out to lunch.

As a side note, I wonder if businesses won't even accept cash if they can't go through their POS system. If not, it's a shame that these modern internet connected POSs lock out stuff like that.

Depending on country and exact POS setup, they might not be able to take cash if POS is down.

For example, in Poland, your typical restaurant or shop needs to generate tax receipt (as well as properly calculate the tax), and uses either a separate receipt POS device, or POS with appropriate receipt printer (the devices are certified and for example do simultaneous two prints - one for client one for seller - or use digitally-signed storage for seller copy).

If the POS isn't designed properly to operate in case of network failure... welp, can't take cash either, at least not legally.

Re: AWS us-east-1 down

#256

Post by bombcar »

d8dUf7KjBEYCk7Q wrote: post #161
matwood wrote: post #123

Earlier quoted context omitted.

Back when we had servers in an onsite DC we lost a raid card and the system I was developing went down. We had the fancy support so a tech was out with the card replaced in a couple hours, then we had to restore from tape backup. All in all, a non-critical system was down for most of a business day. My bosses boss stormed in, upset he couldn't pull a report, and asked how do we prevent this in the future. I responded…

That sounds nice. My boss's boss is usually the one storming in, and he usually says "okay let's do it", and then I have to implement it in a week...

That’s why you always BofH the estimates to include some fun toys for yourself, too

Re: AWS us-east-1 down

#258

Post by heleninboodler »

ishjoh wrote: post #111
dveeden2 wrote: post #13

https://health.aws.amazon.com/health/status reports: Increased Error Rates and Latencies Jun 13 12:08 PM PDT We are investigating increased error rates and latencies in the US-EAST-1 Region. They list Lambda as the only affected service

certificate manager also down (I know because I tried to update an ssl cert for cloudfront which only allows US-East-1 ssl certs, maybe someone will eventually fix that to allow any region to have the ssl cert for cloudfront)

> cloudfront which only allows US-East-1 ssl certs

This seems like an odd limitation. Do you know the technical reason?

Re: AWS us-east-1 down

#259

Post by dietr1ch »

You'd think the largest cloud would be resilient to a zone going down, but I guess not.

i find it stupid that clients get to know about regions at all. They should only notice latency hits and batch job queuing latency if something bad happens underneath, but no services should go down.

Re: AWS us-east-1 down

#260

Post by bombcar »

SamuelAdams wrote: post #243
throaway87c10f0 wrote: post #164

Mysterious lack of "AWS is bad for the internet because it is so centralized" dialog up in here. edit: for those that would downvote: HN _just_ yesterday: https://news.ycombinator.com/item?id=36295352 https://news.ycombinator.com/item?id=36295305

Ok fine. Running your own datacenter in 2023 is incredibly risky. There's the upfront server cost and the ongoing maintenance cost. There's patches and staffing and disaster planning and all the other things that goes into it. Plus there's the cyberinsurance and protections and security components too. Do you really think other (smaller) orgs can do a better job at hosting a datacenter than Amazon / Google / Microsof…

Professional data center hosts host data centers very very well.

Amazon et al even contract with them.

But cloud isn’t selling rented rackspace; it’s selling APIs for billions of things. Much different.

Post reply on HN