Making sense of crypto.
NBTCNEWS

Cloud provider malfunction causes temporary Ethereum access issues

An X report alleges that a hardware fault at an unidentified cloud provider is affecting Ethereum access, but the disruption’s reach and cause remain unverified. Researchers found the consensus layer continued operating, while reliance on a small number of commercial data centers could leave wallets and exchanges unable to serve users even when the blockchain itself remains functional.

By NBTC3 min read

A report posted on X says a hardware malfunction at an unnamed cloud provider is disrupting Ethereum.

The blockchain itself appears to be functioning normally. Research into the incident on November 14, 2026 found that Ethereum’s consensus layer continued operating as usual. The problem is in the access layer, the entry points users rely on to reach the network.

What is actually breaking

Ethereum has two layers. The consensus layer is where validators agree on the order and validity of blocks. The execution layer handles transactions and smart contracts. Most apps query execution-layer nodes to read and write data.

Many of these nodes are not run on hobbyists’ home machines. Instead, they operate in commercial data centers.

As of November 2026, cloud providers hosted between 35% and 60% of Ethereum execution-layer nodes. AWS alone hosted approximately 35%.

Cloud provider problems tend to affect products users interact with directly. Wallets and exchanges that rely on cloud-hosted nodes have historically experienced outages during cloud failures. Blocks continue to be produced, but users trying to check balances or submit transactions may find those services unavailable.

The scope of this event is also unclear. Remote procedure call (RPC) providers, which let apps send requests to the blockchain, reported minor performance issues around mid-November 2026. Those issues have not been linked to widespread Ethereum disruptions. Research covering late October through mid-November 2026 also found no verified reports of a cloud hardware malfunction affecting Ethereum during that period.

The reported disruption should therefore be considered a developing situation. Its full extent has not been established.

The network has been here before

In October 2025, failures in AWS’s DynamoDB service disrupted key Ethereum services for hours. Consensus operations remained functional throughout.

Each incident has added to a long-running debate in the Ethereum community about infrastructure diversification. A network that promotes its resilience should not have a large share of its access points concentrated in a few corporate data centers.

What the disruption means for Ethereum users and investors

For traders, the key distinction is between the health of the protocol and practical access to it. Ethereum’s core consensus has continued through past cloud outages. However, during those outages, users may lose the ability to interact with their assets through popular apps.

Users can take practical steps to reduce this risk. Running a self-hosted node or maintaining access to more than one RPC endpoint reduces reliance on any single provider.

Three developments are worth watching in the days ahead: whether the affected cloud provider is identified; how long access problems last and which services were affected; and whether this episode, like the one in October 2025, prompts node operators to distribute their infrastructure across more providers, or whether the industry returns to business as usual once services resume.

share preview

Sharing is disabled in this private preview. Nothing has been sent.