I love this to be honest. Validates my anti cloud stance.
AWS multiple services outage in us-east-1
191–200 of 1001 posts
Re: AWS multiple services outage in us-east-1
#192Their status page (https://health.aws.amazon.com/health/status) says the only disrupted service is DynamoDB, but it's impacting 37 other services. It is amazing to see how big a blast radius a single service can have.
Re: AWS multiple services outage in us-east-1
#193LOL making one db service a central point of failure, charge gold for small compute instances. Rage about needing Multi AZ, make the costs come onto the developer/organization. But, now fail on a region level, so are we going to now have multi-country setup for simple small applications?
Re: AWS multiple services outage in us-east-1
#194They haven't listed SES there yet in the affected services on their status page
Re: AWS multiple services outage in us-east-1
#195It's weird that we're living in a time where this could be a taste of a prolonged future global internet blackout by adversarial nations. Get used to this feeling I guess :)
Re: AWS multiple services outage in us-east-1
#196Nowadays when this happens it's always something. "Something went wrong."
Even the error message itself is wrong whenever that one appears.
Re: AWS multiple services outage in us-east-1
#197Slack and Zoom working intermittently for me
Re: AWS multiple services outage in us-east-1
#198Robinhood's completely down. Even their main website: https://robinhood.com/
[deleted]
Re: AWS multiple services outage in us-east-1
#199Looks like a DNS issue - dynamodb.us-east-1.amazonaws.com is failing to resolve.
Re: AWS multiple services outage in us-east-1
#200We're seeing issues with RDS proxy. Wouldn't be surprised if a DNS issue was the cause, but who knows, will wait for the postmortem.
We changed our db connection settings to go direct to the db and that's working.
Try taking the proxy out the loop