There are only two kinds of cloud regions: the ones people complain about and the ones nobody uses

Ass covering-wise, you are probably better off going down with everyone else on us-east-1. The not so fun alternative: being targeted during an RCA explaining why you chose some random zone no one ever heard of.

Cackling while reading this visiting my family in Northern Virginia for the holidays. Despite it being a prominent place in the history of the web, it's still the least reliable AWS region (for now).

I intentionally avoid using us-east-1 for anything, since I’ve seen so many outages.

Yes, it's the least reliable. Thanks for summarizing the data here to illustrate the issue.

It's often seen as the "standard" or "default" region to use when spinning up new US-based AWS services, is the oldest AWS center, has the most interconnected systems, and likely has the highest average load.

It makes sense that us-east-1 has reliability problems, but I wish Amazon was a little more upfront about some of the risks when choosing that zone.

I don't know if this is still true, or related, but that area used to be (Circa 10-30 years ago) very highly prone to power outages. The reason was lots of old trees near the lines that would inevitably fall; blackouts in local areas were common due to this.

At 34 hours of downtime that's two nines of uptime

At this point my garage is tied for reliability with us-east-1 largely because it got flooded 8 month ago.

Glad to use us-west-2 for reasons.

Of course it is, all of the NSA men in the middle add a lot of overhead that can interfere with regular operations.

The sorting for the "Duration" column appears to be lexicographical, not numeric.

We get constant resource issues in GCP’s us-east4 region

I searched for it, and did not find, the word "backhoe."

Big fail.

I have said for years, never ascribe to terrorism what can be attributed to some backhoe operator in Ashburn, Virginia.

We got a lotta backhoes in northern Virginia.