| Date | 13 Jun 2026 |
|---|
Google Cloud has announced the complete deprecation and upcoming shutdown of Blockchain Node Engine, its fully managed blockchain node-hosting service. The service, along with associated Blockchain RPC endpoints, will be shut down on December 15, 2026, with existing nodes and endpoints deleted on that date.
This marks the end of a service that launched in private preview in late 2022, reached general availability in mid-2023, and provided developers and organizations with dedicated, enterprise-grade nodes for blockchains including Ethereum (full and archive), Polygon, and Solana.
Timeline and Immediate Impact
- June 15, 2026: New node creation and provisioning of new Blockchain RPC endpoints will be disabled. Existing nodes continue to operate with critical updates until the final shutdown.
- December 15, 2026: Full shutdown. All remaining nodes and endpoints will be deleted, and dependent workloads will fail without migration.
The deprecation directly affects node operators relying on Google Cloud’s managed infrastructure for reliable RPC access, transaction relaying, smart contract deployment, dApp development, and blockchain data ingestion. Archive nodes, in particular, which enabled full historical data queries, will no longer be available through this service.
Official Migration Path
Google Cloud’s primary guidance is a partnership with QuickNode as the recommended RPC infrastructure provider. Customers are directed to migrate workloads to QuickNode to avoid disruption.
Migration steps outlined in the official guide include:
- Provision new nodes/endpoints via QuickNode’s Google Cloud Marketplace offering (with potential incentives) or directly through the QuickNode platform.
- Update application configurations to point to the new endpoints.
- Validate and test workloads on the new infrastructure.
- Delete legacy Blockchain Node Engine resources.
Official Migration Guide: Migrate to QuickNode before Dec 15, 2026
Impact on Open-Source Tooling and Ecosystem
The shutdown will ripple through open-source projects and tooling that integrated with or assumed access to managed Blockchain Node Engine endpoints. Developers using custom scripts, monitoring tools, CI/CD pipelines, or libraries built around Google Cloud’s stable, dedicated nodes will need to refactor configurations, update endpoint handling, authentication (including API keys with rate limits), and potentially adjust for differences in performance, pricing, or feature sets offered by alternative providers.
While Google Cloud continues to support self-managed nodes on its broader infrastructure (Compute Engine, GKE, etc.), the fully managed, low-ops experience of Blockchain Node Engine is ending. This shift signals a strategic move away from operating managed blockchain infrastructure in favor of partnering with specialized Web3 providers.
Important links:
- Migrate to QuickNode – Detailed migration guidance.
- Blockchain Node Engine Product Page – Service overview and features (still live as of now).
Google Cloud has framed the transition as an opportunity for customers to leverage QuickNode’s specialized platform while maintaining access to enterprise-grade blockchain infrastructure. The broader Web3 community on Google Cloud is encouraged to explore the company’s ongoing Web3 startup programs and other cloud services.
We’ll monitor the migration process, any additional partner details, and community adaptations in the open-source space as the December 15 deadline approaches.