Is AWS IoT Core down?
Current AWS IoT Core status is UP

We continue to see recovery of the error rates and latencies for the DynamoDB APIs in the US-WEST-2 Region. Error rates and latencies are close to normal levels but we continue to work towards full resolution. Other AWS services are also seeing recovery. We will continue to keep you updated on our progress.

We continue to investigate increased networking latencies and errors affecting Availability Zones (usw2-az1 and usw2-az2) in the US-WEST-2 Region. The issue affects some instances in each of these Availability Zones, where network mappings are not being propagated to the underlying hardware. Any mutations to network configurations would see delayed mappings, which will affect network connectivity. Other networking services like PrivateLink and API Gateway, are also seeing network connectivity issues where network mappings have been mutated. For other AWS services, such as Lambda and Container Services (ECS/EKS), delays in function and container creation, as well as increased error rates, may occur due to this issue.

We have been working to resolve the issue and are seeing improvements in the usw2-az1 Availability Zone as a result of these efforts. We will continue to keep you updated as we make progress towards full recovery.

We are investigating increased error rates and latencies for Connect, Subscribe & Publish operations in the US-WEST-2 Region.

11:43 AM PST We are investigating increased error rates and latency for the Identity, Registry, and Rules Engine APIs in the US-EAST-1 Region. Device connectivity, messaging and rules evaluations are unaffected.

Increased Error Rates
4:42 PM PST: We continue to work towards full recovery of the issue affecting the Kinesis Data Streams API in the US-EAST-1 Region, and are observing steady signs of recovery. We will be throttling APIs as we work on recovery. Impact to Cognito User & Identity Pools was resolved at 2:28 PM PST. Other AWS Services that rely on Kinesis Data Stream APIs have begun observing recovery, and will continue to as we work toward full resolution. We are actively working toward full recovery for all affected services, and will provide updates as we have new information to share. A comprehensive list of Impacted Services can be found below.

2:25 PM PST: We continue to work towards recovery of the issue affecting the Kinesis Data Streams API in the US-EAST-1 Region. We also continue to see an improvement in error rates for Kinesis and several affected services, but expect full recovery to still take up to a few hours. For Amazon Cognito, the issues affecting APIs and authentication for user and identity pools has now recovered. For AutoScaling, delays in launching new instances has now recovered, however some scaling operations are still delayed due to delayed CloudWatch metrics. For EventBridge, we have seen partial recovery for the issue affecting delivery of Events.

We are actively working toward full recovery for all affected services, and will continue to provide updates regularly as we have new information to share.
12:15 PM PST: We continue to work towards recovery of the issue affecting the Kinesis Data Streams API in the US-EAST-1 Region. We also continue to see an improvement in error rates for Kinesis and several affected services, but expect full recovery to still take up to a few hours.

The issue continues to also affect other services, or parts of these services, that utilize Kinesis Data Streams within their workflows. While features of multiple services are impacted, some services have seen broader impact and service-specific impact details are below. We continue to work towards full recovery.
10:47 AM PST:
We continue to work towards recovery of the issue affecting the Kinesis Data Streams API in the US-EAST-1 Region. For Kinesis Data Streams, the issue is affecting the subsystem that is responsible for handling incoming requests. The team has identified the root cause and is working on resolving the issue affecting this subsystem.

The issue also affects other services, or parts of these services, that utilize Kinesis Data Streams within their workflows. While features of multiple services are impacted, some services have seen broader impact and service-specific impact details are below.
9:52 AM PST: The Kinesis Data Streams API is currently impaired in the US-EAST-1 Region. As a result customers are not able to write or read data published to Kinesis streams.
CloudWatch metrics and events are also affected, with elevated PutMetricData API error rates and some delayed metrics.
While EC2 instances and connectivity remain healthy, some instances are experiencing delayed instance health metrics, but remain in a healthy state.
AutoScaling is also experiencing delays in scaling time due to CloudWatch metric delays. For customers affected by this, we recommend manual scaling adjustments to AutoScaling groups.
Currently Impacted Services: ACM, Amplify Console, AppStream2, AppSync, Athena, Batch, CodeArtifact, CodeGuru Profiler, CodeGuru Reviewer, CloudFormation, CloudMap, CloudTrail, Connect, Comprehend, DynamoDB, Elastic Beanstalk, EventBridge, IoT Services, Lambda, LEX, Macie, Managed Blockchain, Marketplace, MediaLive, MediaConvert, Personalize, RDS Performance Insights, Rekognition, SageMaker, Support Console, and Workspaces. For further details on each of these services, please see your Personal Health Dashboard. Other services, like S3, remain unaffected by this event. This issue has also affected our ability to post updates to the Service Health Dashboard. We are continuing to work towards resolution.