Status.aws.amazon.com

AWS Service Health Dashboard

Get a personalized view of AWS service health Open the Personal Health Dashboard Current Status - Sep 18, 2021 PDT. Amazon Web Services publishes our most up-to-the-minute information on service availability in the table below.

Actived: 8 days ago

URL: https://status.aws.amazon.com/?aug2021

AWS Service Health Dashboard

(8 days ago) Get a personalized view of AWS service health Open the Personal Health Dashboard Current Status - Sep 24, 2021 PDT. Amazon Web Services publishes our most up-to-the-minute information on service availability in the table below.

Category:  Healthy Tips Go Now

AWS Service Health Dashboard

(9 days ago) Customers with Auto Scaling Groups configured to replace instances on impaired EC2 health checks may have had instances replaced as a result of this issue. The Availability Zone has been re-enabled for new launches and Auto Scaling has automatically replaced affected instances. The issue has been resolved and the service is operating normally.

Category:  Healthy Tips Go Now

AWS Service Health Dashboard

(6 days ago) While we began investigating several possible causes, we tried to restore system health by taking several actions to reduce system load. We reduced system load in several stages, but it had no impact on restoring system health. At 9:41am PDT, we determined that servers within Amazon S3 were having problems communicating with each other.

Category:  Healthy Tips Go Now

AWS Service Health Dashboard

(8 days ago) 3:23 PM PDT EU service has been fully restored. We have been working on the US in parallel but restoration will take longer due to fleet size. 4:03 PM PDT We are in the process of restoring Amazon S3 US, and will shortly be bringing the web servers back online. We expect the service will be restored within 1 hour.

Category:  Healthy Tips Go Now

AWS Service Health Dashboard

(7 days ago) Amazon Web Services » Service Health Dashboard » Amazon Simple Queue Service Event: July 20, 2008. Amazon Simple Queue Service Event: July 20, 2008. 9:28 AM PDT We're investigating an issue affecting requests. We'll continue to post updates here.

Category:  Healthy Tips Go Now

Amazon Route 53 Service Status

(5 days ago) There was no impact to the Route 53 API, DNS, or Health Checking services, which were all operating normally during this time. Service is operating normally: [RESOLVED] Increased Route 53 Console Errors

Category:  Healthy Tips Go Now

Amazon CloudFront Service Status

(8 days ago) We are investigating delays in propagating changes to CloudFront distributions to our edge locations. This is related to the ACM issue in the US-EAST-1 Region that we have posted to the Service Health Dashboard. Existing distributions continue to operate normally and there is no impact to serving content from our edge locations.

Category:  Healthy Tips Go Now

Amazon Web Services Service Status

(1 days ago) A component within the subsystem responsible for the processing of network packets for Network Load Balancer, NAT Gateway and PrivateLink services became impaired and was no longer processing health checks successfully.

Category:  Healthy Tips Go Now

AWS Service Health Dashboard

(8 days ago) As a distributed system, the different components of Amazon S3 need to be aware of the state of each other. For example, this awareness makes it possible for the system to decide to which redundant physical storage server to route a request. In order to share this state information across the system, we use a gossip protocol.

Category:  Healthy Tips Go Now

Amazon Elastic Load Balancing (N. Virginia) Service Status

(1 days ago) We are investigating increased provisioning latencies for new load balancers, delayed propagation of load balancer CloudWatch metrics, and inconsistent health check statuses from the DescribeTargetHealth API for Network Load Balancers in the US-EAST-1 Region.

Category:  Healthy Tips Go Now

Amazon OpenSearch Service (N. Virginia) Service Status

(1 days ago) The issue is caused by an overload of the health-checking mechanism that automatically directs the replacement of instances on failure. This system is flooding the service with configuration requests for replacements. We are working to reduce the replacement workflows. We will give further updates as we see progress.

Category:  Healthy Tips Go Now

Amazon Elastic Container Service (N. Virginia) Service Status

(1 days ago) Amazon Elastic Container Service (N. Virginia) Service Status Amazon Elastic Container Service (N. Virginia) Service Status

Category:  Healthy Tips Go Now

Amazon API Gateway (N. Virginia) Service Status

(8 days ago) Amazon API Gateway (N. Virginia) Service Status Amazon API Gateway (N. Virginia) Service Status

Category:  Healthy Tips Go Now

Amazon Elastic Compute Cloud (N. Virginia) Service Status

(1 days ago) In many cases, a retry of the request may succeed as some requests are still succeeding. Other AWS services that utilize these affected APIs for their own workflows may also be experiencing impact. These services have posted impact via the Personal Health and/or Service Health Dashboards. We will provide an update in 30 minutes.

Category:  Healthy Tips Go Now

Alexa for Business (N. Virginia) Service Status

(1 days ago) Alexa for Business (N. Virginia) Service Status Alexa for Business (N. Virginia) Service Status

Category:  Healthy Tips Go Now

Amazon Relational Database Service (Frankfurt) Service Status

(4 days ago) The issue has been resolved for nearly all instances. A small number of remaining instances are hosted on hardware which was adversely affected by increased ambient temperatures and loss of power. We continue to work to recover all affected instances and have opened notifications for the remaining impacted customers via the Personal Health

Category:  Healthy Tips Go Now

Amazon Relational Database Service (N. Virginia) Service

(1 days ago) By 11:55 AM, 1% of instances in the affected AZ were still experiencing connectivity issues. We continue to work to recover all affected instances and volumes and will be communicating to the remaining impacted customers via the Personal Health Dashboard.

Category:  Healthy Tips Go Now

Amazon Elastic Compute Cloud (N. California) Service Status

(1 days ago) Between 4:38 PM and 5:35 PM PDT a small number of instances were unavailable due to power loss in a single Availability Zone (usw1-az1) in the US-WEST-1 Region. Those customers received notification on their Personal Health Dashboard.

Category:  Healthy Tips Go Now

Amazon Virtual Private Cloud (Singapore) Service Status

(6 days ago) We continue to make progress in restoring network connectivity for VPN connections in the AP-SOUTHEAST-1 Region. We are also seeing an improvement in route propagation times as we work towards full recovery.

Category:  Healthy Tips Go Now

Amazon Relational Database Service (Ohio) Service Status

(1 days ago) 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).

Category:  Healthy Tips Go Now

Amazon DynamoDB (N. Virginia) Service Status

(6 days ago) Between 8:45 PM and 11:55 PM PST, we experienced increased processing times for update table with Amazon DynamoDB in the US-EAST-1 Region. The issue has been resolved and the service is operating normally.

Category:  Healthy Tips Go Now

Amazon API Gateway (Frankfurt) Service Status

(1 days ago) Amazon API Gateway (Frankfurt) Service Status Amazon API Gateway (Frankfurt) Service Status

Category:  Healthy Tips Go Now

Amazon WorkSpaces (N. Virginia) Service Status

(8 days ago) We continue to work to recover all affected WorkSpaces. Some of the remaining impacted WorkSpaces may require action from customers and we will be communicating to the remaining impacted customers via the Personal Health Dashboard. Service is operating normally: [RESOLVED] Connectivity Issues

Category:  Healthy Tips Go Now

Amazon WorkMail (N. Virginia) Service Status

(6 days ago) Between 6:57 PM and 9:25 PM PDT we experienced a degraded customer experience logging in to the WorkMail Web client in the US-EAST-1 Region. The issue has been resolved and the service is operating normally.

Category:  Healthy Tips Go Now

Amazon Elastic Compute Cloud (Frankfurt) Service Status

(4 days ago) A very small number of remaining instances and volumes that were adversely affected by the increased ambient temperatures and loss of power remain unresolved. We continue to work to recover those last affected instances and volumes, and have opened notifications for the remaining impacted customers via the Personal Health Dashboard.

Category:  Healthy Tips Go Now

AWS Internet Connectivity (N. Virginia) Service Status

(8 days ago) Between 8:26 AM and 9:46 AM PST, some customers experienced connectivity issues from the East Coast of the United States to AWS services. Connectivity to instances and services within the Region were not impacted by the event.

Category:  Healthy Tips Go Now

Amazon Kinesis Data Streams (N. Virginia) Service Status

(5 days ago) The issue also affects other services, or parts of these services, that utilize Kinesis Data Streams within their workflows. While features of multiple services are impacted, some services have seen broader impact and service-specific impact details are included within Recent Events on the Service Health Dashboard.

Category:  Healthy Tips Go Now

Amazon Simple Email Service (Frankfurt) Service Status

(4 days ago) Amazon Simple Email Service (Frankfurt) Service Status Amazon Simple Email Service (Frankfurt) Service Status

Category:  Healthy Tips Go Now

Amazon Elastic Load Balancing (Ohio) Service Status

(1 days ago) Amazon Elastic Load Balancing (Ohio) Service Status Amazon Elastic Load Balancing (Ohio) Service Status

Category:  Healthy Tips Go Now

Amazon Relational Database Service (Montreal) Service Status

(4 days ago) We wanted to provide an update for Amazon Aurora in the CA-CENTRAL-1 Region that we previously communicated to affected customers on their Personal Health Dashboards. Beginning at 11:43 AM PST some Amazon Aurora clusters experienced increased database create times and cluster unavailability in the CA-CENTRAL-1 Region.

Category:  Healthy Tips Go Now

Amazon Elastic Compute Cloud (Sao Paulo) Service Status

(1 days ago) At 11:10 PM PST on December 6 a small number of underlying hosts experienced power loss, affecting some customers in sae1-az3 in the SA-EAST-1 Region. Impacted customers were automatically notified via the Personal Health Dashboard. We quickly identified root cause and began working toward recovery.

Category:  Healthy Tips Go Now

Amazon Connect (N. Virginia) Service Status

(5 days ago) Between 8:17 AM and 9:30 AM PDT we experienced degraded call handling by agents using the softphone in the US-EAST-1 Region. The issue has been resolved and the service is …

Category:  Healthy Tips Go Now

Amazon Elastic Compute Cloud (London) Service Status

(1 days ago) A small number of remaining instances and volumes are hosted on hardware which was adversely affected by the loss of power. We continue to work to recover all affected instances and volumes and have opened notifications for the remaining impacted customers via the Personal Health Dashboard.

Category:  Healthy Tips Go Now

AWS Transfer for SFTP (N. Virginia) Service Status

(6 days ago) Between 3:34 AM and 6:39 AM PST we experienced increased login failures for Transfer Family in the US-EAST-1 Region. While many customers have been notified in their Personal Health Dashboard, we wanted to share more information about this event. We have identified the component responsible for these errors, and have mitigated the issue.

Category:  Healthy Tips Go Now

AWS Elastic Beanstalk (N. Virginia) Service Status

(4 days ago) Between 3:15 AM and 7:30 AM PDT some customers experienced elevated latencies or timeouts when creating, updating, and terminating Elastic Beanstalk environments in the US-EAST-1 …

Category:  Healthy Tips Go Now

Amazon Elastic Compute Cloud (Hong Kong) Service Status

(1 days ago) At 12:41 AM PDT, EBS volumes with degraded performance began to recover and by 12:58 AM PDT, the vast majority of affected EBS volumes had recovered. We continue to work on a small number of EBS volumes that are still experiencing degraded performance, and will provide further updates via the Personal Health Dashboard for those volumes.

Category:  Healthy Tips Go Now

Amazon Kinesis Data Streams (Oregon) Service Status

(5 days ago) We are investigating increased PutRecord API latencies in the US-WEST-2 Region. Informational message: [RESOLVED] Increased PutRecord API latency

Category:  Healthy Tips Go Now

Amazon Relational Database Service (London) Service Status

(1 days ago) Since the beginning of the impact, we have been working to recover the remaining database instances. A small number of remaining database instances are hosted on hardware which was adversely affected by the loss of power. For these database instances, we have provided additional recovery guidance via the Personal Health Dashboard.

Category:  Healthy Tips Go Now

Amazon Cloud Directory (Sydney) Service Status

(7 days ago) Amazon Cloud Directory (Sydney) Service Status Amazon Cloud Directory (Sydney) Service Status

Category:  Healthy Tips Go Now

Amazon Elastic Compute Cloud (Tokyo) Service Status

(6 days ago) A small number of remaining instances and volumes are hosted on hardware which was adversely affected by the event. We continue to work to recover all affected instances and volumes and have opened notifications for the remaining impacted customers via the Personal Health Dashboard.

Category:  Healthy Tips Go Now

Amazon Elastic Compute Cloud (Seoul) Service Status

(6 days ago) AP-NORTHEAST-2 리전의 단일 가용 영역 (APNE2-AZ3)에서 발생하고 있는 EC2 인스턴스의 기동 실패와 VPC 업데이트의 네트워크 전파 시간 지연에 대해 조사하고 있습니다. | We are investigating elevated launch failures for EC2 instances and delayed network propagation times for VPC update in a single Availability Zone (APNE2-AZ3) in the AP-NORTHEAST-2

Category:  Healthy Tips Go Now

Amazon Elastic Compute Cloud (Oregon) Service Status

(1 days ago) In many cases, retries of failed API requests were successful. Other AWS services that utilize the affected APIs for their own workflows also experienced impact. Those AWS Services have communicated with affected customers via the Personal Health Dashboard. The issue has been resolved and the service is operating normally.

Category:  Healthy Tips Go Now

Amazon Simple Storage Service (London) Service Status

(Just Now) Amazon Simple Storage Service (London) Service Status Amazon Simple Storage Service (London) Service Status

Category:  Healthy Tips Go Now

Related topics