
Indeed. Looks to have stabilized now; I was seeing trace routes die a couple hops out from my east instances. What was interesting is that Twitter reacted before Amazon's status page did. Makes me wonder if that's a monitoring failure on Amazon's part, or a more cynical "Let's not tell them we're down and see if they notice" position. Back to bed I go. -- Corey / KB1JWQ On Mar 15, 2012, at 2:52 AM, Michael R. Self wrote:
Corey:
I'm seeing what looks like communications failures amongst EC2 instances in us1east. The instances themselves do not appear affected (no lost instances or reboots) just IP traffic.
It also seems to have settled down now substantially.
73, Mike / N4OEY
************************** This email composed on my iPhone 4 whilst driving at 90 MPH with my knees.
Please excuse typo's and brevity due to accidents, cops and other mishaps.
Cheers, Michael Self PhoneFusion
On Mar 15, 2012, at 5:43, "Corey Quinn" <corey@sequestered.net> wrote:
Looks like AWS has taken a hit in East (Virginia). EC2 outages is what we're seeing here, no word yet on other services.
Amazon has yet to confirm this, but Twitter is all… atwitter, about it.
-- Corey / KB1JWQ _______________________________________________ Outages mailing list Outages@outages.org https://puck.nether.net/mailman/listinfo/outages