Live data from Hacker News

AWS multiple services outage in us-east-1

health.aws.amazon.com

31–40 of 1001 posts

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

#32

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: ------ ER…

DockerHub shows full outage: https://www.dockerstatus.com/

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

#35
post #2

Looks like maybe a DNS issue? https://www.whatsmydns.net/#A/dynamodb.us-east-1.amazonaws.c... Resolves to nothing.

It's plausible that Amazon removes unhealthy servers from all round-robins including DNS. If all servers are unhealthy, no DNS.

Alternatively, perhaps their DNS service stopped responding to queries or even removed itself from BGP. It's possible for us mere mortals to tell which of these is the case.

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

#39
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.

Self hosting is golden. Sadly we already feel like we have too many services for our company's size, and the sensitivity of vulnerabilities in customer systems precludes unencrypted comms. IRC+TLS could be used but we also regularly send screenshots and such in self-destructing messages (not that an attacker couldn't disable that, but to avoid there being a giant archive when we do have some sort of compromise), so we'd rather fall back to something with a similar featureset

As a degraded-state fallback, email is what we're using now (we have our clients configured to encrypt with PGP by default, we use it for any internal email and also when the customer has PGP so everyone knows how to use that)

Post reply on HN