AWS Failure in U.S Leads Trouble but Ethereum Remain Unaffected

Although the cloud service provider AWS went down for some time, there was no effect on Ethereum network nodes. On June 13th, many errors were noted between 11.49 AM PDT and 3.37 PM PDT. The services are inactive in the US-EAST-1 Region.

The root cause for this dormancy and errors were quickly managed. The issue was with the subsystem responsible for capacity management for AWS Lambda, thereby causing errors in API gateways, and also indirectly in AWS services.

Many mainstream new organizations got affected like Associated Press who was unable to publish its articles. Fortunately, the problems were resolved quickly within a shorter time frame hence, no big issues were created.

AWS Failure Ushers Hampered Chats and Calls

During the failed session, some customers may have faced the problem with the messaging and call services. But by 3.37 PM, the problem had been resolved and the services started operating normally.

In general, the outage of cloud service leads to access to apps and data, slow response time, or connectivity issues which could lead to significant impact on the online business. But, no such horrendous impact was judged. This was due to the main cause of the failure being resolved timely.

Evan Van Ness, Ethereum advocate, observed the failure stating the ETH network was not hampered. As per Ethernodes, 64.5% of Ethereum’s network is dependent on AWS, while others accounting for less networks include Hetzner online, Google Cloud, OVH SAS, Hetzner Online GmbH, Amazon, Oracle Cloud, eraSwitch Networks, netcup GmbH, Contabo GmbH.

Ethereum Network Not Affected

Ness also stated the impact could have been more intense if the failure happened in Europe. The reason for its severity arises due to the amount of Ether staked on Lido, nearly 7.1 Million. If it would have been hampered, then managing the users’ withdrawals and deposits would have created havoc. Solutions like Lido makes staking on Ethereum more accessible to users.

Ethereum is also criticized due to its dependency on Infura, which is an infrastructure provider. It mainly provides network nodes to the companies and the organizations. Lido and Infura depend on AWS for cloud hosting.

However, AWS has highlighted the root cause of the failure, linking it to a service called AWS Lambda. This service allows the customer to run code for different types of applications.

To avoid the outages, companies utilize the monitoring tools to identify and alert any issues with the cloud infrastructure. A strong backup plan is needed to ensure the continuity during cloud outage.

Andrew is a blockchain developer who developed his interest in cryptocurrencies while his post-graduation. He is a keen observer of details and shares his passion for writing along with being a developer. His backend knowledge about blockchain helps him give a unique perspective to his writing