1/8/2023 0 Comments Awa outage![]() We can see that for the Columbus, OH, location the test result was presenting 100% packet loss.įigure 6. In Figure 6, we can see how Webex (AS 13445) was unable to communicate with the server hosted on AWS (AS 16509). Internet Insights reporting Network Outage for, Inc. failure during the power outage of Amazon US-EAST-2 Regionįigure 5. ThousandEyes also captured the problem as a network outage for this target and is seen within Internet Insights™ (as seen in Figure 5).įigure 4. One of the impacted Webex services was .įrom different tests targeting, we can see how they failed during the power outage for US-EAST-2 AZ1 (as seen in Figure 4). ![]() Columbus, OH, US) and within the affected US-EAST-2 AZ1. Some of these Webex services use the prefix 170.72.231.0/24, and this prefix is inside the AS 16509 (Amazon, Inc. The reason is that while many Webex service components are located in Cisco’s Webex data centers, some others are built on top of AWS. Many users experienced issues with the Webex app, preventing them from creating rooms, sending or reading messages, signing in, or sharing files, and even some users reported the Webex status page was presenting an issue. Here are some examples of the apps and services that were affected. ThousandEyes captured the impact that this power loss event had on numerous services and their global users. Incidents impacting EC2 can affect the reachability of multiple customer and business applications. The most significant impact was to Amazon’s EC2 service, which powers a wide range of hosted customer applications and which went down in US-EAST-2 AZ1 during the event. Traffic between several AWS regions and US-EAST-2 located in Columbus, OH, is dropped during the power outage Affected interfaces in the AWS network (AS 16509)Ī good look at the impact can be seen at around 17:10 UTC, with several ThousandEyes vantage points located in various AWS regions around the world showing failures connecting to a ThousandEyes vantage point in Columbus, OH, located in the AWS US-EAST-2 AZ1 data center.įigure 3. ![]() Application outages increased during the incidentįigure 2. Applications hosted on AWS started to see an increase in application errors and, simultaneously, traffic loss was observed on routers in the AWS network (AS 16509 and AS 14618) located in Columbus, OH (see Figure 1 and Figure 2 below). Shortly after the start of the incident, ThousandEyes observed a spike in both application and network outages corresponding with the AWS power outage. ![]() While AWS reported the power outage lasted only approximately 20 minutes, some of its customers’ services and applications took far longer to recover-in some cases, up to three hours. The outage affected connectivity to and from the region and brought down Amazon’s EC2 instances, which impacted applications such as Webex, Okta, Splunk, BambooHR, and others. On July 28, 2022, just before 17:00 UTC, Amazon Web Services (AWS) experienced a power failure that disrupted services located within Availability Zone 1 (AZ1) in the US-EAST-2 Region. The following is an analysis of the outage. On July 28, 2022, Amazon Web Services (AWS) experienced a power failure that disrupted services located within Availability Zone 1 (AZ1) in the US-EAST-2 Region.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |