Instance Unavailablility

4:52 PM PDT We are investigating connectivity issues to some RDS instances in the US-EAST-2 region.

5:35 PM PDT We can confirm connectivity issues to some RDS instances in the US-EAST-2 Region, and continue to work towards resolution.

6:04 PM PDT We are actively working to mitigate connectivity issues for some RDS instances in the US-EAST-2 Region and continue to work towards resolution. The issue with Aurora PostgreSQL is also impacting Elasticache, ELB, API Gateway and Elastic Beanstalk APIs. Existing Elasticache, ELB and API Gateway instances continue to operate normally.

6:33 PM PDT We have narrowed the cause of the connectivity issues impacting some RDS instances in the US-EAST-2 Region and we are continuing to work towards mitigation. The issue with Aurora PostgreSQL is also impacting Elasticache, ELB, API Gateway and Elastic Beanstalk APIs. Existing Elasticache, ELB and API Gateway instances continue to operate normally.

7:09 PM PDT We have begun to see some recovery for the connectivity issues impacting some RDS instances in the US-EAST-2 Region, and we are continuing to work towards mitigation.

8:23 PM PDT We are making progress towards restoring connectivity for the set of impacted Aurora PostgreSQL instances. Some database instances may see intermittent periods of recovery, but may not be fully recovered and we continue to work towards full recovery of these instances.

9:45 PM PDT Between 3:30 PM and 9:30 PM PDT, some Amazon Relational Database Service (RDS) Aurora PostgreSQL instances in the US-EAST-2 Region experienced increased latency and fault rates. This issue also caused issues with Elasticache, ELB, and API Gateway APIs. Existing Elasticache, ELB, and API Gateway instances were not impacted by this event and were operating normally during this entire impact period. We have recovered the vast majority of affected instances and will contact any customers who are still impacted through the Personal Health Dashboard (PHD).