Косяками пошло(

Service: AWS VPCE PrivateLink
Region: 🇺🇸US East (N. Virginia)
URL: http://status.aws.amazon.com/#privatelink-us-east-1_1608333449

We wanted to provide you with some more details on the periods of network connectivity issues for VPCE Private Link within a single Availability Zone (use1-az1) within the US-EAST-1 Region. While we are currently not observing any network connectivity issues at this moment, we did observe two periods of impact, the first between 11:30 AM and 12:00 PM PST and the second between 1:00 PM and 1:45 PM PST. We have identified the subsystem that was responsible for this issue but continue to work towards identifying root cause and mitigating any further impact. We will continue to provide updates on our progress towards full recovery, and immediately should the network connectivity issues return.

#privatelink #useast1

Service: Amazon Elastic Compute Cloud
Region: 🇺🇸US East (N. Virginia)
URL: http://status.aws.amazon.com/#ec2-us-east-1_1608333369

We wanted to provide you with some more details on the periods of network connectivity issues for NAT Gateway within a single Availability Zone (use1-az1) within the US-EAST-1 Region. While we are currently not observing any network connectivity issues at this moment, we did observe two periods of impact, the first between 11:30 AM and 12:00 PM PST and the second between 1:00 PM and 1:45 PM PST. We have identified the subsystem that was responsible for this issue but continue to work towards identifying root cause and mitigating any further impact. We will continue to provide updates on our progress towards full recovery, and immediately should the network connectivity issues return.

#ec2 #useast1

Service: Amazon Elastic Load Balancing
Region: 🇺🇸US East (N. Virginia)
URL: http://status.aws.amazon.com/#elb-us-east-1_1608334030

We wanted to provide you with some more details on the periods of network connectivity issues for Network Load Balancer within a single Availability Zone(use1-az1) within the US-EAST-1 Region. While we are currently not observing any network connectivity issues at this moment, we did observe two periods of impact, the first between 11:30 AM and 12:00 PM PST and the second between 1:00 PM and 1:45 PM PST. We have identified the subsystem that was responsible for this issue but continue to work towards identifying root cause and mitigating any further impact. We will continue to provide updates on our progress towards full recovery, and immediately should the network connectivity issues return.

#elb #useast1

Service: Amazon Elastic Compute Cloud
Region: 🇺🇸US East (N. Virginia)
URL: http://status.aws.amazon.com/#ec2-us-east-1_1608335967

We continue to investigate root cause of the issue affecting network connectivity for NAT Gateway within a single Availability Zone (use1-az1) in the US-EAST-1 Region. We have not seen impact since 1:45 PM PST and our engineering teams remain engaged as we work to determine root cause, and apply mitigations before resolving this event. Since this issue only affected a single Availability Zone, customers who are able to route network traffic through alternative Availability Zones for the affected services, should consider doing so.

#ec2 #useast1

Service: AWS VPCE PrivateLink
Region: 🇺🇸US East (N. Virginia)
URL: http://status.aws.amazon.com/#privatelink-us-east-1_1608335962

We continue to investigate root cause of the issue affecting network connectivity for PrivateLink within a single Availability Zone (use1-az1) in the US-EAST-1 Region. We have not seen impact since 1:45 PM PST and our engineering teams remain engaged as we work to determine root cause, and apply mitigations before resolving this event. Since this issue only affected a single Availability Zone, customers who are able to route network traffic through alternative Availability Zones for the affected services, should consider doing so.

#privatelink #useast1

Service: Amazon Elastic Load Balancing
Region: 🇺🇸US East (N. Virginia)
URL: http://status.aws.amazon.com/#elb-us-east-1_1608336163

We continue to investigate root cause of the issue affecting network connectivity for Network Load Balancer within a single Availability Zone (use1-az1) in the US-EAST-1 Region. We have not seen impact since 1:45 PM PST and our engineering teams remain engaged as we work to determine root cause, and apply mitigations before resolving this event. Since this issue only affected a single Availability Zone, customers who are able to route network traffic through alternative Availability Zones for the affected services, should consider doing so.

#elb #useast1

Service: AWS VPCE PrivateLink
Region: 🇺🇸US East (N. Virginia)
URL: http://status.aws.amazon.com/#privatelink-us-east-1_1608337987

We have not seen any further network connectivity issues for PrivateLink since 1:45 PM PST. We have also identified the root cause and prepared a fix to address the issue. The engineering team is currently working on testing this fix and preparing for deployment to the affected subset of hosts that were affected by this issue. We will continue to provide updates as we work through that deployment.

#privatelink #useast1

Service: Amazon Elastic Load Balancing
Region: 🇺🇸US East (N. Virginia)
URL: http://status.aws.amazon.com/#elb-us-east-1_1608338126

We have not seen any further network connectivity issues for Network Load Balancer since 1:45 PM PST. We have also identified the root cause and prepared a fix to address the issue. The engineering team is currently working on testing this fix and preparing for deployment to the affected subset of hosts that were affected by this issue. We will continue to provide updates as we work through that deployment.

#elb #useast1

Service: Amazon Elastic Compute Cloud
Region: 🇺🇸US East (N. Virginia)
URL: http://status.aws.amazon.com/#ec2-us-east-1_1608338005

We have not seen any further network connectivity issues for NAT Gateway since 1:45 PM PST. We have also identified the root cause and prepared a fix to address the issue. The engineering team is currently working on testing this fix and preparing for deployment to the affected subset of hosts that were affected by this issue. We will continue to provide updates as we work through that deployment.

#ec2 #useast1

Service: Amazon Elastic Load Balancing
Region: 🇺🇸US East (N. Virginia)
URL: http://status.aws.amazon.com/#elb-us-east-1_1608341674

We have seen no further network connectivity issues for Network Load Balancer since 1:45 PM PST (5 hours ago). We have identified the root cause and prepared a fix to resolve the issue, which is now being deployed. We have also taken steps to mitigate any impact should the issue reoccur before the deployment is fully completed. This issue resulted in two periods of network connectivity issues between 11:30 AM and 12:00 PM PST, and between 1:00 PM and 1:45 PM PST. The issue has been resolved and the service is operating normally.

#elb #useast1

Service: AWS VPCE PrivateLink
Region: 🇺🇸US East (N. Virginia)
URL: http://status.aws.amazon.com/#privatelink-us-east-1_1608341846

We have seen no further network connectivity issues for PrivateLink since 1:45 PM PST (5 hours ago). We have identified the root cause and prepared a fix to resolve the issue, which is now being deployed. We have also taken steps to mitigate any impact should the issue reoccur before the deployment is fully completed. This issue resulted in two periods of network connectivity issues between 11:30 AM and 12:00 PM PST, and between 1:00 PM and 1:45 PM PST. The issue has been resolved and the service is operating normally.

#privatelink #useast1

Service: Amazon Elastic Compute Cloud
Region: 🇺🇸US East (N. Virginia)
URL: http://status.aws.amazon.com/#ec2-us-east-1_1608342941

We have seen no further network connectivity issues for NAT Gateway since 1:45 PM PST (5 hours ago). We have identified the root cause and prepared a fix to resolve the issue, which is now being deployed. We have also taken steps to mitigate any impact should the issue reoccur before the deployment is fully completed. This issue resulted in two periods of network connectivity issues between 11:30 AM and 12:00 PM PST, and between 1:00 PM and 1:45 PM PST. The issue has been resolved and the service is operating normally.

#ec2 #useast1

Че AWS разваливается шоли?

Ну уже вроде как раз ожило

почему? сначала были сообщения что упало, потом что починили

в итоге сообщений много но аварий не так уж много

Там просто по каждому сервису отдельно писали

И все в одной зоне

Тьфу это вчерашние сообщения