Google Cloud Sets Dec. 15 Deadline to Shut Down Blockchain Services
Google Cloud will shut down Blockchain Node Engine and Blockchain RPC on Dec. 15, 2026, forcing customers to migrate their blockchain infrastructure before the deadline. Google Cloud has partnered with Quicknode as its recommended replacement for customers moving their workloads.
The move marks a significant change for developers and businesses that use Google Cloud to host blockchain nodes or connect applications to blockchain networks. Google Cloud’s official migration guidance confirms that existing nodes and RPC endpoints will be deleted on the shutdown date.
Migration Deadline Approaches
Google Cloud began limiting the services on June 15, when it disabled new node creation and new Blockchain RPC endpoint provisioning. Existing infrastructure continued operating during the transition period.
Customers now have until Dec. 15 to complete their migration. Google Cloud warns that workloads relying on the legacy resources will fail after the shutdown.
The migration process includes 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.
Google Cloud says customers can provision Quicknode services through the Google Cloud Marketplace or directly through Quicknode.
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 gives existing users a direct migration path while allowing them to continue using cloud infrastructure.
Quicknode also says customers can maintain procurement through the Google Cloud Marketplace. However, teams must still update their applications and verify their workloads before the final shutdown.
The deadline creates 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 dependent workload.
Google Cloud’s announcement makes the Dec. 15 date definitive. Customers should therefore treat the migration as an infrastructure transition rather than an optional upgrade. Completing testing well before the deadline can reduce the risk of outages when the legacy services disappear.