Hacker News Reader

The times are off - says 01:00 GMT on the timer, but believe it was 01:00 PDT when Amazon began noticing issues.

"The errors, which started at 12:55AM PDT, began recovering at 2:55am PDT" http://status.aws.amazon.com/

Hold on a second, only EBS-backed instances and RDS are having trouble, yes? Not EC2 in general and not other services. To say "amazon aws services" is misleading.

only EBS-backed instances and RDS are having trouble, yes

This sentence is technically incorrect. Even at this hour, we're still experiencing problems instantiating volumes from snaps, attaching volumes, or recovering previously stuck volumes in at least one of the US-East availability zones. This is true even when the instances we're trying to target are not themselves backed by EBS.

It's true that if you don't touch EBS in any way you might be okay. But the problem is definitely ongoing and it definitely goes beyond just EBS-backed instances and RDS.

I think EBS is important enough that this isn't misleading. This should be obvious given how many sites this is actually affecting

Lumping S3 into EC2 isn't misleading?

fuck

fuck fuck

its still down 2 days later

AWS Downtime Counter