The outage suffered by Amazon Web Services (AWS) did not affect Ethereum network nodes that are heavily dependent on Amazon’s hosting service.
Cloud service provider Amazon Web Services was temporarily down for about three hours on June 13. The company initially reported that it is investigating increased error rates and delays in parts of the United States. Ethereum network nodes, which are largely connected to Amazon’s hosting network, continued to operate without being affected by the interruption.
64.5% of Ethereum Network Depends on Amazon’s Providers
In this process, many mainstream news organizations such as the Associated Press were affected by this situation and could not publish their articles.
Ethereum advocate Evan Van Ness stated that he observed the outage and that the Ethereum network was not affected by this outage. Van Ness added that if the cut had been in Europe, the impact could have been more significant due to the amount of Ethereum invested in Lido, which is now about 7.1 million, or 35 percent of the total.
According to Ethernodes, 64.5 percent of the Ethereum network is connected to Amazon’s hosting providers.
Ethereum has previously been criticized for centralization due to its reliance on infrastructure company Infura, which provides companies and organizations with network nodes. Most of these companies and liquid staking platform Lido currently rely heavily on AWS for their cloud hosting services.
About 20 minutes after the issue was discovered, AWS said the root cause was linked to a service called AWS Lambda, which allows customers to run code for different types of applications.
Three hours after AWS crashed, the company reported that the issue was resolved and all AWS services were operating normally.
51803
