Google Cloud to shut down Blockchain Node Engine and hand customers to Quicknode

Google Cloud is getting out of the blockchain node business. The company will fully shut down its Blockchain Node Engine and Blockchain RPC services on December 15, 2026.

Customers are being pointed to Quicknode, which Google has named its officially recommended RPC infrastructure provider. Teams that miss the date will find their infrastructure deleted.

What’s changing and when

The wind-down is happening in two stages. The first is already in effect: since June 15, 2026, Google Cloud has disabled new node creation and stopped provisioning new Blockchain RPC endpoints.

Between that date and the final cutoff, current nodes and endpoints stay online with limited support. Google says it will keep shipping critical updates, but customers should expect the product to stay where it is rather than gain new features.

The second stage is the shutdown itself. On December 15, 2026, every remaining node and endpoint will be deleted.

Google’s migration documentation lays out a fairly standard checklist:

• Provision replacement infrastructure
• Update RPC URLs and application configurations
• Validate workloads on the new setup
• Delete legacy Blockchain Node Engine nodes

There is one asymmetry worth noting. Google will automatically delete any remaining RPC endpoints at shutdown. Dedicated nodes, however, are on the customer’s list to clean up.

Where Quicknode fits in

Google is not leaving customers to find a replacement on their own. It has partnered with Quicknode as the recommended destination for teams that need to migrate and provision nodes.

There are two ways to make the switch. Customers can provision through the Quicknode listing on Google Cloud Marketplace, which comes with Google Cloud incentives. Or they can sign up directly on Quicknode’s own platform.

What Blockchain Node Engine actually did

Every blockchain app has to talk to a blockchain. It does that through a node, a computer that keeps a copy of the chain and answers questions about it.

Running your own node is tedious. You have to sync the chain, keep up with client upgrades, monitor uptime and pay for storage. Blockchain Node Engine was Google’s managed answer to that headache.

The service offered dedicated full nodes and archive nodes. A full node tracks the current state of the chain. An archive node keeps the complete history of past states, which matters for analytics, indexing and some auditing tasks.

Support focused mainly on Ethereum Mainnet and its testnets, along with Polygon and Solana. Alongside the dedicated nodes, Google ran a shared Blockchain RPC service, limited to Ethereum Mainnet and the Holesky testnet.

What this means for builders and the infrastructure market

The immediate impact lands on engineering teams. Anyone running production workloads on Blockchain Node Engine now has a project on the roadmap whether they wanted one or not.

Archive node users should pay particular attention. Historical data queries are often the hardest to replicate cleanly, so teams relying on them have extra reason to test early rather than in December.

On the competitive side, the arrangement is a clear win for Quicknode. Being named the official recommended provider by a hyperscaler, with a migration path built into Google’s own documentation, is the sort of distribution infrastructure companies usually have to fight for.

The date to watch is December 15, 2026. Teams that treat it like a real deadline will be fine. Teams that treat it like a suggestion will learn what deletion means.