Google Cloud to Shut Down Blockchain Node Engine and RPC Services on Dec. 15, 2026
Key Takeaways
- β’Google Cloud will shut down its Blockchain Node Engine and Blockchain RPC services on Dec. 15, 2026, at which point all existing nodes and RPC endpoints will be deleted.
- β’Quicknode has been named the recommended replacement provider, and customers can procure its services through the Google Cloud Marketplace or directly from Quicknode.
- β’Google Cloud began restricting the services on June 15 by the creation of new nodes and the provisioning of new Blockchain RPC endpoints.
- β’The required migration involves provisioning replacement infrastructure through Quicknode, updating application endpoint configurations, testing and validating workloads, and deleting legacy resources.
- β’Businesses running production applications, wallets, decentralized applications, and blockchain data services face potential service interruptions if they wait until December to complete migration.

Google Cloud will shut down its Blockchain Node Engine and Blockchain RPC services on Dec. 15, 2026, requiring customers to migrate their blockchain infrastructure before that date. The company has named Quicknode as its recommended replacement provider for workloads moving off the retiring services.
The decision represents a significant shift for developers and businesses that use Google Cloud to host blockchain nodes or connect applications to blockchain networks. Blockchain Node Engine let customers run dedicated blockchain nodes on Google-managed infrastructure, while Blockchain RPC offered managed endpoints that applications call to read on-chain data and send transactions without operating their own servers. According to Google Cloud's official migration guidance, existing nodes and RPC endpoints will be deleted on the shutdown date.
Migration Deadline Approaches
Google Cloud began restricting the services on June 15, disabling the creation of new nodes and the provisioning of new Blockchain RPC endpoints. Existing infrastructure continued to operate throughout the transition period, but customers now have until Dec. 15 to complete their. Google Cloud warns that workloads depending on the legacy resources will fail once the shutdown takes effect.
The migration process involves several key steps:
- Provision replacement nodes or endpoints through Quicknode.
- Update applications and services with the new endpoint configurations.
- Test and validate workloads before switching over.
- Delete legacy Blockchain Node Engine resources.
Customers can provision Quicknode services through the Google Cloud Marketplace or directly through Quicknode. That dependency chain is what gives the deadline its weight: an application whose RPC endpoint is deleted without a replacement loses its connection to the blockchain, which is why Google Cloud ties the deletion of legacy resources directly to the shutdown date.
Quicknode Becomes Recommended Provider
Google Cloud has selected Quicknode as its recommended RPC infrastructure provider for customers leaving Blockchain Node Engine and Blockchain RPC. The partnership offers existing users a direct migration path while allowing them to keep using cloud infrastructure. Quicknode says customers can also maintain procurement through the Google Cloud Marketplace, though teams must still update their applications and verify their workloads before the final shutdown.
Google Cloud first introduced Blockchain Node Engine in 2022 as a managed node-hosting service for Web3 developers, and the retirement of both services now routes those workloads to a company that specializes in blockchain RPC infrastructure. The deadline leaves a limited window for businesses running production applications, wallets, decentralized applications and blockchain data services. Companies that wait until December could face service interruptions if they have overlooked an endpoint or a dependent workload.
Google Cloud's announcement makes the Dec. 15 date definitive. Customers should treat the migration as an infrastructure transition rather than an optional upgrade, and completing testing well ahead of the deadline can reduce the risk of outages when the legacy services disappear.
Source: CryptoMeter io