One instance was randomly powered down about 22 hours ago. We saw a synthetic monitor failure at midnight. Investigation of the transaction trace shows that a

One instance was randomly powered down about 22 hours ago. We saw a synthetic monitor failure at midnight. Investigation of the transaction trace shows that a specific code path that should take maybe ~100ms took almost 40000ms. It could have been unresponsive EBS. Or failure to look up the Redis server's IP address. Or some other infrastructure-level failure. The synthetic browser saw it as a 502.