us-east

It will be great to compare m1.small for all regions, or most cheap types in us-east-1 2.

We had some Opsworks instances reboot as well, but only minor outages overall (us-east and us-west).

US-East -> US-West), the latencies between the containers seem far higher than just the 200-300ms predicted by speed of light.

All of my instances in us-east-1 lost outbound connectivity Sunday morning for half an hour, and an hour last night.

My latency is 11 times what it would be if there were a direct fiber run from my laptop to us-east-1.

Put a chart with calculated savings: us-east-1 m1.small cost $10 but currently is trading for $5, so the chart will show you are saving %50, etc.

We started getting SQS errors from us-east-1 around 05:08 UTC.

My us-east boxes are up and accessible from Phoenix.

With us-east-1.linux.m1.small prices averaging around $0.03/hour, it might make sense to just set up an instance to continuously run on spot prices instead of paying the regular $0.085/hour.

I'm having no problems with us-east, accessed from Southern California and Texas.

All of these services seem to take the same approach: AWS US-East, maybe use two availability zones, call it a day.

Sure, the AWS us-west datacenters would go down (Oregon and NorCal), but us-east (VA) is still the largest of all AWS regions.

DO's "most popular plan" is $10/mo [1] AWS's t2.micro in us-east is ~$10.30/mo with a standard 8GB disk [2] Both VMs are single core, 1GB RAM.