Comment by fastest963
12 hours ago
Coinbase claimed multiple AZs were down but the AWS statement was that only a single AZ was affected. Does anyone have more details?
12 hours ago
Coinbase claimed multiple AZs were down but the AWS statement was that only a single AZ was affected. Does anyone have more details?
Coinbase confirmed on X that the exchange only ran in one AZ for latency reasons: https://x.com/i/status/2052855725857329254
I can't find an official source, but I suspect the blast radius isn't limited to the AZ.
I have systems running in us-east-1, and over the course of the incident, I noticed unexplainable intermittent connectivity issues that I've never seen before, even outside of az4.
East-1 going down always takes some things from other AZs, because there's always something dependent on East-1.
Never trust a crypto company to be honest.
spent the evening looking at SLI graphs waiting for the region to blow up but it never did. only a few envs across many had some degraded EBS vols in the single AZ. it was absolutely a single az (use-az4).