Google Cloud is fully shutting down its Blockchain Node Engine and Blockchain RPC services on December 15, 2026. All remaining nodes and RPC endpoints will be removed. Clients are advised to transition to Quicknode, which Google has officially recommended as the RPC infrastructure provider. Those who miss the deadline will lose their infrastructure.
The shutdown is occurring in two phases. The first phase is already in effect: as of June 15, 2026, Google Cloud has disabled the creation of new nodes and stopped issuing new RPC endpoints. Until the final shutdown, current nodes and endpoints will operate with limited support. Google promises to release only critical updates, with no new features.
The second phase – the actual shutdown. On December 15, 2026, all remaining nodes and endpoints will be deleted. Google's migration documentation provides a standard checklist: deploy replacements, update RPC addresses and application configurations, verify workloads on the new infrastructure, and remove old Blockchain Node Engine nodes. There is one asymmetry: Google will delete RPC endpoints itself, but clients must clean up dedicated nodes independently.
Google is not leaving clients to find a replacement on their own. Quicknode has been chosen as the partner and recommended recipient. Transition can be done in two ways: through Quicknode's listing in the Google Cloud Marketplace, which offers Google Cloud incentives, or directly through the Quicknode platform.
Blockchain Node Engine was a managed solution for running blockchain nodes without manual synchronization, client updates, and monitoring. The service offered dedicated full nodes and archive nodes. A full node tracks the current state of the chain, while an archive node stores the entire history of past states, which is important for analytics, indexing, and auditing. Support covered Ethereum Mainnet and its testnets, Polygon, and Solana. A separate general Blockchain RPC was limited to Ethereum Mainnet and the Holesky testnet.
The main impact will be on engineering teams with workloads on the Blockchain Node Engine. Users of archive nodes should pay special attention: historical queries are the hardest to reproduce accurately, so it's better to test in advance rather than in December. For Quicknode, this is a clear victory: the status of officially recommended provider from a hyperscaler with a ready migration path in Google's documentation.
This material is prepared solely for informational purposes and does not constitute financial advice or a recommendation.
Related articles
