Performance Issue: Some AWS Customers Experiencing Increased Errors
Last Updated:
2020-11-26 13:50:09
Event:
2020-11-25 17:06:00
Status:
Closed
Brief Description:
Some Cornell AWS users may be experiencing issues with individual AWS services. This may also cause performance issues and outages for services that rely on AWS. The vendor is actively working to resolve the issue.
User Impact:
Some Cornell AWS users may be experiencing issues with individual AWS services (e.g., CloudWatch, Cognito, AppStream 2.0). This may also cause performance issues and outages for services that rely on AWS (e.g., Apps on Demand, Video on Demand human captioning).
Workaround:
There is no workaround for this issue
Current Status:
Amazon has resolved the issue. All services are now operating normally. The vendor identified the root cause of the Kinesis Data Streams event and completed immediate actions to prevent recurrence.
Services Affected:
Cloudification
Video Streaming & Hosting
Apps on Demand
Subsites Affected:
Collaboration Tools
Full Description:
Some Cornell AWS users may be experiencing issues with individual AWS services (e.g., CloudWatch, Cognito, AppStream 2.0). This may also cause performance issues and outages for services that rely on AWS (e.g., Apps on Demand, Video on Demand human captioning). The vendor is aware of the issue and is investigating the root cause, specifically increased Kinesis API errors causing issues with multiple other services. More information is available at the AWS Service Health Dashboard: https://status.aws.amazon.com.
CIT TDX ID:
Timeline of Changes
| Description | Current Status | Date | Time |
|---|---|---|---|
| Some Cornell AWS users may be experiencing issues with individual AWS services (e.g., CloudWatch, Cognito, AppStream 2.0). This may also cause performance issues and outages for services that rely on AWS (e.g., Apps on Demand, Video on Demand human captioning). The vendor is aware of the issue and is investigating the root cause, specifically increased Kinesis API errors causing issues with multiple other services. More information is available at the AWS Service Health Dashboard: https://status.aws.amazon.com. | Amazon has resolved the issue. All services are now operating normally. The vendor identified the root cause of the Kinesis Data Streams event and completed immediate actions to prevent recurrence. | 2020-11-26 | 13:50:09 |
| Some Cornell AWS users may be experiencing issues with individual AWS services (e.g., CloudWatch, Cognito, AppStream 2.0). This may also cause performance issues and outages for services that rely on AWS (e.g., Apps on Demand, Video on Demand human captioning). The vendor is aware of the issue and is investigating the root cause, specifically increased Kinesis API errors causing issues with multiple other services. More information is available at the AWS Service Health Dashboard: https://status.aws.amazon.com. | Amazon continues to work toward recovery of the issue affecting the Kinesis Data Streams API in the US-EAST-1 Region. There is an improvement in error rates for Kinesis and several affected services and full recovery may take up to a few hours. For Amazon Cognito, the issues affecting APIs and authentication for user and identity pools has now recovered. CloudWatch metrics are still delayed. The vendor is actively working toward full recovery for all affected services. | 2020-11-25 | 22:45:11 |
| Some Cornell AWS users may be experiencing issues with individual AWS services (e.g., CloudWatch, Cognito, AppStream 2.0). This may also cause performance issues and outages for services that rely on AWS (e.g., Apps on Demand, Video on Demand human captioning). The vendor is aware of the issue and is investigating the root cause, specifically increased Kinesis API errors causing issues with multiple other services. More information is available at the AWS Service Health Dashboard: https://status.aws.amazon.com. | The Amazon Kinesis Data Streams API is currently impaired in the US-EAST-1 Region. This issue is also impacting other AWS services. The vendor is actively working to resolve the issue. | 2020-11-25 | 17:52:04 |