Google Cloud to Shut Down Blockchain Node Engine and Recommend Quicknode

Google Cloud is exiting the blockchain node sector, setting a hard shutdown date of December 15, 2026, for both its Blockchain Node Engine and Blockchain RPC services. The wind-down process began on June 15, 2026, when Google stopped provisioning new node creation and new Blockchain RPC endpoints.

Current nodes and endpoints remain online during the transition period with limited support. Google stated it will continue to ship critical updates, but customers should expect the products to remain static rather than gain new features. Teams running production workloads must now plan migrations for dedicated full nodes, archive nodes, and shared endpoints.

The Google Cloud Deprecation Timeline and Deletion Rules

The wind-down operates in two distinct stages across a six-month window. Since June 15, 2026, users have been unable to provision new resources. Between that date and the final cutoff, existing infrastructure stays operational under limited support conditions. On December 15, 2026, every remaining node and endpoint will be permanently deleted from the platform.

Google Cloud documentation outlines a specific asymmetry regarding how resources will be removed at the final deadline. Google will automatically delete any remaining RPC endpoints at shutdown. Dedicated nodes, however, remain on the customer checklist for manual cleanup inside the Google Cloud console.

Transitioning Infrastructure to Quicknode

Google has named Quicknode as its officially recommended RPC infrastructure provider for migrating customers. Teams can provision replacement infrastructure through two primary channels. Customers can sign up directly on Quicknode’s platform, or they can provision through the Quicknode listing on Google Cloud Marketplace to access Google Cloud incentives.

Migration documentation from Google Cloud instructs builders to follow a four-step checklist. Teams must provision replacement nodes or endpoints, update their application configurations and RPC URLs, validate workloads on the new setup, and finally delete legacy Blockchain Node Engine nodes from their accounts.

Technical Impact on Ethereum, Polygon, and Solana Builders

Blockchain Node Engine served as a managed infrastructure layer to eliminate the tedium of running personal validator and query hardware. The service primarily supported Ethereum Mainnet and its testnets, alongside Polygon and Solana. It offered dedicated full nodes that track the current chain state alongside archive nodes that maintain complete historical states for analytics and indexing.

Engineering teams utilizing archive nodes face the most complex migration tasks. Historical data queries are notoriously difficult to replicate cleanly across providers, giving archive users an urgent reason to test replacements early. Quicknode steps into this market vacuum as a major beneficiary, securing a recommended hyperscaler status and a direct integration pathway inside official Google documentation.

Migrate to Quicknode before Dec 15, 2026 | Blockchain Node Engine … Send feedback Blockchain Node Engine and Blockchain RPC will be shut down on December 15, 2026. Google Cloud has partnered with Quicknode to serve as the recommended RPC infrastructure provider for our customers moving forward.

docs.cloud.google.com