Size: a a a

2020 November 25

N

Nikolay in AWS_RU
Если накроет, то у всех такие проблемы будут :)
источник

LB

Let Eat Bee in AWS_RU
Nikolay
Основной регион у всех находится в Ashburn, North Virginia
Почему так кучкуются? ГЭС где-то рядом?
источник

A

Alex in AWS_RU
Let Eat Bee
Почему так кучкуются? ГЭС где-то рядом?
АЭС :)
источник

N

Nikolay in AWS_RU
Data center valley
источник

N

Nikolay in AWS_RU
Каналы связи
источник

☁️ AWStatus in AWS_RU
Service: Amazon WorkSpaces
Region: 🇺🇸US East (N. Virginia)
URL: http://status.aws.amazon.com/#workspaces-us-east-1_1606334944

We are experiencing increased error rates in provisioning of new Amazon WorkSpaces in the US-EAST-1 Region

#workspaces #useast1
источник

KT

Karen Tovmasyan in AWS_RU
Да, постмортем гуглится
источник

☁️ AWStatus in AWS_RU
Service: AWS IoT SiteWise
Region: 🇺🇸US East (N. Virginia)
URL: http://status.aws.amazon.com/#iotsitewise-us-east-1_1606335878

We are continuing to experience elevated error rates on data ingestion and increased computation latency for IoT SiteWise auto-computed aggregates, transforms and metrics in the US-EAST-1 Region. This is also impacting IoT Events and IoT Analytics. We continue to work towards resolution.

#iotsitewise #useast1
источник

LK

L K in AWS_RU
жестка
источник

N

Nikolay in AWS_RU
Трамп что-ли разошелся
источник

AS

Alexey Stekov in AWS_RU
Nikolay
Трамп что-ли разошелся
«Шутка не ушла»
источник

☁️ AWStatus in AWS_RU
Service: Amazon Cognito
Region: 🇺🇸US East (N. Virginia)
URL: http://status.aws.amazon.com/#cognito-us-east-1_1606337298

We continue to work towards recovery of the issue affecting the Cognito User Pools and Identity Pools operations in the US-EAST-1 Region and we see improvement in the error rates experienced by customers.

#cognito #useast1
источник
2020 November 26

☁️ AWStatus in AWS_RU
Service: AWS Batch
Region: 🇺🇸US East (N. Virginia)
URL: http://status.aws.amazon.com/#batch-us-east-1_1606337888

We have identified the root cause of increased error rates and delays for job state transitions and compute environment scaling in the US-EAST-1 Region and continue to work toward resolution.

#batch #useast1
источник

☁️ AWStatus in AWS_RU
Service: Amazon CloudFront
Region: 🌏 Global
URL: http://status.aws.amazon.com/#cloudfront_1606339522

We are working towards recovery for delays in reporting updates for change propagation of invalidations and CloudFront configurations. Customer changes are propagating fine across our edge locations but the associated reporting is not getting updated. CloudFront Access Logs, Metrics and Reporting may continue to be affected. End-user requests for content from our edge locations are not affected by this issue and are being served normally.

#cloudfront
источник

☁️ AWStatus in AWS_RU
Service: Amazon Cognito
Region: 🇺🇸US East (N. Virginia)
URL: http://status.aws.amazon.com/#cognito-us-east-1_1606339853

We continue to work towards recovery of the issue affecting the Cognito User Pools and Identity Pools operations in the US-EAST-1 Region and we see further improvement in the error rates experienced by customers.

#cognito #useast1
источник

☁️ AWStatus in AWS_RU
Service: AWS Batch
Region: 🇺🇸US East (N. Virginia)
URL: http://status.aws.amazon.com/#batch-us-east-1_1606340112

We are no longer seeing compute environment scaling delays but are still experiencing elevated job state transition times in the US-EAST-1 Region and continue to work toward resolution.

#batch #useast1
источник

☁️ AWStatus in AWS_RU
Service: Amazon EventBridge
Region: 🇺🇸US East (N. Virginia)
URL: http://status.aws.amazon.com/#events-us-east-1_1606340166

We have identified the root cause of elevated API errors and latencies in US-EAST-1. While we are seeing partial recovery, we continue to see elevated error rates and latency on API calls to PutEvents. Additionally, Rules subscribing to Events from other AWS Services continue to be delayed as we work toward full resolution.

#events #useast1
источник

☁️ AWStatus in AWS_RU
Service: Amazon CloudWatch
Region: 🇺🇸US East (N. Virginia)
URL: http://status.aws.amazon.com/#cloudwatch-us-east-1_1606340996

We are still seeing elevated PutMetricData API error rates and some delayed metrics in US-EAST-1 Region. We continue to work toward full recovery.

#cloudwatch #useast1
источник

☁️ AWStatus in AWS_RU
Service: Amazon Elastic Kubernetes Service
Region: 🇺🇸US East (N. Virginia)
URL: http://status.aws.amazon.com/#eks-us-east-1_1606341305

We continue to work towards recovery of the issue affecting Amazon EKS in the US-EAST-1 Region. Customer applications that are backed by pods already running are not impacted. Also applications and pods can be started and run on EC2 instances that are already part of the cluster. EKS customers are experiencing errors when creating, upgrading and deleting EKS clusters and managed node groups. Customers will experience errors launching new Fargate pods, running Fargate pods are not impacted.

#eks #useast1
источник

☁️ AWStatus in AWS_RU
Service: Amazon Elastic Container Service
Region: 🇺🇸US East (N. Virginia)
URL: http://status.aws.amazon.com/#ecs-us-east-1_1606341471

We continue working towards recovery for the issue impacting Amazon ECS in the US-EAST-1 region. Currently running ECS tasks are not impacted for either the EC2 or Fargate launch types. Customers are experiencing API error rates and delays delivering task events and metrics in the US-EAST-1 region. ECS clusters are also not able to scale up or down due to task launch errors. Customers are missing metrics and events from their running tasks as ECS Insights is not able to propagate information. Task Set and Capacity Providers are also impacted. Customers using ECS on Fargate are not able to launch new tasks, running Fargate tasks are not impacted.

#ecs #useast1
источник