AWS Experiences Disruption, Ethereum Unaffected

Amazon Web Services (AWS) experienced a minor disruption, but Ethereum network nodes were unaffected despite their reliance on Amazon’s hosting.

On June 13, the cloud service provider was temporarily unavailable for approximately three hours.

At 12:08 p.m. PDT, the company reported for the first time that it was “investigating increased error rates and latencies” in certain U.S. regions.

Numerous major news outlets, such as the Associated Press, were impacted and unable to publish articles.

Evan Van Ness, an advocate for Ethereum, observed the outage and noted that the Ethereum network was unaffected.

Ethernodes reports that 64.5% of the Ethereum network depends on Amazon hosting providers.

Van Ness added that the impact could have been more significant if the outage had occurred in Europe due to the current quantity of Ether staked on Lido, which is approximately 7.1 million, or 35 percent of the total:

“I imagine there would be some effect if AWS went down in Europe given how much of Lido is in the cloud.”

Ethereum has been criticized for centralization due to its dependence on infrastructure provider Infura, which provides network nodes to businesses and organizations.

Many of these businesses, including the Lido platform for liquid staking, rely significantly on AWS for cloud hosting services.

Twenty minutes after discovering the issue, AWS reported that it was related to a service called AWS Lambda, which allows customers to execute code for various types of applications.

At 3.37 PM PDT, more than three hours after AWS fell offline, the company announced that “the issue has been resolved and all AWS services are operating normally.”

AWS holds a 34% market share, according to the hosting platform Kinsta, as the leading cloud hosting provider.