Current Status - Sep 20, 2015 PDT

Amazon Web Services publishes our most up-to-the-minute information on service availability in the table below. Check back here any time to get current status information, or subscribe to an RSS feed to be notified of interruptions to each individual service. If you are experiencing a real-time, operational issue with one of our services that is not described below, please inform us by clicking on the "Contact Us" link to submit a service issue report. All dates and times are Pacific Time (PST/PDT).

Contact Us

• North America
• South America
• Europe
• Asia Pacific

Current Status		Details	RSS
	Amazon API Gateway (N. Virginia)	Service is operating normally
	Amazon API Gateway (Oregon)	Service is operating normally
	Amazon AppStream (N. Virginia)	[RESOLVED] Increased API Error Rates     more  6:44 AM PDT We are investigating increased API error rates in the US-EAST-1 Region. 8:19 AM PDT Between 6:44 AM PDT and 7:45 AM PDT we experienced increased API error rates for AppStream in the US-EAST-1 Region.The issue has been resolved and the service is operating normally.
	Amazon CloudFront	Service is operating normally
	Amazon CloudSearch (N. California)	Service is operating normally
	Amazon CloudSearch (N. Virginia)	[RESOLVED] Elevated API error rates     more  10:29 AM PDT Between 2:40 AM and 7:45 AM PDT we experienced increased error rates and latencies for API requests in the US-EAST-1 Region. CloudSearch resolved API issues, however, creating new domains and indexing operations functionality are still unavailable in US-EAST-1. Existing search domains continue to serve search queries. The issue has been resolved and the service is operating normally.
	Amazon CloudSearch (Oregon)	Service is operating normally
	Amazon CloudWatch (N. California)	Service is operating normally
	Amazon CloudWatch (N. Virginia)	[RESOLVED] Elevated Latencies and Faults in US-EAST-1     more  3:28 AM PDT We are investigating increased faults and latencies for CloudWatch Logs, Metrics and Alarms APIs in the US-EAST-1 Region. Log events and metrics may be delayed. Alarms may transition into "INSUFFICIENT_DATA" state if set on delayed metrics. 4:23 AM PDT We can confirm increased delays for CloudWatch log events and API faults in the US-EAST-1 Region. Customers may experience delayed or missing data points for CloudWatch metrics and CloudWatch alarms may transition into "INSUFFICIENT_DATA" state if set on delayed metrics. 6:39 AM PDT We can confirm significantly increased API faults for CloudWatch metrics and logs in the US-EAST-1 Region. Customers are experiencing delayed or missing data points for CloudWatch metrics and CloudWatch alarms will transition into "INSUFFICIENT_DATA" state if set on affected metrics. 7:37 AM PDT We are beginning to see recovery in API faults for CloudWatch metrics and logs in the US-EAST-1 Region. Customers may still experience delayed or missing data points for CloudWatch metrics and CloudWatch alarms may transition into "INSUFFICIENT_DATA" state if set on affected metrics. We are continuing to work to resolve the issue. 7:56 AM PDT We are seeing recovery in API faults for CloudWatch metrics and logs in the US-EAST-1 Region. Delayed metrics and log events are in the process of backfilling in CloudWatch console graphs and for API retrieval. Customers may still experience delayed or missing data points for CloudWatch metrics and CloudWatch alarms may transition into "INSUFFICIENT_DATA" state if set on affected metrics. We are continuing to monitor recovery. 8:22 AM PDT Between 02:23 AM PDT and 07:27 AM PDT, customers experienced elevated faults when calling CloudWatch Logs and Metrics APIs in the US-EAST-1 Region. Customers also experienced increased delays in some metrics. During that time, alarms on delayed metrics may have transitioned into an INSUFFICIENT_DATA state. We have resolved the issue. Delayed metrics and log events are in the process of backfilling in CloudWatch console graphs and for API retrieval. The service is operating normally.
	Amazon CloudWatch (Oregon)	Service is operating normally
	Amazon Cognito (N. Virginia)	[RESOLVED] Elevated API Error Rates     more  4:24 AM PDT We are investigating increased error rates for Amazon Cognito in the US-EAST-1 Region. 5:08 AM PDT We can confirm elevated error rates and latencies for our Amazon Cognito in the US-EAST-1 Region and are working towards resolution. 6:11 AM PDT We can confirm a significant increase in error rates for Amazon Cognito in the US-EAST-1 region. These errors reflect direct service API calls while applications using the AWS Mobile SDK continue to have access to their local sync datasets. 7:45 AM PDT We are seeing recovery on the API error rates for Amazon Cognito in the US-EAST-1 region. These errors reflect direct service API calls while applications using the AWS Mobile SDK continue to have access to their local sync datasets. We are continuing to work on full service recovery. 8:15 AM PDT Between 02:13am PDT and 07:55 am PDT, Amazon Cognito experienced increased error rates for acquiring identities and credentials, and synchronizing sync datasets in the US-EAST-1 region. We have fully recovered and the service is operating normally.
	Amazon DynamoDB (N. California)	Service is operating normally
	Amazon DynamoDB (N. Virginia)	[RESOLVED] Increased API error rates     more  3:00 AM PDT We are investigating increased error rates for API requests in the US-EAST-1 Region. 3:26 AM PDT We are continuing to see increased error rates for all API calls in DynamoDB in US-East-1. We are actively working on resolving the issue. 4:05 AM PDT We have identified the source of the issue. We are working on the recovery. 4:41 AM PDT We continue to work towards recovery of the issue causing increased error rates for the DynamoDB APIs in the US-EAST-1 Region. 4:52 AM PDT We want to give you more information about what is happening. The root cause began with a portion of our metadata service within DynamoDB. This is an internal sub-service which manages table and partition information. Our recovery efforts are now focused on restoring metadata operations. We will be throttling APIs as we work on recovery. 5:22 AM PDT We can confirm that we have now throttled APIs as we continue to work on recovery. 5:42 AM PDT We are seeing increasing stability in the metadata service and continue to work towards a point where we can begin removing throttles. 6:19 AM PDT The metadata service is now stable and we are actively working on removing throttles. 7:12 AM PDT We continue to work on removing throttles and restoring API availability but are proceeding cautiously. 7:22 AM PDT We are continuing to remove throttles and enable traffic progressively. 7:40 AM PDT We continue to remove throttles and are starting to see recovery. 7:50 AM PDT We continue to see recovery of read and write operations and continue to work on restoring all other operations. 8:16 AM PDT We are seeing significant recovery of read and write operations and continue to work on restoring all other operations. 9:12 AM PDT Between 2:13 AM and 8:15 AM PDT we experienced high error rates for API requests in the US-EAST-1 Region. The issue has been resolved and the service is operating normally.
	Amazon DynamoDB (Oregon)	Service is operating normally
	Amazon EC2 Container Service (N. California)	Service is operating normally
	Amazon EC2 Container Service (N. Virginia)	[RESOLVED] Increased API Errors and Latencies     more  4:37 AM PDT We are investigating increased API error rates and latencies for the EC2 Container Service APIs in the US-EAST-1 Region. Container Instance connectivity and running tasks are not affected. 6:51 AM PDT We can confirm increased API error rates and latencies for the EC2 Container Service APIs in the US-EAST-1 Region. Container Instance connectivity and running tasks are not affected. Customers publishing ECS metrics to CloudWatch may experience delayed or missing data points. 8:26 AM PDT Between 2:45 AM PDT and 8:05 AM PDT we experienced increased error rates and latencies for some EC2 Container Service APIs in the US-EAST-1 Region. During this period customers publishing ECS metrics to CloudWatch may have experience delayed or missing data points. Container Instance connectivity and running tasks were not affected. The issue has been resolved and the service is operating normally.
	Amazon EC2 Container Service (Oregon)	Service is operating normally
	Amazon Elastic Compute Cloud (N. California)	Service is operating normally
	Amazon Elastic Compute Cloud (N. Virginia)	[RESOLVED] Increased API Errors     more  3:12 AM PDT We are investigating increased error rates and latencies for the EC2 APIs in the US-EAST-1 Region. 3:51 AM PDT We can confirm increased error rates for EBS and Spot Instance APIs and increased error rates for new EC2 instance launches in the US-EAST-1 Region. Instance connectivity and EBS volume performance are not affected. 5:15 AM PDT We continue to work to resolve the increased error rates for EBS APIs, Spot Instance APIs, and new EC2 instance launches in the US-EAST-1 Region. In addition, we are experiencing increased error rates accessing VPC endpoints for S3, and Instance Status CloudWatch metrics are reporting INSUFFICIENT_DATA for some instances. Instance connectivity and EBS volume performance are not affected. 6:45 AM PDT We continue to work to resolve the issue in the US-EAST-1 Region. We are currently experiencing impact on a few dimensions: error rates for the EBS APIs and Spot Instance APIs are elevated; new EC2 instance launches are experiencing delays and elevated error rates; we are also experiencing increased error rates accessing VPC endpoints for S3; and Instance Status CloudWatch metrics are reporting INSUFFICIENT_DATA for some instances. Instance connectivity and EBS volume performance are not affected. 7:43 AM PDT Error rates for impacted APIs are beginning to recover and new instance launches are starting to succeed. We continue to work on restoring full service functionality. 8:19 AM PDT Between 2:13 AM and 8:07 AM PST EC2 experienced impact in the US-EAST-1 Region on a few dimensions: error rates for the EBS APIs and Spot Instance APIs were elevated; new EC2 instance launches experienced delays and elevated error rates; we experienced increased error rates accessing VPC endpoints for S3; VPC Flow Logs were delayed; and Instance Status CloudWatch metrics reported INSUFFICIENT_DATA for some instances. Instance connectivity and EBS volume performance were not affected. The issue has been resolved and the service is operating normally.
	Amazon Elastic Compute Cloud (Oregon)	Service is operating normally
	Amazon Elastic Load Balancing (N. California)	Service is operating normally
	Amazon Elastic Load Balancing (N. Virginia)	[RESOLVED] Increased API Error Rates     more  4:15 AM PDT We are investigating increased API error rates and latencies for the ELB APIs in the US-EAST-1 Region. Connectivity to load balancers is not affected. 8:30 AM PDT Between 2:13 AM and 8:07 AM PDT we experienced increased error rates and latencies for the ELB APIs in the US-EAST-1 Region. The issue has been resolved and the service is operating normally.
	Amazon Elastic Load Balancing (Oregon)	Service is operating normally
	Amazon Elastic MapReduce (N. California)	Service is operating normally
	Amazon Elastic MapReduce (N. Virginia)	[RESOLVED] Increased API Error Rates and Latencies     more  3:42 AM PDT We are investigating increased error rates and latencies for Amazon EMR APIs in the US-EAST-1 Region. 5:00 AM PDT We can confirm increased error rates and latencies for all APIs and delays starting and terminating clusters in the US-EAST-1 Region. We continue to work towards resolution. 7:48 AM PDT We are seeing recovery on API error rates and latencies for Amazon EMR API calls in the US-EAST-1 Region. Customers may still see delays in starting and terminating clusters. We continue to work towards full resolution. 8:56 AM PDT Between 2:20 AM and 8:35 AM PDT we experienced higher than normal error rates and latencies for Amazon EMR APIs, and delays in starting and terminating clusters in the US-EAST-1 Region. The issue has been resolved and the service is operating normally.
	Amazon Elastic MapReduce (Oregon)	Service is operating normally
	Amazon Elastic Transcoder (N. California)	Service is operating normally
	Amazon Elastic Transcoder (N. Virginia)	[RESOLVED] Elevated API Error Rates     more  4:00 AM PDT We are investigating increased error rates for Amazon Elastic Transcoder APIs in the US-EAST-1 Region. 7:56 AM PDT Between 2:30 AM PDT and 7:36 AM PDT customers experienced elevated error rates for Amazon Elastic Transcoder APIs in the US-EAST-1 Region. The issue has now been resolved and the service is operating normally.
	Amazon Elastic Transcoder (Oregon)	Service is operating normally
	Amazon ElastiCache (N. California)	Service is operating normally
	Amazon ElastiCache (N. Virginia)	Service is operating normally
	Amazon ElastiCache (Oregon)	Service is operating normally
	Amazon Glacier (N. California)	Service is operating normally
	Amazon Glacier (N. Virginia)	[RESOLVED] Elevated API Error Rates     more  4:16 AM PDT We are investigating increased API error rates in the US-EAST-1 Region. 8:18 AM PDT Between 2:34 PDT and 7:28 PDT, we experienced elevated API error rates. This issue has been resolved and the service is operating normally.
	Amazon Glacier (Oregon)	Service is operating normally
	Amazon Kinesis (N. California)	Service is operating normally
	Amazon Kinesis (N. Virginia)	[RESOLVED] Elevated API Error Rates     more  4:37 AM PDT We are currently investigating increased error rates for API requests in the US-EAST-1 Region. 6:14 AM PDT We can confirm significantly increased error rates for Amazon Kinesis API calls in the US-EAST-1 Region and continue to work towards resolution. 7:36 AM PDT We are seeing recovery on API error rates for Amazon Kinesis API calls in the US-EAST-1 Region and continue to work on restoring full service functionality. 8:09 AM PDT Between 2:13 AM PDT and 7:36 AM PDT we experienced increased error rates and latencies for Amazon Kinesis API calls in the US-EAST-1 Region. The issue has been resolved and the service is operating normally.
	Amazon Kinesis (Oregon)	Service is operating normally
	Amazon Machine Learning (N. Virginia)	[RESOLVED] Increased API Error Rates and Latencies     more  5:11 AM PDT We are investigating increased API error rates and latencies in the US-EAST-1 Region. 6:09 AM PDT We can confirm increased error rates and latencies to Machine Learning APIs in the US-EAST-1 Region and continue to work towards resolution. 6:12 AM PDT We can confirm increased error rates and latencies to Machine Learning APIs in the US-EAST-1 Region and continue to work towards resolution. 9:04 AM PDT Between 2:30 AM and 8:40 AM PDT, Amazon Maching Learning experienced increased error rates in the US-EAST-1 Region. The issue has been resolved and the service is operating normally.
	Amazon Mobile Analytics (N. Virginia)	[RESOLVED] Increased Error rates     more  3:57 AM PDT We are investigating increased error rates for the Mobile Analytics console in the US-EAST-1 Region. 6:52 AM PDT Mobile Analytics charts are not currently available in the AWS console and auto-export of analytics events to S3 and Redshift is currently delayed. App events submitted to the service via API continue to be recorded. 8:11 AM PDT We have identified root cause, and Mobile Analytics charts are displaying in the AWS console. Auto-export of events to S3 and Redshift have resumed. 9:41 AM PDT Between 2:15 AM and 7:45 AM PDT, Amazon Mobile Analytics experienced issues displaying analytics charts in the AWS console. We identified the root cause, the error has been corrected, and the service is operating normally. Auto-export of analytics events to S3 and Redshift continues to be delayed, and we are investigating root cause. 11:10 AM PDT Between 2:15 AM and 11:05 AM PDT, Amazon Mobile Analytics experienced issues processing analytics events and auto-exporting events to S3 and Redshift. We identified the root cause, the error has been corrected, and the service is operating normally. No analytics events were lost during this time.
	Amazon Redshift (N. Virginia)	[RESOLVED] Increased API Error Rates     more  3:51 AM PDT We are investigating increased API error rates in the US-EAST-1 Region. 5:27 AM PDT We continue to experience elevated error rates for some APIs in the US-EAST-1 Region and are working towards a resolution. 8:07 AM PDT We are beginning to see recovery in API error rates and latencies, and are continuing to work towards full recovery. 9:30 AM PDT Between 2:26 AM and 8:15 AM PDT we experienced increased error rates and latencies for API requests in the US-EAST-1 Region. The issue has been resolved and the service is operating normally.
	Amazon Redshift (Oregon)	Service is operating normally
	Amazon Relational Database Service (N. California)	Service is operating normally
	Amazon Relational Database Service (N. Virginia)	[RESOLVED] Increased API Error Rates     more  3:43 AM PDT We are investigating increased API error rates in the US-EAST-1 Region. 4:20 AM PDT We can confirm increased error rates for all APIs in the US-EAST-1 Region and continue to work towards resolution. 6:50 AM PDT We continue to experience elevated error rates for some APIs in the US-EAST-1 Region and are working towards a resolution. 8:31 AM PDT We are seeing limited recovery of the elevated error rates for some APIs in the US-EAST-1 Region. 9:41 AM PDT We continue to see recovery of the elevated error rates of some APIs in the US-EAST-1 Region and are working towards a full resolution. 10:05 AM PDT Between 2:26 and 9:55 AM PDT, RDS experienced increased API error rates in the US-EAST-1 Region. The issue has been resolved and the service is operating normally.
	Amazon Relational Database Service (Oregon)	Service is operating normally
	Amazon Route 53	Service is operating normally
	Amazon Route 53 Private DNS (N. California)	Service is operating normally
	Amazon Route 53 Private DNS (N. Virginia)	Service is operating normally
	Amazon Route 53 Private DNS (Oregon)	Service is operating normally
	Amazon Simple Email Service (N. Virginia)	[RESOLVED] Elevated email-sending API error rates     more  3:19 AM PDT We are currently investigating elevated error rates for our email-sending APIs in the US-EAST-1 Region. This includes the SendEmail/SendRawEmail APIs as well as calls made to the SMTP endpoint. 4:45 AM PDT We can confirm elevated error rates and latencies for our email-sending APIs in the US-EAST-1 Region and are working towards resolution. 6:39 AM PDT We can confirm significantly increased error rates for our email-sending APIs in the US-EAST-1 Region and are continuing to work towards resolution. 7:45 AM PDT We are beginning to see recovery in API error rates and latencies in the US-EAST-1 Region. We are continuing to work to resolve the issue. 8:15 AM PDT Between 2:35 AM PDT and 7:30 AM PDT we experienced elevated error rates and latencies across our APIs in the US-EAST-1 Region. The issue has been resolved and the service is operating normally.
	Amazon Simple Email Service (Oregon)	Service is operating normally
	Amazon Simple Notification Service (N. California)	Service is operating normally
	Amazon Simple Notification Service (N. Virginia)	[RESOLVED] Increased Error rates     more  3:45 AM PDT We are investigating increased error rates in the US-EAST-1 Region. 4:45 AM PDT We can confirm increased error rates for API calls in the US-EAST-1 Region and continue to work towards resolution. 6:16 AM PDT We can confirm significantly increased error rates for all API calls including publish, subscribe and topic-related APIs in the US-EAST-1 Region. 7:31 AM PDT We are seeing recovery on API error rates for all APIs including publish, subscribe and topic-related APIs. We continue to work on restoring full service functionality. 7:57 AM PDT We are continuing to see recovery on API error rates for all APIs including publish, subscribe and topic-related APIs. We continue to work on restoring full service functionality. 8:18 AM PDT Between 2:35 AM and 7:14 AM PDT, Amazon SNS experienced elevated API error rates for all API calls including publish, subscribe, and topic-related APIs. We identified the root cause, the error has been corrected, and the service is operating normally.
	Amazon Simple Notification Service (Oregon)	Service is operating normally
	Amazon Simple Queue Service (N. California)	Service is operating normally
	Amazon Simple Queue Service (N. Virginia)	[RESOLVED] Increased Error rates     more  3:14 AM PDT We are investigating increased error rates in the US-EAST-1 Region. 4:06 AM PDT We can confirm increased error rates for CreateQueue, SendMessage and ReceiveMessage API calls in the US-EAST-1 Region and continue to work towards resolution. 5:07 AM PDT We can confirm increased error rates for CreateQueue, SendMessage and ReceiveMessage API calls in the US-EAST-1 Region. As we work towards recovery, error rates may temporarily increase. 6:06 AM PDT We can confirm significantly increased error rates for CreateQueue, SendMessage and ReceiveMessage API calls in the US-EAST-1 Region. As we work towards recovery, error rates may temporarily increase. 7:43 AM PDT We are beginning to see recovery in API error rates for Simple Queue Service API calls in the US-EAST-1 Region and continue to work on restoring full service functionality. 7:57 AM PDT We are continuing to see improvements in API error rates for SQS API calls in the US-EAST-1 Region and continue to work on restoring full service functionality. 8:20 AM PDT Between 2:42 AM and 7:14 AM PDT SQS experienced significantly elevated API error rates for CreateQueue, SendMessage and ReceiveMessage API calls in the US-EAST-1 Region. The issue has been resolved and the service is operating normally.
	Amazon Simple Queue Service (Oregon)	Service is operating normally
	Amazon Simple Storage Service (N. California)	Service is operating normally
	Amazon Simple Storage Service (Oregon)	Service is operating normally
	Amazon Simple Storage Service (US Standard)	Service is operating normally
	Amazon Simple Workflow Service (N. California)	Service is operating normally
	Amazon Simple Workflow Service (N. Virginia)	[RESOLVED] Increased Error rates and delayed workflows     more  3:17 AM PDT We are investigating increased API error rates in the US-EAST-1 Region. 4:07 AM PDT We can confirm increased error rates for all APIs in the US-EAST-1 Region and continue to work towards resolution. 6:50 AM PDT We can confirm significantly increased API error rates and delays in workflow processing in the US-EAST-1 Region and continue to work towards resolution. 7:44 AM PDT We are beginning to see recovery in API error rates for Simple Workflow API calls in the US-EAST-1 Region and continue to work on restoring full service functionality. 8:30 AM PDT Between 2:26 AM and 7:40 AM PDT SWF experienced elevated API error rates, and increased workflow processing times in the US-EAST-1 Region. The issue has been resolved and the service is operating normally.
	Amazon Simple Workflow Service (Oregon)	Service is operating normally
	Amazon SimpleDB (N. California)	Service is operating normally
	Amazon SimpleDB (N. Virginia)	Service is operating normally
	Amazon SimpleDB (Oregon)	Service is operating normally
	Amazon Virtual Private Cloud (N. California)	Service is operating normally
	Amazon Virtual Private Cloud (N. Virginia)	Service is operating normally
	Amazon Virtual Private Cloud (Oregon)	Service is operating normally
	Amazon WorkDocs (N. Virginia)	[RESOLVED] Increased Error Rates and Latencies     more  7:06 AM PDT We are experiencing login issues and elevated error rates and latencies in the US-EAST-1 region. We are working toward resolution. 8:06 AM PDT We are beginning to see recovery for login, error rates, and latencies. We are continuing to work on fully restoring the service 8:32 AM PDT Between 2:16 AM PDT and 7:41 AM PDT, we experienced elevated login issues, error rates, and latencies in the US-EAST-1 region. This issue has been resolved and the service is operating normally.
	Amazon WorkDocs (Oregon)	Service is operating normally
	Amazon WorkSpaces (N. Virginia)	[RESOLVED] Increased Connectivity and API Failure Rates     more  4:13 AM PDT We are investigating connectivity issues for WorkSpaces in the US-EAST-1 Region. 5:21 AM PDT We can confirm connectivity issues and API faults for WorkSpaces in the US-EAST-1 Region and are working towards resolution. 6:34 AM PDT We can confirm significantly increased connectivity issues and API error rate for WorkSpaces in the US-EAST-1 Region. We are actively working to resolve the issue. 7:55 AM PDT We are seeing recovery on connectivity issues and API faults for WorkSpaces in the US-EAST-1 Region. We continue to work on restoring full service functionality. 8:28 AM PDT Between 2:25 AM PDT and 7:51 AM PDT we experienced increased connectivity issues and API error rates for WorkSpaces in the US-EAST-1 Region.The issue has been resolved and the service is operating normally.
	Amazon WorkSpaces (Oregon)	Service is operating normally
	Auto Scaling (N. California)	Service is operating normally
	Auto Scaling (N. Virginia)	[RESOLVED] Increased Error rates and delayed instance replacements     more  3:14 AM PDT We are investigating increased error rates in the US-EAST-1 Region. 4:08 AM PDT We can confirm increased error rates for all APIs in the US-EAST-1 Region and continue to work towards resolution. 6:53 AM PDT We can confirm significantly increased error rates for all APIs and increases in the time to launch replacements for failed instances in the US-EAST-1 Region. We continue to work towards resolution. 7:46 AM PDT We are beginning to see recovery in API error rates for Auto Scaling API calls in the US-EAST-1 Region. Customers may still experience delays in launching or terminating instances due to metric alarms or health checks. We continue to work on restoring full service functionality. 9:36 AM PDT We continue to experience delays launching and terminating instances due to metric alarms or health checks and continue to work on restoring full service functionality. 10:07 AM PDT We have resolved issues with API error rates, but are still seeing increased instance replacement and launch times and are continuing to investigate this issue in the US-EAST-1 Region. 11:23 AM PDT Between 2:26 AM and 10:52 AM PDT Auto Scaling experienced elevated API error rates, and increased latency in the time to launch replacements for failed instances in the US-EAST-1 Region. The issue has been resolved and the service is operating normally.
	Auto Scaling (Oregon)	Service is operating normally
	AWS CloudFormation (N. California)	Service is operating normally
	AWS CloudFormation (N. Virginia)	[RESOLVED] Elevated API error rates and latencies     more  3:52 AM PDT We are experiencing elevated error rates and latencies for the AWS CloudFormation APIs in theUS-EAST-1 region. 4:16 AM PDT We are investigating increased error rates and latencies for APIs in the US-EAST-1 region 7:12 AM PDT We can confirm high error rates for API requests and latencies for customers creating, updating and deleting stacks in US-EAST-1. We are actively working to resolve the issue. 8:02 AM PDT "API error rates and latencies are beginning to recover for customers in US-EAST1. We are continuing to work on resolving the problem." 8:16 AM PDT "API error rates and latencies have seen significant recovery for customers in US-EAST1. We are continuing to work on resolving the problem. 8:59 AM PDT Between 02:31 and 07:30 PDT, CloudFormation APIs experienced significantly elevated error rates and latencies is US-EAST-1. The errors have recovered and the service is now operating normally.
	AWS CloudFormation (Oregon)	Service is operating normally
	AWS CloudHSM (N. Virginia)	Service is operating normally
	AWS CloudHSM (Oregon)	Service is operating normally
	AWS CloudTrail (N. California)	Service is operating normally
	AWS CloudTrail (N. Virginia)	[RESOLVED] Elevated event delivery latencies in US-EAST-1     more  3:31 AM PDT We are investigating delays in delivering CloudTrail events in the US-EAST-1 Region to some users' S3 buckets. 5:47 AM PDT We can confirm significant latencies of event delivery and increased error rates in the US-EAST-1 Region. We are actively working to resolve the issue. 8:47 AM PDT Between 2:30 AM and 8:40 AM PDT, CloudTrail experienced delays in processing events in the US-EAST-1 Region. We have resolved the issue. Delayed events are in the process of backfilling. The service is operating normally.
	AWS CloudTrail (Oregon)	Service is operating normally
	AWS CodeCommit (N. Virginia)	[RESOLVED] Increased API and Git Push/Pull Error Rates     more  3:33 AM PDT We are investigating increased control plane and git push/pull error rates in the US-EAST-1 Region. 6:38 AM PDT We can confirm elevated error rates and latencies for the control plane and git push/pull operations in the US-EAST-1 Region and are working towards resolution. 7:49 AM PDT Control plane and git push/pull error rates are beginning to recover for customers in US-EAST1. We continue to work on restoring full service functionality 8:25 AM PDT Between 2:13 AM and 7:38 AM PDT we experienced increased control plane and git push/pull error rates in the US-EAST-1 Region. The issue has been resolved and the service is operating normally.
	AWS CodeDeploy (N. Virginia)	[RESOLVED] Increased API Error Rates     more  3:57 AM PDT We are investigating increased API error rates in the US-EAST-1 Region 6:57 AM PDT We can confirm increased API error rates in the US-EAST-1 Region and continue to work towards resolution 7:53 AM PDT We are beginning to see recovery in API error rates in the US-EAST-1 Region. 9:58 AM PDT We have resolved issues with API error rates, but are still seeing increased deployment latency and are continuing to investigate this issue in the US-EAST-1 Region. 10:08 AM PDT Between 2:13 AM and 9:20 AM PDT we experienced increased API error rates and latencies in the US-EAST-1 Region. The issue has been resolved and the service is operating normally.
	AWS CodeDeploy (Oregon)	Service is operating normally
	AWS CodePipeline (N. Virginia)	[RESOLVED] Increased API Error Rates     more  3:48 AM PDT We are investigating increased API error rates in the US-EAST-1 Region. 7:17 AM PDT We can confirm elevated error rates and latencies for the control plane in the US-EAST-1 Region. Customers will be unable to start new pipeline runs or create new pipelines. We are working towards resolution. 7:49 AM PDT We are seeing recovery on the API error rates for AWS CodePipeline in the US-EAST-1 region. We are continuing to work on full service recovery. 8:31 AM PDT Between 2:15 AM and 7:30 AM PDT we experienced increased API error rates and latencies in the US-EAST-1 Region. The issue has been resolved and the service is operating normally.
	AWS Config (N. California)	Service is operating normally
	AWS Config (N. Virginia)	[RESOLVED] Elevated API Error Rates and Latencies     more  3:39 AM PDT We are currently investigating increased error rates and latencies to AWS Config APIs in the us-east-1 Region. 5:49 AM PDT We can confirm increased error rates and latencies to AWS Config APIs in the US-EAST-1 Region and continue to work towards resolution. 7:57 AM PDT We can confirm recovery on the API error rates and latencies for AWS Config. We are continuing to work on full service recovery. 8:17 AM PDT Between 2:30 AM and 7:37 AM PDT customers experienced elevated error rates and latencies in the US-EAST-1 Region. The issue has been resolved and the service is operating normally.
	AWS Config (Oregon)	Service is operating normally
	AWS Data Pipeline (N. Virginia)	Service is operating normally
	AWS Data Pipeline (Oregon)	Service is operating normally
	AWS Device Farm (Oregon)	Service is operating normally
	AWS Direct Connect (N. California)	Service is operating normally
	AWS Direct Connect (N. Virginia)	Service is operating normally
	AWS Directory Service (N. Virginia)	[RESOLVED] Degraded Authentication Performance     more  3:51 AM PDT We are investigating degraded performance in authentication requests for directories in the US-EAST-1 Region. 4:35 AM PDT We have confirmed continued elevated error rates in authentication requests in the US-EAST-1 region, and continue to work towards resolution. 8:21 AM PDT Between 2:13 AM and 8:15 AM we experienced increased error rates for authentications in the US-EAST-1 Region. The issue has been resolved and the service is operating normally.
	AWS Directory Service (Oregon)	Service is operating normally
	AWS Elastic Beanstalk (N. California)	Service is operating normally
	AWS Elastic Beanstalk (N. Virginia)	[RESOLVED] Elevated API Error Rates and Latencies     more  4:17 AM PDT We are investigating increased error rates and latencies for the AWS Elastic Beanstalk APIs in the US-EAST-1 Region. 5:12 AM PDT We can confirm increased error rates and elevated latencies for all APIs in the US-EAST-1 Region and continue to work towards resolution. 5:38 AM PDT We can confirm significant error rates in the US-EAST-1 Region and continue to work towards resolution. 8:23 AM PDT We can confirm recovery on the API error rates and latencies. We are making progress working through the remaining workflows. 11:02 AM PDT Between 2:30 AM and 10:58 AM PDT, customers experienced elevated API error rates and latencies in the US-EAST-1 Region. Environment launch, terminate and scale operations were severely delayed or failing during this period of time. The issue has been resolved and the service is operating normally.
	AWS Elastic Beanstalk (Oregon)	Service is operating normally
	AWS Identity and Access Management (N. California)	Service is operating normally
	AWS Identity and Access Management (N. Virginia)	Service is operating normally
	AWS Identity and Access Management (Oregon)	Service is operating normally
	AWS Import/Export	Service is operating normally
	AWS Key Management Service (N. California)	Service is operating normally
	AWS Key Management Service (N. Virginia)	[RESOLVED] Increased Error Rates     more  4:18 AM PDT We are investigating elevated error rates for API requests in the US-EAST-1 region. 4:43 AM PDT KMS is experiencing elevated error rates for APIs related to managing keys (such as CreateKey). APIs related to using keys (such as Encrypt and Decrypt) are experiencing elevated latencies, but are completing successfully. We are working to correct the issue. 7:10 AM PDT APIs related to managing keys continue to have significantly elevated error rates. APIs related to using keys are experiencing elevated latencies, but are completing successfully. We continue to work towards service restoration. 7:52 AM PDT API error rates and latencies have decreased and are trending towards normal. 8:14 AM PDT Between 2:13 AM PDT and 7:29 AM PDT, KMS APIs related to managing keys experienced elevated error rates, and APIs related to using keys experienced elevated latencies. At this time the service is operating normally.
	AWS Key Management Service (Oregon)	Service is operating normally
	AWS Lambda (N. Virginia)	[RESOLVED] Increased API Error Rates     more  3:53 AM PDT We are investigating increased API error rates in the US-EAST-1 Region. 4:04 AM PDT AWS Lambda is experiencing increased faults and latency in the US-EAST-1 Region. We are actively working on resolving the issue. 5:30 AM PDT We can confirm increased API faults and elevated latencies in the US-EAST-1 Region and are working towards resolution. 6:15 AM PDT We can confirm increased error rates for invoke API calls in the US-EAST-1 Region. Function creation and the AWS Lambda console are also affected. Processing of DynamoDB and Kinesis events are experiencing highly elevated latencies. We have identified the cause and are actively working on resolving this issue. 8:49 AM PDT We are seeing a reduction in API error rates for all APIs in the US-EAST-1 Region. Customers may still experience elevated fault rates and latencies as we continue to restore full service functionality. 10:17 AM PDT We have resolved the issue causing elevated API error rates. We are rapidly completing the processing of events delayed during the service interruption. 10:55 AM PDT Between 2:15 AM and 10:52 AM PDT, AWS Lambda experienced significantly elevated API failures and latencies in the US-EAST-1 Region. We identified the root cause, the error has been corrected, and the service is operating normally. Events delayed during the service interruption are being processed now.
	AWS Lambda (Oregon)	Service is operating normally
	AWS Management Console	[RESOLVED] Elevated login error rates     more  6:31 AM PDT We are currently experiencing elevated error rates affecting customers logging into the Console. Customers who have already logged into the Console are not affected. 7:55 AM PDT We are seeing recovery on the error rates affecting customers logging into the Console. Customers who have already logged into the Console are not affected. 8:14 AM PDT Between 06:01 AM and 07:15 AM PDT, the AWS Management Console experienced elevated error rates affecting customers logging into the Console. The issue has been resolved and the AWS Management Console is now operating normally.
	AWS OpsWorks (N. Virginia)	[RESOLVED] Increased API error rates     more  3:14 AM PDT We are investigating increased error rates for API requests and instance commands. 6:34 AM PDT We can confirm a significant increase in error rates for API requests and instance commands. We are actively working to resolve the issue. 7:46 AM PDT We are beginning to see recovery for API requests and instance commands. 8:51 AM PDT Between 2:34 PDT and 8:29 PDT, we experienced elevated errors for API requests and instance commands. This issue has been resolved and the service is now operating normally.
	AWS Service Catalog (N. Virginia)	Service is operating normally
	AWS Service Catalog (Oregon)	Service is operating normally
	AWS Storage Gateway (N. California)	Service is operating normally
	AWS Storage Gateway (N. Virginia)	[RESOLVED] Elevated Snapshot and Console Error Rates     more  4:36 AM PDT We are currently investigating elevated error rates for Snapshot updates in US-East-1 that began at 2:40 am PDT. 5:16 AM PDT We are continuing to investigate elevated error rates for Snapshot updates in US-East-1 that began at 2:40 am PDT. 6:47 AM PDT We are continuing to investigate elevated error rates for Snapshot updates US-East-1 that began at 2:40 am PDT as well as Console errors that began at 5:50 am PDT. 7:33 AM PDT We are continuing to investigate elevated error rates for Snapshot updates US-East-1 that began at 2:40 PDT. Console errors that began at 5:50 PDT have been resolved as of 7:10 PDT. 8:03 AM PDT Between 2:40 PDT and 7:30 PDT, we experienced elevated Snapshot error rates. This issue has been resolved and the service is operating normally. Console errors that began at 5:50 PDT have been resolved as of 7:10 PDT.
	AWS Storage Gateway (Oregon)	Service is operating normally

Current Status		Details	RSS
	Amazon CloudFront	Service is operating normally
	Amazon CloudSearch (Sao Paulo)	Service is operating normally
	Amazon CloudWatch (Sao Paulo)	Service is operating normally
	Amazon DynamoDB (Sao Paulo)	Service is operating normally
	Amazon Elastic Compute Cloud (Sao Paulo)	Service is operating normally
	Amazon Elastic Load Balancing (Sao Paulo)	Service is operating normally
	Amazon Elastic MapReduce (Sao Paulo)	Service is operating normally
	Amazon ElastiCache (Sao Paulo)	Service is operating normally
	Amazon Relational Database Service (Sao Paulo)	Service is operating normally
	Amazon Route 53	Service is operating normally
	Amazon Route 53 Private DNS (Sao Paulo)	Service is operating normally
	Amazon Simple Notification Service (Sao Paulo)	Service is operating normally
	Amazon Simple Queue Service (Sao Paulo)	Service is operating normally
	Amazon Simple Storage Service (Sao Paulo)	Service is operating normally
	Amazon Simple Workflow Service (Sao Paulo)	Service is operating normally
	Amazon SimpleDB (Sao Paulo)	Service is operating normally
	Amazon Virtual Private Cloud (Sao Paulo)	Service is operating normally
	Auto Scaling (Sao Paulo)	Service is operating normally
	AWS CloudFormation (Sao Paulo)	Service is operating normally
	AWS CloudTrail (Sao Paulo)	Service is operating normally
	AWS Config (Sao Paulo)	Service is operating normally
	AWS Direct Connect (Sao Paulo)	Service is operating normally
	AWS Elastic Beanstalk (Sao Paulo)	Service is operating normally
	AWS Identity and Access Management (Sao Paulo)	Service is operating normally
	AWS Key Management Service (Sao Paulo)	Service is operating normally
	AWS Management Console	[RESOLVED] Elevated login error rates     more  6:31 AM PDT We are currently experiencing elevated error rates affecting customers logging into the Console. Customers who have already logged into the Console are not affected. 7:55 AM PDT We are seeing recovery on the error rates affecting customers logging into the Console. Customers who have already logged into the Console are not affected. 8:14 AM PDT Between 06:01 AM and 07:15 AM PDT, the AWS Management Console experienced elevated error rates affecting customers logging into the Console. The issue has been resolved and the AWS Management Console is now operating normally.
	AWS Storage Gateway (Sao Paulo)	Service is operating normally

Current Status		Details	RSS
	Amazon API Gateway (Ireland)	Service is operating normally
	Amazon CloudFront	Service is operating normally
	Amazon CloudSearch (Frankfurt)	Service is operating normally
	Amazon CloudSearch (Ireland)	Service is operating normally
	Amazon CloudWatch (Frankfurt)	Service is operating normally
	Amazon CloudWatch (Ireland)	Service is operating normally
	Amazon Cognito (Ireland)	Service is operating normally
	Amazon DynamoDB (Frankfurt)	Service is operating normally
	Amazon DynamoDB (Ireland)	Service is operating normally
	Amazon EC2 Container Service (Ireland)	Service is operating normally
	Amazon Elastic Compute Cloud (Frankfurt)	Service is operating normally
	Amazon Elastic Compute Cloud (Ireland)	Service is operating normally
	Amazon Elastic Load Balancing (Frankfurt)	Service is operating normally
	Amazon Elastic Load Balancing (Ireland)	Service is operating normally
	Amazon Elastic MapReduce (Frankfurt)	Service is operating normally
	Amazon Elastic MapReduce (Ireland)	Service is operating normally
	Amazon Elastic Transcoder (Ireland)	Service is operating normally
	Amazon ElastiCache (Frankfurt)	Service is operating normally
	Amazon ElastiCache (Ireland)	Service is operating normally
	Amazon Glacier (Frankfurt)	Service is operating normally
	Amazon Glacier (Ireland)	Service is operating normally
	Amazon Kinesis (Frankfurt)	Service is operating normally
	Amazon Kinesis (Ireland)	Service is operating normally
	Amazon Machine Learning (Ireland)	Service is operating normally
	Amazon Redshift (Frankfurt)	Service is operating normally
	Amazon Redshift (Ireland)	Service is operating normally
	Amazon Relational Database Service (Frankfurt)	Service is operating normally
	Amazon Relational Database Service (Ireland)	Service is operating normally
	Amazon Route 53	Service is operating normally
	Amazon Route 53 Private DNS (Ireland)	Service is operating normally
	Amazon Simple Email Service (Ireland)	Service is operating normally
	Amazon Simple Notification Service (Frankfurt)	Service is operating normally
	Amazon Simple Notification Service (Ireland)	Service is operating normally
	Amazon Simple Queue Service (Frankfurt)	Service is operating normally
	Amazon Simple Queue Service (Ireland)	Service is operating normally
	Amazon Simple Storage Service (Frankfurt)	Service is operating normally
	Amazon Simple Storage Service (Ireland)	Service is operating normally
	Amazon Simple Workflow Service (Frankfurt)	Service is operating normally
	Amazon Simple Workflow Service (Ireland)	Service is operating normally
	Amazon SimpleDB (Ireland)	Service is operating normally
	Amazon Virtual Private Cloud (Frankfurt)	Service is operating normally
	Amazon Virtual Private Cloud (Ireland)	Service is operating normally
	Amazon WorkDocs (Ireland)	Service is operating normally
	Amazon WorkSpaces (Ireland)	Service is operating normally
	Auto Scaling (Frankfurt)	Service is operating normally
	Auto Scaling (Ireland)	Service is operating normally
	AWS CloudFormation (Frankfurt)	Service is operating normally
	AWS CloudFormation (Ireland)	Service is operating normally
	AWS CloudHSM (Frankfurt)	Service is operating normally
	AWS CloudHSM (Ireland)	Service is operating normally
	AWS CloudTrail (Frankfurt)	Service is operating normally
	AWS CloudTrail (Ireland)	Service is operating normally
	AWS CodeDeploy (Ireland)	Service is operating normally
	AWS Config (Frankfurt)	Service is operating normally
	AWS Config (Ireland)	Service is operating normally
	AWS Data Pipeline (Ireland)	Service is operating normally
	AWS Direct Connect (Frankfurt)	Service is operating normally
	AWS Direct Connect (Ireland)	Service is operating normally
	AWS Directory Service (Ireland)	Service is operating normally
	AWS Elastic Beanstalk (Frankfurt)	Service is operating normally
	AWS Elastic Beanstalk (Ireland)	Service is operating normally
	AWS Identity and Access Management (Frankfurt)	Service is operating normally
	AWS Identity and Access Management (Ireland)	Service is operating normally
	AWS Import/Export	Service is operating normally
	AWS Key Management Service (Frankfurt)	Service is operating normally
	AWS Key Management Service (Ireland)	Service is operating normally
	AWS Lambda (Ireland)	Service is operating normally
	AWS Management Console	[RESOLVED] Elevated login error rates     more  6:31 AM PDT We are currently experiencing elevated error rates affecting customers logging into the Console. Customers who have already logged into the Console are not affected. 7:55 AM PDT We are seeing recovery on the error rates affecting customers logging into the Console. Customers who have already logged into the Console are not affected. 8:14 AM PDT Between 06:01 AM and 07:15 AM PDT, the AWS Management Console experienced elevated error rates affecting customers logging into the Console. The issue has been resolved and the AWS Management Console is now operating normally.
	AWS Storage Gateway (Frankfurt)	Service is operating normally
	AWS Storage Gateway (Ireland)	Service is operating normally

Current Status		Details	RSS
	Amazon CloudFront	Service is operating normally
	Amazon CloudSearch (Singapore)	Service is operating normally
	Amazon CloudSearch (Sydney)	Service is operating normally
	Amazon CloudSearch (Tokyo)	Service is operating normally
	Amazon CloudWatch (Singapore)	Service is operating normally
	Amazon CloudWatch (Sydney)	Service is operating normally
	Amazon CloudWatch (Tokyo)	Service is operating normally
	Amazon DynamoDB (Singapore)	Service is operating normally
	Amazon DynamoDB (Sydney)	Service is operating normally
	Amazon DynamoDB (Tokyo)	Service is operating normally
	Amazon EC2 Container Service (Sydney)	Service is operating normally
	Amazon EC2 Container Service (Tokyo)	Service is operating normally
	Amazon Elastic Compute Cloud (Singapore)	Service is operating normally
	Amazon Elastic Compute Cloud (Sydney)	Service is operating normally
	Amazon Elastic Compute Cloud (Tokyo)	Service is operating normally
	Amazon Elastic Load Balancing (Singapore)	Service is operating normally
	Amazon Elastic Load Balancing (Sydney)	Service is operating normally
	Amazon Elastic Load Balancing (Tokyo)	Service is operating normally
	Amazon Elastic MapReduce (Singapore)	Service is operating normally
	Amazon Elastic MapReduce (Sydney)	Service is operating normally
	Amazon Elastic MapReduce (Tokyo)	Service is operating normally
	Amazon Elastic Transcoder (Singapore)	Service is operating normally
	Amazon Elastic Transcoder (Tokyo)	Service is operating normally
	Amazon ElastiCache (Singapore)	Service is operating normally
	Amazon ElastiCache (Sydney)	Service is operating normally
	Amazon ElastiCache (Tokyo)	Service is operating normally
	Amazon Glacier (Sydney)	Service is operating normally
	Amazon Glacier (Tokyo)	Service is operating normally
	Amazon Kinesis (Singapore)	Service is operating normally
	Amazon Kinesis (Sydney)	Service is operating normally
	Amazon Kinesis (Tokyo)	Service is operating normally
	Amazon Redshift (Singapore)	Service is operating normally
	Amazon Redshift (Sydney)	Service is operating normally
	Amazon Redshift (Tokyo)	Service is operating normally
	Amazon Relational Database Service (Singapore)	Service is operating normally
	Amazon Relational Database Service (Sydney)	Service is operating normally
	Amazon Relational Database Service (Tokyo)	Service is operating normally
	Amazon Route 53	Service is operating normally
	Amazon Route 53 Private DNS (Singapore)	Service is operating normally
	Amazon Route 53 Private DNS (Sydney)	Service is operating normally
	Amazon Route 53 Private DNS (Tokyo)	Service is operating normally
	Amazon Simple Notification Service (Singapore)	Service is operating normally
	Amazon Simple Notification Service (Sydney)	Service is operating normally
	Amazon Simple Notification Service (Tokyo)	Service is operating normally
	Amazon Simple Queue Service (Singapore)	Service is operating normally
	Amazon Simple Queue Service (Sydney)	Service is operating normally
	Amazon Simple Queue Service (Tokyo)	Service is operating normally
	Amazon Simple Storage Service (Singapore)	Service is operating normally
	Amazon Simple Storage Service (Sydney)	Service is operating normally
	Amazon Simple Storage Service (Tokyo)	Service is operating normally
	Amazon Simple Workflow Service (Singapore)	Service is operating normally
	Amazon Simple Workflow Service (Sydney)	Service is operating normally
	Amazon Simple Workflow Service (Tokyo)	Service is operating normally
	Amazon SimpleDB (Singapore)	Service is operating normally
	Amazon SimpleDB (Sydney)	Service is operating normally
	Amazon SimpleDB (Tokyo)	Service is operating normally
	Amazon Virtual Private Cloud (Singapore)	Service is operating normally
	Amazon Virtual Private Cloud (Sydney)	Service is operating normally
	Amazon Virtual Private Cloud (Tokyo)	Service is operating normally
	Amazon WorkDocs (Singapore)	Service is operating normally
	Amazon WorkDocs (Sydney)	Service is operating normally
	Amazon WorkDocs (Tokyo)	Service is operating normally
	Amazon WorkSpaces (Singapore)	Service is operating normally
	Amazon WorkSpaces (Sydney)	Service is operating normally
	Amazon WorkSpaces (Tokyo)	Service is operating normally
	Auto Scaling (Singapore)	Service is operating normally
	Auto Scaling (Sydney)	Service is operating normally
	Auto Scaling (Tokyo)	Service is operating normally
	AWS CloudFormation (Singapore)	Service is operating normally
	AWS CloudFormation (Sydney)	Service is operating normally
	AWS CloudFormation (Tokyo)	Service is operating normally
	AWS CloudHSM (Singapore)	Service is operating normally
	AWS CloudHSM (Sydney)	Service is operating normally
	AWS CloudHSM (Tokyo)	Service is operating normally
	AWS CloudTrail (Singapore)	Service is operating normally
	AWS CloudTrail (Sydney)	Service is operating normally
	AWS CloudTrail (Tokyo)	Service is operating normally
	AWS CodeDeploy (Sydney)	Service is operating normally
	AWS CodeDeploy (Tokyo)	Service is operating normally
	AWS Config (Singapore)	Service is operating normally
	AWS Config (Sydney)	Service is operating normally
	AWS Config (Tokyo)	Service is operating normally
	AWS Data Pipeline (Sydney)	Service is operating normally
	AWS Data Pipeline (Tokyo)	Service is operating normally
	AWS Direct Connect (Singapore)	Service is operating normally
	AWS Direct Connect (Sydney)	Service is operating normally
	AWS Direct Connect (Tokyo)	Service is operating normally
	AWS Directory Service (Singapore)	Service is operating normally
	AWS Directory Service (Sydney)	Service is operating normally
	AWS Directory Service (Tokyo)	Service is operating normally
	AWS Elastic Beanstalk (Singapore)	Service is operating normally
	AWS Elastic Beanstalk (Sydney)	Service is operating normally
	AWS Elastic Beanstalk (Tokyo)	Service is operating normally
	AWS Identity and Access Management (Singapore)	Service is operating normally
	AWS Identity and Access Management (Sydney)	Service is operating normally
	AWS Identity and Access Management (Tokyo)	Service is operating normally
	AWS Import/Export	Service is operating normally
	AWS Key Management Service (Singapore)	Service is operating normally
	AWS Key Management Service (Sydney)	Service is operating normally
	AWS Key Management Service (Tokyo)	Service is operating normally
	AWS Management Console	[RESOLVED] Elevated login error rates     more  6:31 AM PDT We are currently experiencing elevated error rates affecting customers logging into the Console. Customers who have already logged into the Console are not affected. 7:55 AM PDT We are seeing recovery on the error rates affecting customers logging into the Console. Customers who have already logged into the Console are not affected. 8:14 AM PDT Between 06:01 AM and 07:15 AM PDT, the AWS Management Console experienced elevated error rates affecting customers logging into the Console. The issue has been resolved and the AWS Management Console is now operating normally.
	AWS Storage Gateway (Singapore)	Service is operating normally
	AWS Storage Gateway (Sydney)	Service is operating normally
	AWS Storage Gateway (Tokyo)	Service is operating normally

Service is operating normally

Performance issues

Service disruption

Informational message

Status History

Amazon Web Services keeps a running log of all service interruptions that we publish in the table below for the past year. Mouse over any of the status icons below to see a detailed incident report (click on the icon to persist the popup). Click on the arrow buttons at the top of the table to move forward and backwards through the calendar. All dates and times are Pacific Time (PST/PDT).

• North America
• South America
• Europe
• Asia Pacific

Amazon API Gateway (N. Virginia) Amazon API Gateway (Oregon) Amazon AppStream (N. Virginia) Amazon CloudFront Amazon CloudSearch (N. California) Amazon CloudSearch (N. Virginia) Amazon CloudSearch (Oregon) Amazon CloudWatch (N. California) Amazon CloudWatch (N. Virginia) Amazon CloudWatch (Oregon) Amazon Cognito (N. Virginia) Amazon DynamoDB (N. California) Amazon DynamoDB (N. Virginia) Amazon DynamoDB (Oregon) Amazon ECS (N. California) Amazon ECS (N. Virginia) Amazon ECS (Oregon) EC2 (N. California) EC2 (N. Virginia) EC2 (Oregon) ELB (N. California) ELB (N. Virginia) ELB (Oregon) EMR (N. California) EMR (N. Virginia) EMR (Oregon) Amazon Elastic Transcoder (N. California) Amazon Elastic Transcoder (N. Virginia) Amazon Elastic Transcoder (Oregon) Amazon ElastiCache (N. California) Amazon ElastiCache (N. Virginia) Amazon ElastiCache (Oregon) Amazon Glacier (N. California) Amazon Glacier (N. Virginia) Amazon Glacier (Oregon) Amazon Kinesis (N. California) Amazon Kinesis (N. Virginia) Amazon Kinesis (Oregon) Amazon Machine Learning (N. Virginia) Amazon Mobile Analytics (N. Virginia) Amazon Redshift (N. Virginia) Amazon Redshift (Oregon) RDS (N. California) RDS (N. Virginia) RDS (Oregon) Amazon Route 53 Amazon Route 53 Private DNS (N. California) Amazon Route 53 Private DNS (N. Virginia) Amazon Route 53 Private DNS (Oregon) Amazon Simple Email Service (N. Virginia) Amazon Simple Email Service (Oregon) SNS (N. California) SNS (N. Virginia) SNS (Oregon) SQS (N. California) SQS (N. Virginia) SQS (Oregon) S3 (N. California) S3 (Oregon) S3 (US Standard) SWF (N. California) SWF (N. Virginia) SWF (Oregon) Amazon SimpleDB (N. California) Amazon SimpleDB (N. Virginia) Amazon SimpleDB (Oregon) VPC (N. California) VPC (N. Virginia) VPC (Oregon) Amazon WorkDocs (N. Virginia) Amazon WorkDocs (Oregon) Amazon WorkSpaces (N. Virginia) Amazon WorkSpaces (Oregon) Auto Scaling (N. California) Auto Scaling (N. Virginia) Auto Scaling (Oregon) AWS CloudFormation (N. California) AWS CloudFormation (N. Virginia) AWS CloudFormation (Oregon) AWS CloudHSM (N. Virginia) AWS CloudHSM (Oregon) AWS CloudTrail (N. California) AWS CloudTrail (N. Virginia) AWS CloudTrail (Oregon) AWS CodeCommit (N. Virginia) AWS CodeDeploy (N. Virginia) AWS CodeDeploy (Oregon) AWS CodePipeline (N. Virginia) AWS Config (N. California) AWS Config (N. Virginia) AWS Config (Oregon) AWS Data Pipeline (N. Virginia) AWS Data Pipeline (Oregon) AWS Device Farm (Oregon) AWS Direct Connect (N. California) AWS Direct Connect (N. Virginia) AWS Directory Service (N. Virginia) AWS Directory Service (Oregon) AWS Elastic Beanstalk (N. California) AWS Elastic Beanstalk (N. Virginia) AWS Elastic Beanstalk (Oregon) AWS IAM (N. California) AWS IAM (N. Virginia) AWS IAM (Oregon) AWS Import/Export AWS Key Management Service (N. California) AWS Key Management Service (N. Virginia) AWS Key Management Service (Oregon) AWS Lambda (N. Virginia) AWS Lambda (Oregon) AWS Management Console AWS OpsWorks (N. Virginia) AWS Service Catalog (N. Virginia) AWS Service Catalog (Oregon) AWS Storage Gateway (N. California) AWS Storage Gateway (N. Virginia) AWS Storage Gateway (Oregon)

Sep 19 Sep 18 Sep 17 Sep 16 Sep 15 Sep 14 Sep 13 [RESOLVED] DescribeInstanceStatus API Errors / Network Connectivity DescribeInstanceStatus API Errors 3:07 PM PDT We are investigating increased error rates for the DescribeInstanceStatus API in the US-EAST-1 Region. 3:36 PM PDT We can confirm increased error rates for the DescribeInstanceStatus API in the US-EAST-1 Region and are working to resolve this issue. 4:15 PM PDT We are continuing to work to resolve increased error rates for the DescribeInstanceStatus API. Because of these error rates, the AWS Management Console is reporting "Unable to describe instance status" and alarms based on instance health status may be incorrectly triggered. This issue impacts the reporting of instance status using this API, however instances are healthy and operating normally. New instance launches are also operating normally. 5:29 PM PDT We have identified the root cause of the issue causing elevated error rates for the DescribeInstanceStatus API and are working to resolve the issue. This issue impacts the reporting of instance status using this API, however instances are healthy and operating normally. New instance launches are also operating normally. 5:49 PM PDT Between 2:41 PM and 5:34 PM PDT we experienced elevated error rates for the DescribeInstanceStatus API in the US-EAST-1 Region. This API is now operating normally. Instances were healthy and operating normally throughout this event. Network Connectivity 10:00 PM PDT We are investigating connectivity issues for newly launched instances and increased Elastic IP mapping latencies in a single Availability Zone in the US-EAST-1 Region. 10:32 PM PDT We have identified the root cause of the issue affecting connectivity for newly launched instances and increased Elastic IP mapping latencies in a single Availability Zone in the US-EAST-1 Region, and are working on resolving the issue. 11:27 PM PDT We continue to work on resolving the issue affecting connectivity for newly launched instances and increased Elastic IP mapping latencies in a single Availability Zone in the US-EAST-1 Region. Instances in other Availability Zones as well as existing instances in the affected Availability Zone are not impacted by this event. The AWS Management Console has been updated to indicate which Availability Zone is experiencing the issue. Sep 18, 12:20 AM PDT Between 7:35 PM and 11:55 PM PDT we experienced connectivity issues for newly launched instances and increased Elastic IP mapping latencies in a single Availability Zone in the US-EAST-1 Region. Instances in other Availability Zones as well as existing instances in the affected Availability Zone were not impacted by this event. The issue has been resolved and the service is operating normally. [RESOLVED] Intermittent API Latency 10:03 PM PDT We are investigating a brief hourly API latency increase for ReceiveMessage API calls in the US-EAST-1 Region. 11:01 PM PDT We continue to investigate brief hourly API latency increases for ReceiveMessage API calls in the US-EAST-1 Region. The service is operating normally outside of these periods. Sep 15, 12:15 AM PDT We continue to experience brief hourly API latency increases for ReceiveMessage API calls in the US-EAST-1 Region and are actively working to resolve the issue. The service is operating normally outside of these periods. Sep 15, 1:57 AM PDT We continue to experience brief hourly API latency increases for ReceiveMessage API calls in the US-EAST-1 Region. We have identified the cause, and are actively working to resolve the issue. The service is operating normally outside of these periods. Sep 15, 3:25 AM PDT Between Sept 14th 4:09 PM and Sept 15 2:16 AM PDT, SQS experienced short periods of increased API error rates and latencies for the ReceiveMessage API in the US-EAST-1 Region. The service is now operating normally. [RESOLVED] Increased Deployment Error Rates 3:34 PM PDT We are experiencing increased deployment error rates in the US-EAST-1 Region. 4:21 PM PDT We can confirm and continue to investigate increased deployment error rates related to the EC2 DescribeInstanceStatus API event in the US-EAST-1 Region. 5:32 PM PDT We can confirm increased deployment error rates related to the EC2 DescribeInstanceStatus API event in the US-EAST-1 Region and continue working to resolve the issue. 5:50 PM PDT Between 2:41 PM and 5:34 PM PDT we experienced an increased error rate while executing deployments in the US-EAST-1 Region. The issue has been resolved and the service is operating normally.

Amazon CloudFront Amazon CloudSearch (Sao Paulo) Amazon CloudWatch (Sao Paulo) Amazon DynamoDB (Sao Paulo) EC2 (Sao Paulo) ELB (Sao Paulo) EMR (Sao Paulo) Amazon ElastiCache (Sao Paulo) RDS (Sao Paulo) Amazon Route 53 Amazon Route 53 Private DNS (Sao Paulo) SNS (Sao Paulo) SQS (Sao Paulo) S3 (Sao Paulo) SWF (Sao Paulo) Amazon SimpleDB (Sao Paulo) VPC (Sao Paulo) Auto Scaling (Sao Paulo) AWS CloudFormation (Sao Paulo) AWS CloudTrail (Sao Paulo) AWS Config (Sao Paulo) AWS Direct Connect (Sao Paulo) AWS Elastic Beanstalk (Sao Paulo) AWS IAM (Sao Paulo) AWS Key Management Service (Sao Paulo) AWS Management Console AWS Storage Gateway (Sao Paulo)

Sep 19 Sep 18 Sep 17 Sep 16 Sep 15 Sep 14 Sep 13

Amazon API Gateway (Ireland) Amazon CloudFront Amazon CloudSearch (Frankfurt) Amazon CloudSearch (Ireland) Amazon CloudWatch (Frankfurt) Amazon CloudWatch (Ireland) Amazon Cognito (Ireland) Amazon DynamoDB (Frankfurt) Amazon DynamoDB (Ireland) Amazon ECS (Ireland) EC2 (Frankfurt) EC2 (Ireland) ELB (Frankfurt) ELB (Ireland) EMR (Frankfurt) EMR (Ireland) Amazon Elastic Transcoder (Ireland) Amazon ElastiCache (Frankfurt) Amazon ElastiCache (Ireland) Amazon Glacier (Frankfurt) Amazon Glacier (Ireland) Amazon Kinesis (Frankfurt) Amazon Kinesis (Ireland) Amazon Machine Learning (Ireland) Amazon Redshift (Frankfurt) Amazon Redshift (Ireland) RDS (Frankfurt) RDS (Ireland) Amazon Route 53 Amazon Route 53 Private DNS (Ireland) Amazon Simple Email Service (Ireland) SNS (Frankfurt) SNS (Ireland) SQS (Frankfurt) SQS (Ireland) S3 (Frankfurt) S3 (Ireland) SWF (Frankfurt) SWF (Ireland) Amazon SimpleDB (Ireland) VPC (Frankfurt) VPC (Ireland) Amazon WorkDocs (Ireland) Amazon WorkSpaces (Ireland) Auto Scaling (Frankfurt) Auto Scaling (Ireland) AWS CloudFormation (Frankfurt) AWS CloudFormation (Ireland) AWS CloudHSM (Frankfurt) AWS CloudHSM (Ireland) AWS CloudTrail (Frankfurt) AWS CloudTrail (Ireland) AWS CodeDeploy (Ireland) AWS Config (Frankfurt) AWS Config (Ireland) AWS Data Pipeline (Ireland) AWS Direct Connect (Frankfurt) AWS Direct Connect (Ireland) AWS Directory Service (Ireland) AWS Elastic Beanstalk (Frankfurt) AWS Elastic Beanstalk (Ireland) AWS IAM (Frankfurt) AWS IAM (Ireland) AWS Import/Export AWS Key Management Service (Frankfurt) AWS Key Management Service (Ireland) AWS Lambda (Ireland) AWS Management Console AWS Storage Gateway (Frankfurt) AWS Storage Gateway (Ireland)

Sep 19 Sep 18 Sep 17 Sep 16 Sep 15 Sep 14 Sep 13

Amazon CloudFront Amazon CloudSearch (Singapore) Amazon CloudSearch (Sydney) Amazon CloudSearch (Tokyo) Amazon CloudWatch (Singapore) Amazon CloudWatch (Sydney) Amazon CloudWatch (Tokyo) Amazon DynamoDB (Singapore) Amazon DynamoDB (Sydney) Amazon DynamoDB (Tokyo) Amazon ECS (Sydney) Amazon ECS (Tokyo) EC2 (Singapore) EC2 (Sydney) EC2 (Tokyo) ELB (Singapore) ELB (Sydney) ELB (Tokyo) EMR (Singapore) EMR (Sydney) EMR (Tokyo) Amazon Elastic Transcoder (Singapore) Amazon Elastic Transcoder (Tokyo) Amazon ElastiCache (Singapore) Amazon ElastiCache (Sydney) Amazon ElastiCache (Tokyo) Amazon Glacier (Sydney) Amazon Glacier (Tokyo) Amazon Kinesis (Singapore) Amazon Kinesis (Sydney) Amazon Kinesis (Tokyo) Amazon Redshift (Singapore) Amazon Redshift (Sydney) Amazon Redshift (Tokyo) RDS (Singapore) RDS (Sydney) RDS (Tokyo) Amazon Route 53 Amazon Route 53 Private DNS (Singapore) Amazon Route 53 Private DNS (Sydney) Amazon Route 53 Private DNS (Tokyo) SNS (Singapore) SNS (Sydney) SNS (Tokyo) SQS (Singapore) SQS (Sydney) SQS (Tokyo) S3 (Singapore) S3 (Sydney) S3 (Tokyo) SWF (Singapore) SWF (Sydney) SWF (Tokyo) Amazon SimpleDB (Singapore) Amazon SimpleDB (Sydney) Amazon SimpleDB (Tokyo) VPC (Singapore) VPC (Sydney) VPC (Tokyo) Amazon WorkDocs (Singapore) Amazon WorkDocs (Sydney) Amazon WorkDocs (Tokyo) Amazon WorkSpaces (Singapore) Amazon WorkSpaces (Sydney) Amazon WorkSpaces (Tokyo) Auto Scaling (Singapore) Auto Scaling (Sydney) Auto Scaling (Tokyo) AWS CloudFormation (Singapore) AWS CloudFormation (Sydney) AWS CloudFormation (Tokyo) AWS CloudHSM (Singapore) AWS CloudHSM (Sydney) AWS CloudHSM (Tokyo) AWS CloudTrail (Singapore) AWS CloudTrail (Sydney) AWS CloudTrail (Tokyo) AWS CodeDeploy (Sydney) AWS CodeDeploy (Tokyo) AWS Config (Singapore) AWS Config (Sydney) AWS Config (Tokyo) AWS Data Pipeline (Sydney) AWS Data Pipeline (Tokyo) AWS Direct Connect (Singapore) AWS Direct Connect (Sydney) AWS Direct Connect (Tokyo) AWS Directory Service (Singapore) AWS Directory Service (Sydney) AWS Directory Service (Tokyo) AWS Elastic Beanstalk (Singapore) AWS Elastic Beanstalk (Sydney) AWS Elastic Beanstalk (Tokyo) AWS IAM (Singapore) AWS IAM (Sydney) AWS IAM (Tokyo) AWS Import/Export AWS Key Management Service (Singapore) AWS Key Management Service (Sydney) AWS Key Management Service (Tokyo) AWS Management Console AWS Storage Gateway (Singapore) AWS Storage Gateway (Sydney) AWS Storage Gateway (Tokyo)

Sep 19 Sep 18 Sep 17 Sep 16 Sep 15 Sep 14 Sep 13