Live data from Hacker News

AWS multiple services outage in us-east-1

health.aws.amazon.com

211–220 of 1001 posts

Re: AWS multiple services outage in us-east-1

#211

As this incident unfolds, what’s the best way to estimate how many additional hours it’s likely to last? My intuition is that the expected remaining duration increases the longer the outage persists, but that would ultimately depend on the historical distribution of similar incidents. Is that kind of data available anywhere?

Yes, with no prior knowledge the mathematically correct estimate is:

time left = time so far

But as you note prior knowledge will enable a better guess.

Re: AWS multiple services outage in us-east-1

#212
We just had a power outage in Ashburn starting at 10 pm Sunday night. It restored at 3:40am ish, and I know datacenters have redundant power sources but the timing is very suspicious. The AWS outage supposedly started at midnight

Re: AWS multiple services outage in us-east-1

#216

Nowadays when this happens it's always something . "Something went wrong." Even the error message itself is wrong whenever that one appears.

Displaying and propagating accurate error messages is an entire science unto itself... ...I can see why it's sometimes sensible to invest resource elsewhere and fall back to 'something'.

Re: AWS multiple services outage in us-east-1

#217
So, uh, over the weekend I decided to use the fact that my company needs a status checker/page to try out Elixir + Phoenix LiveView, and just now I found out my region is down while tinkering with it and watching Final Destination. That’s a little too on the nose for my comfort.

Re: AWS multiple services outage in us-east-1

#219

Can't resolve any records for dynamodb.us-east-1.amazonaws.com However, if you desperately need to access it you can force resolve it to 3.218.182.212. Seems to work for me. DNS through HN curl -v --resolve "dynamodb.us-east-1.amazonaws.com:443:3.218.182.212" https://dynamodb.us-east-1.amazonaws.com/

It's always DNS
Post reply on HN