Live data from Hacker News

US-East AWS Connectivity Issues

status.aws.amazon.com

41–50 of 51 posts

Re: US-East AWS Connectivity Issues

#41

Did anyone else notice a huge spike in incoming network traffic on their EC2 instance immediately before the outage? Roughly 9:55AM EST.

Did it look like a ddos attack, or do you think something went wrong where you were getting traffic meant for other EC2 nodes?

I'm not quite sure how you would tell the difference of course...

Re: US-East AWS Connectivity Issues

#42
post #3

Amazon is continuing the trend of announcing outages 30 minutes after they start. Just signed up for a support contract since the status page said everything was fine.

“outage (n): a period when a power supply or other service is not available or when equipment is closed down”

A subset of traffic taking longer than normal is not an outage

Re: US-East AWS Connectivity Issues

#48
I've recently moved some of our servers over to Digital Ocean, but I'm still using AWS for DNS since their Route 53 weighted DNS with health checks work as a basic load balancer for our needs. I'm seeing DNS health checks that point at individual servers at Digital Ocean that are showing 0.91 for a status (1 being up and 0 being down. The alarms attached to the health checks keep flipping from "alarm" to "ok" and causing tons of alerts. As of about 15 minutes ago all of my checks started holding steady back at a status of 1 (ok) Good stuff :)

Re: US-East AWS Connectivity Issues

#50

Earlier quoted context omitted.

Not just any Friday... $ date Fri Sep 13 12:07:58 EDT 2013

Not just any Friday the 13th... http://en.wikipedia.org/wiki/Programmers'_Day

Not just any Friday the 13th Programmer's Day... http://www.holidayinsights.com/other/fortunecookie.htm
Post reply on HN