A hardware malfunction at an unnamed cloud provider is disrupting access to Ethereum, according to a report on X. Ethereum's consensus layer kept working normally, and the full reach of the problem has not been established.
A hardware malfunction at a cloud provider is disrupting Ethereum, according to a report posted on X. The provider has not been named.
The blockchain itself appears to be fine. Research into the incident found that Ethereum's consensus layer kept working normally on November 14, 2026. The trouble sits in the access layer, which users go through to reach the network.
Cloud-hosted nodes put user access at risk
Ethereum runs on two layers. The consensus layer is where validators agree on the order and validity of blocks, while the execution layer processes transactions and smart contracts. Most apps query execution-layer nodes to read and write data.
Many of those nodes run in commercial data centers. As of November 2026, between 35% and 60% of execution-layer nodes are hosted on cloud providers, and AWS alone accounts for approximately 35%.
When a cloud provider fails, the effects tend to show up in user-facing products. Wallets and exchanges that depend on cloud-hosted nodes have historically seen outages during cloud failures, so blocks keep getting produced while users checking balances or submitting transactions may lose access.
The scope of the outage remains unclear
The scale of this event is uncertain. RPC providers, which let apps send requests to the blockchain, reported minor performance issues around mid-November 2026, but those issues have not been tied to widespread Ethereum disruptions. Research covering late October through mid-November 2026 also found no verified report of a cloud hardware malfunction affecting Ethereum in that window.
Ethereum has faced something similar before. In October 2025, failures in AWS's DynamoDB service disrupted key Ethereum services for hours, while consensus operations stayed functional. Each incident has fed a debate in the Ethereum community about infrastructure diversification.
Users can reduce their dependence on a single provider. Running a self-hosted node, or keeping access to more than one RPC endpoint, is one option the source describes.
Next, the points to watch are whether the affected provider is identified and how long the access problems last.
Source: Crypto Briefing
Trading involves risk.
Risk Disclaimer
