AWS Service Interuptions

It will take a direct hit with nuclear weapon on the datacenter for Amazon to change icon to red on service status page.

Not sure if relevant to this issue, but Sydney is currently being hit with one of the biggest storms I can remember in the past few years. Probably not crazy enough to take down a DC, but might be a contributing factor in this outage.

I realize that some systems may need to have all of their servers located close together in a single AZ. But barring that, if this took you offline, you should really consider spreading your instances across AZs. It&#x27;s so easy there&#x27;s no excuse not to do it.<p>Another thing to look into is EC2 Auto Recovery [1]. I don&#x27;t know if this would&#x27;ve kicked in with today&#x27;s event, but it&#x27;s worth setting up as an extra safety net.<p>[1] <a href="https:&#x2F;&#x2F;aws.amazon.com&#x2F;blogs&#x2F;aws&#x2F;new-auto-recovery-for-amazon-ec2&#x2F;" rel="nofollow">https:&#x2F;&#x2F;aws.amazon.com&#x2F;blogs&#x2F;aws&#x2F;new-auto-recovery-for-amazo...</a><p>edit: I&#x27;m basing this off the status page which indicated that only one AZ was impacted.

From AWS status page for Asia Pacific:<p>10:47 PM PDT We are investigating increased connectivity issues for EC2 instances in the AP-SOUTHEAST-2 Region.<p>11:08 PM PDT We continue to investigate connectivity issues for some instances in a single Availability Zone and increased API error rates for the EC2 APIs in the AP-SOUTHEAST-2 Region.<p>11:49 PM PDT We can confirm that instances have experienced a power event within a single Availability Zone in the AP-SOUTHEAST-2 Region. Error rates for the EC2 APIs have improved and launches of new EC2 instances are succeeding within the other Availability Zones in the Region.<p>Jun 5, 12:31 AM PDT We have restored power to the affected Availability Zone and are working to restore connectivity to the affected instances.

I recently switched to Google Compute Engine. It&#x27;s cheaper and so far more reliable than AWS. Might be another option for some people here.

Our Sydney EC2 DB instance is stuck spinning in the &quot;stopping&quot; state so we are basically offline right now. The team is working on getting a new DB instance set up, but I read that our payment provide, Westpac, is also having issues. So even if we do get back online, users might not be able to purchase.<p>What a mess.

For all intents and purposes, we&#x27;re completely offline at the moment. It&#x27;s clearly some serious issue because the icon for EC2 in Sydney on AWS&#x27; status page is yellow, rather than the usual green tick with the small &#x27;i&#x27;.

Still down 5 hours later. ELB won&#x27;t register instances. Ugh

Another confirmation here, all services in our Sydney AZ are down. AWS Support last mentioned a power failure or similar in AZ1, but some of ours are coming back online now.

I see lots of people using ELB for load balancing. Anyone tried using DNS on top of ELB to spread the load? That might just save you from the extended downtime.

Works for me - Sydney Region

Yes, AWS EC2 (Sydney) is completely offline from what we see. We have almost 10 servers there unaccessible for over an hour.

Yes, it seems that zone A is completely down. However, load balancers seem to be affected as well.

Still having issues with accessing apps hosted on Elastic Beanstalk on AP-SOUTHEAST-2 Region. Restarting app servers &#x2F; rebuilding the environment doesn&#x27;t make a difference.

Curious if you are all based in Australia, or if the Sydney outage is effecting other regions?

Anyone having problems with BJ servers? My site is not running, <a href="https:&#x2F;&#x2F;www.weisisheng.cn" rel="nofollow">https:&#x2F;&#x2F;www.weisisheng.cn</a>, I can not SSH into machine nor access login page to AWS dashboard.

We appear to be back online, however all machines have rebooted.

ap-southeast-2 EC2 appears to be completely offline for us