Get a personalized view of AWS service health

Current Status - Apr 20, 2021 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
• Africa
• Asia Pacific
• Middle East

Recent Events		Details	RSS
	No recent events.

Remaining Services		Details	RSS

Recent Events		Details	RSS
	No recent events.

Remaining Services		Details	RSS

Recent Events		Details	RSS
	No recent events.

Remaining Services		Details	RSS

Recent Events		Details	RSS
	No recent events.

Remaining Services		Details	RSS

Recent Events		Details	RSS
	No recent events.

Remaining Services		Details	RSS

Recent Events		Details	RSS
	No recent events.

Remaining Services		Details	RSS

Service is (probably) okay

It's broken but we'll blame you

We concede there is a problem

Service has been Googled

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
• Africa
• Asia Pacific
• Middle East

Alexa for Business (N. Virginia) Amazon API Gateway (Montreal) Amazon API Gateway (N. California) Amazon API Gateway (N. Virginia) Amazon API Gateway (Ohio) Amazon API Gateway (Oregon) Amazon AppFlow (Montreal) Amazon AppFlow (N. California) Amazon AppFlow (N. Virginia) Amazon AppFlow (Ohio) Amazon AppFlow (Oregon) Amazon AppStream 2.0 (N. Virginia) Amazon AppStream 2.0 (Oregon) Amazon Athena (Montreal) Amazon Athena (N. California) Amazon Athena (N. Virginia) Amazon Athena (Ohio) Amazon Athena (Oregon) Amazon Augmented AI (Montreal) Amazon Augmented AI (N. Virginia) Amazon Augmented AI (Ohio) Amazon Augmented AI (Oregon) Amazon Braket (N. California) Amazon Braket (N. Virginia) Amazon Braket (Oregon) Amazon Chime Amazon Cloud Directory (Montreal) Amazon Cloud Directory (N. Virginia) Amazon Cloud Directory (Ohio) Amazon Cloud Directory (Oregon) Amazon CloudFront Amazon CloudSearch (N. California) Amazon CloudSearch (N. Virginia) Amazon CloudSearch (Oregon) Amazon CloudWatch (Montreal) Amazon CloudWatch (N. California) Amazon CloudWatch (N. Virginia) Amazon CloudWatch (Ohio) Amazon CloudWatch (Oregon) Amazon CodeGuru Profiler (N. Virginia) Amazon CodeGuru Profiler (Ohio) Amazon CodeGuru Profiler (Oregon) Amazon CodeGuru Reviewer (N. Virginia) Amazon CodeGuru Reviewer (Ohio) Amazon CodeGuru Reviewer (Oregon) Amazon Cognito (Montreal) Amazon Cognito (N. California) Amazon Cognito (N. Virginia) Amazon Cognito (Ohio) Amazon Cognito (Oregon) Amazon Comprehend (Montreal) Amazon Comprehend (N. Virginia) Amazon Comprehend (Ohio) Amazon Comprehend (Oregon) Amazon Comprehend Medical (Montreal) Amazon Comprehend Medical (N. Virginia) Amazon Comprehend Medical (Ohio) Amazon Comprehend Medical (Oregon) Amazon Connect (Montreal) Amazon Connect (N. Virginia) Amazon Connect (Oregon) Amazon Data Lifecycle Manager (Montreal) Amazon Data Lifecycle Manager (N. California) Amazon Data Lifecycle Manager (N. Virginia) Amazon Data Lifecycle Manager (Ohio) Amazon Data Lifecycle Manager (Oregon) Amazon Detective (Montreal) Amazon Detective (N. California) Amazon Detective (N. Virginia) Amazon Detective (Ohio) Amazon Detective (Oregon) Amazon DocumentDB (Montreal) Amazon DocumentDB (N. Virginia) Amazon DocumentDB (Ohio) Amazon DocumentDB (Oregon) Amazon DynamoDB (Montreal) Amazon DynamoDB (N. California) Amazon DynamoDB (N. Virginia) Amazon DynamoDB (Ohio) Amazon DynamoDB (Oregon) EC2 (Montreal) EC2 (N. California) EC2 (N. Virginia) EC2 (Ohio) EC2 (Oregon) Amazon ECR (Montreal) Amazon ECR (N. California) Amazon ECR (N. Virginia) Amazon ECR (Ohio) Amazon ECR (Oregon) Amazon ECR Public Amazon ECS (Montreal) Amazon ECS (N. California) Amazon ECS (N. Virginia) Amazon ECS (Ohio) Amazon ECS (Oregon) Amazon Elastic File System (Montreal) Amazon Elastic File System (N. California) Amazon Elastic File System (N. Virginia) Amazon Elastic File System (Ohio) Amazon Elastic File System (Oregon) Amazon Elastic Kubernetes Service (Montreal) Amazon Elastic Kubernetes Service (N. California) Amazon Elastic Kubernetes Service (N. Virginia) Amazon Elastic Kubernetes Service (Ohio) Amazon Elastic Kubernetes Service (Oregon) ELB (Montreal) ELB (N. California) ELB (N. Virginia) ELB (Ohio) ELB (Oregon) EMR (Montreal) EMR (N. California) EMR (N. Virginia) EMR (Ohio) EMR (Oregon) Amazon ElastiCache (Montreal) Amazon ElastiCache (N. California) Amazon ElastiCache (N. Virginia) Amazon ElastiCache (Ohio) Amazon ElastiCache (Oregon) Amazon Elasticsearch Service (Montreal) Amazon Elasticsearch Service (N. California) Amazon Elasticsearch Service (N. Virginia) Amazon Elasticsearch Service (Ohio) Amazon Elasticsearch Service (Oregon) Amazon EventBridge (Montreal) Amazon EventBridge (N. California) Amazon EventBridge (N. Virginia) Amazon EventBridge (Ohio) Amazon EventBridge (Oregon) Amazon Forecast (N. Virginia) Amazon Forecast (Ohio) Amazon Forecast (Oregon) Amazon Fraud Detector (N. Virginia) Amazon Fraud Detector (Ohio) Amazon Fraud Detector (Oregon) Amazon FreeRTOS (Montreal) Amazon FreeRTOS (N. California) Amazon FreeRTOS (N. Virginia) Amazon FreeRTOS (Ohio) Amazon FreeRTOS (Oregon) Amazon FSx (Montreal) Amazon FSx (N. California) Amazon FSx (N. Virginia) Amazon FSx (Ohio) Amazon FSx (Oregon) Amazon GameLift (Montreal) Amazon GameLift (N. California) Amazon GameLift (N. Virginia) Amazon GameLift (Ohio) Amazon GameLift (Oregon) Amazon Glacier (Montreal) Amazon Glacier (N. California) Amazon Glacier (N. Virginia) Amazon Glacier (Ohio) Amazon Glacier (Oregon) Amazon GuardDuty (Montreal) Amazon GuardDuty (N. California) Amazon GuardDuty (N. Virginia) Amazon GuardDuty (Ohio) Amazon GuardDuty (Oregon) Amazon Inspector (N. California) Amazon Inspector (N. Virginia) Amazon Inspector (Ohio) Amazon Inspector (Oregon) Amazon Inter-Region VPC Peering Amazon Interactive Video Service (N. Virginia) Amazon Interactive Video Service (Oregon) Amazon Kendra (N. Virginia) Amazon Kendra (Oregon) Amazon Keyspaces (Montreal) Amazon Keyspaces (N. California) Amazon Keyspaces (N. Virginia) Amazon Keyspaces (Ohio) Amazon Keyspaces (Oregon) Amazon Kinesis Analytics (Montreal) Amazon Kinesis Analytics (N. California) Amazon Kinesis Analytics (N. Virginia) Amazon Kinesis Analytics (Ohio) Amazon Kinesis Analytics (Oregon) Amazon Kinesis Data Streams (Montreal) Amazon Kinesis Data Streams (N. California) Amazon Kinesis Data Streams (N. Virginia) Amazon Kinesis Data Streams (Ohio) Amazon Kinesis Data Streams (Oregon) Amazon Kinesis Firehose (Montreal) Amazon Kinesis Firehose (N. California) Amazon Kinesis Firehose (N. Virginia) Amazon Kinesis Firehose (Ohio) Amazon Kinesis Firehose (Oregon) Amazon Kinesis Video Streams (Montreal) Amazon Kinesis Video Streams (N. Virginia) Amazon Kinesis Video Streams (Ohio) Amazon Kinesis Video Streams (Oregon) Amazon Lex (N. Virginia) Amazon Lex (Oregon) Amazon Lightsail (Montreal) Amazon Lightsail (N. Virginia) Amazon Lightsail (Ohio) Amazon Lightsail (Oregon) Amazon Lookout for Metrics (N. Virginia) Amazon Lookout for Metrics (Ohio) Amazon Lookout for Metrics (Oregon) Amazon Lookout for Vision (N. Virginia) Amazon Lookout for Vision (Ohio) Amazon Lookout for Vision (Oregon) Amazon Machine Learning (N. Virginia) Amazon Macie (N. Virginia) Amazon Macie (Oregon) Amazon Managed Blockchain (N. Virginia) Amazon MSK (Montreal) Amazon MSK (N. California) Amazon MSK (N. Virginia) Amazon MSK (Ohio) Amazon MSK (Oregon) AWS Airflow (N. Virginia) AWS Airflow (Ohio) AWS Airflow (Oregon) Amazon Monitron (N. Virginia) Amazon MQ (Montreal) Amazon MQ (N. California) Amazon MQ (N. Virginia) Amazon MQ (Ohio) Amazon MQ (Oregon) Amazon Neptune (Montreal) Amazon Neptune (N. California) Amazon Neptune (N. Virginia) Amazon Neptune (Ohio) Amazon Neptune (Oregon) Amazon Personalize (Montreal) Amazon Personalize (N. Virginia) Amazon Personalize (Ohio) Amazon Personalize (Oregon) Amazon Pinpoint (Montreal) Amazon Pinpoint (N. Virginia) Amazon Pinpoint (Oregon) Amazon Polly (Montreal) Amazon Polly (N. California) Amazon Polly (N. Virginia) Amazon Polly (Ohio) Amazon Polly (Oregon) Amazon Quantum Ledger Database (N. Virginia) Amazon Quantum Ledger Database (Ohio) Amazon Quantum Ledger Database (Oregon) Amazon Redshift (Montreal) Amazon Redshift (N. California) Amazon Redshift (N. Virginia) Amazon Redshift (Ohio) Amazon Redshift (Oregon) Amazon Rekognition (Montreal) Amazon Rekognition (N. California) Amazon Rekognition (N. Virginia) Amazon Rekognition (Ohio) Amazon Rekognition (Oregon) RDS (Montreal) RDS (N. California) RDS (N. Virginia) RDS (Ohio) RDS (Oregon) Amazon Route 53 Amazon Route 53 Domain Registration Amazon Route 53 Private DNS (Montreal) Amazon Route 53 Private DNS (N. California) Amazon Route 53 Private DNS (N. Virginia) Amazon Route 53 Private DNS (Ohio) Amazon Route 53 Private DNS (Oregon) Amazon Route 53 Resolver (Montreal) Amazon Route 53 Resolver (N. California) Amazon Route 53 Resolver (N. Virginia) Amazon Route 53 Resolver (Ohio) Amazon Route 53 Resolver (Oregon) Amazon SageMaker (Montreal) Amazon SageMaker (N. California) Amazon SageMaker (N. Virginia) Amazon SageMaker (Ohio) Amazon SageMaker (Oregon) Amazon Simple Email Service (Montreal) Amazon Simple Email Service (N. California) Amazon Simple Email Service (N. Virginia) Amazon Simple Email Service (Ohio) Amazon Simple Email Service (Oregon) SNS (Montreal) SNS (N. California) SNS (N. Virginia) SNS (Ohio) SNS (Oregon) SQS (Montreal) SQS (N. California) SQS (N. Virginia) SQS (Ohio) SQS (Oregon) S3 (Montreal) S3 (N. California) S3 (N. Virginia) S3 (Ohio) S3 (Oregon) SWF (Montreal) SWF (N. California) SWF (N. Virginia) SWF (Ohio) SWF (Oregon) Amazon SimpleDB (N. California) Amazon SimpleDB (N. Virginia) Amazon SimpleDB (Oregon) Amazon Sumerian (Montreal) Amazon Sumerian (N. California) Amazon Sumerian (N. Virginia) Amazon Sumerian (Ohio) Amazon Sumerian (Oregon) Amazon Textract (Montreal) Amazon Textract (N. California) Amazon Textract (N. Virginia) Amazon Textract (Ohio) Amazon Textract (Oregon) Amazon Timestream (N. Virginia) Amazon Timestream (Ohio) Amazon Timestream (Oregon) Amazon Transcribe (Montreal) Amazon Transcribe (N. California) Amazon Transcribe (N. Virginia) Amazon Transcribe (Ohio) Amazon Transcribe (Oregon) Amazon Translate (Montreal) Amazon Translate (N. California) Amazon Translate (N. Virginia) Amazon Translate (Ohio) Amazon Translate (Oregon) VPC (Montreal) VPC (N. California) VPC (N. Virginia) VPC (Ohio) VPC (Oregon) Amazon WorkDocs (N. Virginia) Amazon WorkDocs (Oregon) Amazon Worklink (N. Virginia) Amazon Worklink (Ohio) Amazon Worklink (Oregon) Amazon WorkMail (N. Virginia) Amazon WorkMail (Oregon) Amazon WorkSpaces (Montreal) Amazon WorkSpaces (N. Virginia) Amazon WorkSpaces (Oregon) Auto Scaling (Montreal) Auto Scaling (N. California) Auto Scaling (N. Virginia) Auto Scaling (Ohio) Auto Scaling (Oregon) AWS Activate Console (Oregon) AWS Amplify (Montreal) AWS Amplify (N. California) AWS Amplify (N. Virginia) AWS Amplify (Ohio) AWS Amplify (Oregon) AWS App Mesh (Montreal) AWS App Mesh (N. California) AWS App Mesh (N. Virginia) AWS App Mesh (Ohio) AWS App Mesh (Oregon) AWS Application Discovery Service (N. Virginia) AWS Application Discovery Service (Oregon) AWS Application Migration Service (N. Virginia) AWS Application Migration Service (Ohio) AWS Application Migration Service (Oregon) AWS AppSync (Montreal) AWS AppSync (N. California) AWS AppSync (N. Virginia) AWS AppSync (Ohio) AWS AppSync (Oregon) AWS Audit Manager (N. California) AWS Audit Manager (N. Virginia) AWS Audit Manager (Ohio) AWS Audit Manager (Oregon) AWS Backup (Montreal) AWS Backup (N. California) AWS Backup (N. Virginia) AWS Backup (Ohio) AWS Backup (Oregon) AWS Batch (Montreal) AWS Batch (N. California) AWS Batch (N. Virginia) AWS Batch (Ohio) AWS Batch (Oregon) AWS Billing Console AWS Certificate Manager (Montreal) AWS Certificate Manager (N. California) AWS Certificate Manager (N. Virginia) AWS Certificate Manager (Ohio) AWS Certificate Manager (Oregon) AWS Chatbot AWS Client VPN (Montreal) AWS Client VPN (N. California) AWS Client VPN (N. Virginia) AWS Client VPN (Ohio) AWS Client VPN (Oregon) AWS Cloud Map (Montreal) AWS Cloud Map (N. California) AWS Cloud Map (N. Virginia) AWS Cloud Map (Ohio) AWS Cloud Map (Oregon) AWS Cloud9 (Montreal) AWS Cloud9 (N. California) AWS Cloud9 (N. Virginia) AWS Cloud9 (Ohio) AWS Cloud9 (Oregon) AWS CloudFormation (Montreal) AWS CloudFormation (N. California) AWS CloudFormation (N. Virginia) AWS CloudFormation (Ohio) AWS CloudFormation (Oregon) AWS CloudHSM (Montreal) AWS CloudHSM (N. California) AWS CloudHSM (N. Virginia) AWS CloudHSM (Ohio) AWS CloudHSM (Oregon) AWS CloudShell (N. Virginia) AWS CloudShell (Ohio) AWS CloudShell (Oregon) AWS CloudTrail (Montreal) AWS CloudTrail (N. California) AWS CloudTrail (N. Virginia) AWS CloudTrail (Ohio) AWS CloudTrail (Oregon) AWS CodeArtifact (N. Virginia) AWS CodeArtifact (Ohio) AWS CodeArtifact (Oregon) AWS CodeBuild (Montreal) AWS CodeBuild (N. California) AWS CodeBuild (N. Virginia) AWS CodeBuild (Ohio) AWS CodeBuild (Oregon) AWS CodeCommit (Montreal) AWS CodeCommit (N. California) AWS CodeCommit (N. Virginia) AWS CodeCommit (Ohio) AWS CodeCommit (Oregon) AWS CodeDeploy (Montreal) AWS CodeDeploy (N. California) AWS CodeDeploy (N. Virginia) AWS CodeDeploy (Ohio) AWS CodeDeploy (Oregon) AWS CodePipeline (Montreal) AWS CodePipeline (N. California) AWS CodePipeline (N. Virginia) AWS CodePipeline (Ohio) AWS CodePipeline (Oregon) AWS CodeStar (Montreal) AWS CodeStar (N. California) AWS CodeStar (N. Virginia) AWS CodeStar (Ohio) AWS CodeStar (Oregon) AWS Config (Montreal) AWS Config (N. California) AWS Config (N. Virginia) AWS Config (Ohio) AWS Config (Oregon) AWS Control Tower (Montreal) AWS Control Tower (N. Virginia) AWS Control Tower (Ohio) AWS Control Tower (Oregon) AWS Data Exchange (N. California) AWS Data Exchange (N. Virginia) AWS Data Exchange (Ohio) AWS Data Exchange (Oregon) AWS Data Pipeline (N. Virginia) AWS Data Pipeline (Oregon) AWS DMS (Montreal) AWS DMS (N. California) AWS DMS (N. Virginia) AWS DMS (Ohio) AWS DMS (Oregon) AWS DataSync (Montreal) AWS DataSync (N. California) AWS DataSync (N. Virginia) AWS DataSync (Ohio) AWS DataSync (Oregon) AWS DeepComposer (N. Virginia) AWS DeepLens (N. Virginia) AWS DeepRacer (N. Virginia) AWS Device Farm (Oregon) AWS Direct Connect (Montreal) AWS Direct Connect (N. California) AWS Direct Connect (N. Virginia) AWS Direct Connect (Ohio) AWS Direct Connect (Oregon) AWS Directory Service (Montreal) AWS Directory Service (N. California) AWS Directory Service (N. Virginia) AWS Directory Service (Ohio) AWS Directory Service (Oregon) AWS Elastic Beanstalk (Montreal) AWS Elastic Beanstalk (N. California) AWS Elastic Beanstalk (N. Virginia) AWS Elastic Beanstalk (Ohio) AWS Elastic Beanstalk (Oregon) AWS Elemental (Montreal) AWS Elemental (N. California) AWS Elemental (N. Virginia) AWS Elemental (Ohio) AWS Elemental (Oregon) AWS Fault Injection Simulator (Montreal) AWS Fault Injection Simulator (N. California) AWS Fault Injection Simulator (N. Virginia) AWS Fault Injection Simulator (Ohio) AWS Fault Injection Simulator (Oregon) AWS Firewall Manager (Montreal) AWS Firewall Manager (N. California) AWS Firewall Manager (N. Virginia) AWS Firewall Manager (Ohio) AWS Firewall Manager (Oregon) AWS Global Accelerator AWS Glue (Montreal) AWS Glue (N. California) AWS Glue (N. Virginia) AWS Glue (Ohio) AWS Glue (Oregon) AWS Glue DataBrew (Montreal) AWS Glue DataBrew (N. California) AWS Glue DataBrew (N. Virginia) AWS Glue DataBrew (Ohio) AWS Glue DataBrew (Oregon) AWS Greengrass (N. Virginia) AWS Greengrass (Ohio) AWS Greengrass (Oregon) AWS Ground Station (N. Virginia) AWS Ground Station (Ohio) AWS Ground Station (Oregon) AWS Health AWS IAM AWS Import/Export AWS Internet Connectivity (Montreal) AWS Internet Connectivity (N. California) AWS Internet Connectivity (N. Virginia) AWS Internet Connectivity (Ohio) AWS Internet Connectivity (Oregon) AWS IoT 1-Click (N. Virginia) AWS IoT 1-Click (Ohio) AWS IoT 1-Click (Oregon) AWS IoT Analytics (N. Virginia) AWS IoT Analytics (Ohio) AWS IoT Analytics (Oregon) AWS IoT Core (Montreal) AWS IoT Core (N. California) AWS IoT Core (N. Virginia) AWS IoT Core (Ohio) AWS IoT Core (Oregon) AWS IoT Device Defender (Montreal) AWS IoT Device Defender (N. California) AWS IoT Device Defender (N. Virginia) AWS IoT Device Defender (Ohio) AWS IoT Device Defender (Oregon) AWS IoT Device Management AWS IoT Events (N. Virginia) AWS IoT Events (Ohio) AWS IoT Events (Oregon) AWS IoT SiteWise (N. Virginia) AWS IoT SiteWise (Oregon) AWS IoT Things Graph (N. California) AWS IoT Things Graph (N. Virginia) AWS IoT Things Graph (Oregon) AWS Key Management Service (Montreal) AWS Key Management Service (N. California) AWS Key Management Service (N. Virginia) AWS Key Management Service (Ohio) AWS Key Management Service (Oregon) AWS Lake Formation (Montreal) AWS Lake Formation (N. California) AWS Lake Formation (N. Virginia) AWS Lake Formation (Ohio) AWS Lake Formation (Oregon) AWS Lambda (Montreal) AWS Lambda (N. California) AWS Lambda (N. Virginia) AWS Lambda (Ohio) AWS Lambda (Oregon) AWS License Manager (Montreal) AWS License Manager (N. California) AWS License Manager (N. Virginia) AWS License Manager (Ohio) AWS License Manager (Oregon) AWS Management Console AWS Marketplace AWS Migration Hub (N. Virginia) AWS Migration Hub (Oregon) AWS Mobile Hub (N. Virginia) AWS NAT Gateway (Montreal) AWS NAT Gateway (N. California) AWS NAT Gateway (N. Virginia) AWS NAT Gateway (Ohio) AWS NAT Gateway (Oregon) AWS Network Firewall (N. Virginia) AWS Network Firewall (Ohio) AWS Network Firewall (Oregon) OpsWorks CM (N. California) OpsWorks CM (N. Virginia) OpsWorks CM (Ohio) OpsWorks CM (Oregon) AWS OpsWorks for Puppet Enterprise (N. California) AWS OpsWorks for Puppet Enterprise (N. Virginia) AWS OpsWorks for Puppet Enterprise (Ohio) AWS OpsWorks for Puppet Enterprise (Oregon) AWS OpsWorks Stacks (Montreal) AWS OpsWorks Stacks (N. California) AWS OpsWorks Stacks (N. Virginia) AWS OpsWorks Stacks (Ohio) AWS OpsWorks Stacks (Oregon) AWS Organizations AWS Outposts (Montreal) AWS Outposts (N. California) AWS Outposts (N. Virginia) AWS Outposts (Ohio) AWS Outposts (Oregon) AWS QuickSight (Montreal) AWS QuickSight (N. Virginia) AWS QuickSight (Ohio) AWS QuickSight (Oregon) AWS Resource Access Manager (Montreal) AWS Resource Access Manager (N. California) AWS Resource Access Manager (N. Virginia) AWS Resource Access Manager (Ohio) AWS Resource Access Manager (Oregon) AWS Resource Groups Resource Tagging (Montreal) Resource Tagging (N. California) Resource Tagging (N. Virginia) Resource Tagging (Ohio) Resource Tagging (Oregon) AWS RoboMaker (N. Virginia) AWS RoboMaker (Ohio) AWS RoboMaker (Oregon) AWS Secrets Manager (Montreal) AWS Secrets Manager (N. California) AWS Secrets Manager (N. Virginia) AWS Secrets Manager (Ohio) AWS Secrets Manager (Oregon) AWS Security Hub (Montreal) AWS Security Hub (N. California) AWS Security Hub (N. Virginia) AWS Security Hub (Ohio) AWS Security Hub (Oregon) AWS Serverless Application Repository (Montreal) AWS Serverless Application Repository (N. California) AWS Serverless Application Repository (N. Virginia) AWS Serverless Application Repository (Ohio) AWS Serverless Application Repository (Oregon) AWS Service Catalog (Montreal) AWS Service Catalog (N. California) AWS Service Catalog (N. Virginia) AWS Service Catalog (Ohio) AWS Service Catalog (Oregon) AWS Sign-In (Montreal) AWS Sign-In (N. California) AWS Sign-In (N. Virginia) AWS Sign-In (Ohio) AWS Sign-In (Oregon) AWS Single Sign-On (Montreal) AWS Single Sign-On (N. Virginia) AWS Single Sign-On (Ohio) AWS Single Sign-On (Oregon) AWS Site-to-Site VPN (Montreal) AWS Site-to-Site VPN (N. California) AWS Site-to-Site VPN (N. Virginia) AWS Site-to-Site VPN (Ohio) AWS Site-to-Site VPN (Oregon) AWS Step Functions (Montreal) AWS Step Functions (N. California) AWS Step Functions (N. Virginia) AWS Step Functions (Ohio) AWS Step Functions (Oregon) AWS Storage Gateway (Montreal) AWS Storage Gateway (N. California) AWS Storage Gateway (N. Virginia) AWS Storage Gateway (Ohio) AWS Storage Gateway (Oregon) AWS Support Center AWS Systems Manager (Montreal) AWS Systems Manager (N. California) AWS Systems Manager (N. Virginia) AWS Systems Manager (Ohio) AWS Systems Manager (Oregon) AWS Transfer (Montreal) AWS Transfer (N. California) AWS Transfer (N. Virginia) AWS Transfer (Ohio) AWS Transfer (Oregon) AWS Transit Gateway (Montreal) AWS Transit Gateway (N. California) AWS Transit Gateway (N. Virginia) AWS Transit Gateway (Ohio) AWS Transit Gateway (Oregon) AWS Trusted Advisor AWS VPCE PrivateLink (Montreal) AWS VPCE PrivateLink (N. California) AWS VPCE PrivateLink (N. Virginia) AWS VPCE PrivateLink (Ohio) AWS VPCE PrivateLink (Oregon) AWS WAF AWS X-Ray (Montreal) AWS X-Ray (N. California) AWS X-Ray (N. Virginia) AWS X-Ray (Ohio) AWS X-Ray (Oregon) EC2 Image Builder (Montreal) EC2 Image Builder (N. California) EC2 Image Builder (N. Virginia) EC2 Image Builder (Ohio) EC2 Image Builder (Oregon) Server Migration Service (Montreal) Server Migration Service (N. California) Server Migration Service (N. Virginia) Server Migration Service (Ohio) Server Migration Service (Oregon)

Apr 19 Apr 18 Apr 17 Apr 16 Apr 15 Apr 14 Apr 13 [RESOLVED] Increased API Errors 11:44 AM PDT We are investigating increased API error rates in the US-EAST-1 Region. 12:17 PM PDT We are working to resolve the issue resulting in increased error rates for the following EC2 APIs in the US-EAST-1 Region: RunInstances, *SecurityGroups, *NetworkInterfaces, *RouteTables, *AccountAttributes, and *NetworkAcls. These APIs will affect the ability to launch new EC2 instances and make mutating changes to Virtual Private Cloud (VPC) network configuration(s). Existing instances and networks continue to work normally. We have identified the root cause and are working towards resolution. 12:56 PM PDT We continue to work toward recovery for the issue resulting in increased API error rates for the EC2 APIs in the US-EAST-1 Region. We have identified the root cause and applied mitigations to reduce the impact, while we continue to work towards full mitigation. Some APIs may experience errors or “request limit exceeded” when calling an affected API or using the EC2 Management Console. 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. 1:22 PM PDT We continue to work towards full resolution for the issue resulting in increased error rates for the EC2 APIs in the US-EAST-1 Region. We have applied some request throttling for the affected APIs, which has reduced error rates, allowing several APIs to see early recovery. We are adjusting these throttling for some of the affected APIs, which are causing some additional API errors and elevated errors in the EC2 Management Console. We would expect API error rates to continue to recover with the mitigation steps we have taken as we work towards full recovery. 2:13 PM PDT We continue to work towards full recovery for the issue resulting in increased error rates for the EC2 APIs in the US-EAST-1 Region. We have adjusted request throttles to reduce error rates for the affected APIs. While this has worked for some of the affected APIs, such as RunInstances, some of the affected APIs are now returning “request limit exceeded”. If this does occur, attempt to reduce your request rate for the affected API and retry. With the request throttling, some of the affected services are also beginning to see recovery. We continue to work on resolving the underlying root cause and expect to be fully recovered within the next hour. 3:01 PM PDT We have further adjusted request throttles to reduce error rates for the affected APIs, so “request limit exceeded” errors should now be significantly reduced. We are now in the final stages of resolving the issue with the underlying data store. Once resolved, we will remove all API throttles and expect all API operations to return to normal levels. 3:55 PM PDT We have resolved the issue resulting in the increased error rates for the EC2 APIs, and removed all API request throttling, in the US-EAST-1 Region. Beginning at 11:11 AM PDT, we experienced an increase in API error rates for RunInstances and networking related EC2 APIs. At 12:57 PM PDT, request throttling was applied to several of the affected APIs, which helped to improve error rates for the RunInstances API. We continued to work towards full resolution, while removing request throttles, until 3:30 PM PDT, at which time all affected APIs returned to normal levels of operation. The issue has been resolved and the service is operating normally. [RESOLVED] Increased Provisioning and Scaling Latencies 12:50 PM PDT We can confirm increased provisioning and scaling latencies for Elastic Load Balancers in the US-EAST-1 Region. 1:38 PM PDT We have determined the root cause of increased scaling latencies for Elastic Load Balancers in the US-EAST-1 Region and are working towards mitigation. 2:39 PM PDT The team is closely monitoring the issue with EC2 APIs, and continues to see reductions in scaling and provisioning latencies. Other load balancing operations, including target registrations and traffic processing are unaffected. Once the issue with the EC2 APIs is resolved, we will process the backlog of any pending operations before we observe full resolution. 3:44 PM PDT Beginning at 11:13 AM PDT we experienced increased provisioning and scaling latencies for Elastic Load Balancers in the US-EAST-1 Region. Recovery for scaling latency occurred at 1:15 PM PDT, and recovery for provisioning latency occurred at 3:35 PM PDT. The issue has been resolved and the service is operating normally.