Live data from Hacker News

AWS multiple services outage in us-east-1

health.aws.amazon.com

21–30 of 1001 posts

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

#22
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/

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

#28
post #13

Signal is down from several vantage points and accounts in Europe, I'd guess because of this dependence on Amazon overseas We're having fun figuring out how to communicate amongst colleagues now! It's when it's gone when you realise your dependence

Thankfully Slack is still holding up.

[flagged]

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

#29
post #13

Signal is down from several vantage points and accounts in Europe, I'd guess because of this dependence on Amazon overseas We're having fun figuring out how to communicate amongst colleagues now! It's when it's gone when you realise your dependence

Our last resort fallbacks are channels on different IRC servers. They always hold.

same here, we never left IRC

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

#30
docker hub or github cache internal maybe is affected:

Booting builder /usr/bin/docker buildx inspect --bootstrap --builder builder-1c223ad9-e21b-41c7-a28e-69eea59c8dac #1 [internal] booting buildkit #1 pulling image moby/buildkit:buildx-stable-1 #1 pulling image moby/buildkit:buildx-stable-1 9.6s done #1 ERROR: received unexpected HTTP status: 500 Internal Server Error ------ > [internal] booting buildkit: ------ ERROR: received unexpected HTTP status: 500 Internal Server Error

Post reply on HN