Hacker News Reader

Comment by jschorr | Hacker News Reader

Latest Update from http://status.aws.amazon.com/:

1:52 AM PDT We are actively working on the recovery process, focusing on multiple steps in parallel. While we are in recovery, customers will continue to see elevated error rate and latencies.

View on HN

The icon got yellow. I repeat: YELLOW

It only goes red when a nuclear event occurs, obliterating most of humanity and only the machines remain.

That would actually turn it green again, I think.

maybe true – but if a server gets no requests, does it really exist?

or would the inter-machine chatter continue ad infinitum? would they run out of IPs or successfully transition to IPv6?

So many questions.

Cory Doctorow's When Sysadmins Ruled the Earth touches on this - what happens to the internet activity during a global crisis?

http://craphound.com/overclocked/Cory_Doctorow_-_Overclocked...

this is excellent, hadn't seen it before! thx

Eventually the undefined behavior of this chatter will result in unallocated memory slowly churning in the garbage collection of time. Some day one of the sectors of unallocated memory will be executed resulting in a self replicating program. This program will evolve and multiply, pondering on the vastness of the S3verse, forever in search of Root.

my service looks pretty red now

The EC2 launch thing is still green even though all launches fail for us.

Could you expand what you mean? Is that because your launch is trying to fetch something from s3?

There was a period in which I couldn't launch instances. Meaning the instance state did not ever reach "running" according to the console and were not responsive to initial ssh attempts. (knife timed out after 5 minutes and the machines were still unavailable after several more)

Maybe related to AMI retrieval from S3?

Went to green again and it seems to be resolved.

Reply on news.ycombinator.com