Google Cloud sets a shutdown date for Blockchain Node Engine

Google Cloud says in its release notes that Blockchain Node Engine entered limited support on June 15, 2026. The operational fact is clear: creating new Blockchain Node Engine nodes and provisioning new Blockchain RPC endpoints is now disabled. Existing nodes and endpoints will continue to run, but Google says they will only receive critical updates until the service’s final shutdown date, set for December 15, 2026.

Blockchain Node Engine was Google Cloud’s managed service for deploying dedicated blockchain nodes, including Ethereum nodes, without operating the full infrastructure stack in-house. A blockchain node stores and verifies the network state. It also acts as an access point for applications, indexers, wallets, and analytics tools that query the chain through RPC, meaning programmatic calls to a node. When this kind of service is retired, the risk is not merely administrative. A team can lose its primary path to chain data if it waits until the deadline is close.

The official note recommends migrating workloads to Quicknode, named as Google’s partner, to avoid disruption. That detail says something useful about the blockchain infrastructure market. Large cloud providers have offered a familiar entry point for teams that wanted to consume nodes like any other cloud service. In this case, Google is not silently retiring a side experiment. It gives a schedule, keeps existing resources alive for several months, and points customers toward a specialist provider. The implied message is that running node infrastructure remains important, but it is not necessarily a product every hyperscaler wants to operate directly.

For developers, the practical consequence is an architecture review. Teams need to inventory production endpoints, credentials, quotas, WebSocket use, specific RPC methods, archive-data requirements, and failover policies. Migrating node access is not always just changing a URL. Rate limits, latency, available historical data, and monitoring behavior can differ between providers. The announcement is therefore a sober reminder about blockchain infrastructure: even when the application layer is decentralized, access paths are often concentrated in a small number of vendors. Google’s timeline turns that dependency into work that should be completed before December.