Migration messaging: migrate from Infura/Alchemy/QuickNode, compatibility, zero-downtime migration, backup and failover
Last consolidated: 2026-10-13
Coverage: 9/15 providers have at least one directly evidenced comparison dimension; 0/15 have direct public evidence across all five dimensions. Evidence was checked against the monitored first-party surface on 2026-10-13.
> Evidence semantics: “Not verified in monitored public evidence” means the captured first-party pages were insufficient; it is not a claim that the capability is absent. “Not applicable” is used only for Blast API’s discontinued service. Marketing language about uptime or generic chain compatibility is not treated as proof of a zero-downtime migration or provider-level drop-in compatibility.
Comparison schema
- Migration guidance: a first-party migration guide, named source-provider path, or explicit transition offer.
- Endpoint / API compatibility: evidence that a workload can retain a standard interface or primarily swap endpoints; chain-level “EVM-compatible” wording alone does not qualify.
- Parallel cutover / zero-downtime migration: an explicit migration procedure or promise covering parallel run, traffic shifting, rollback, or uninterrupted cutover.
- Routing / automatic failover: traffic routing, health-based fallback, or failover is stated directly.
- Backup / redundancy option: a separately described failover node, multi-provider/network redundancy, or comparable backup architecture.
| Provider | Migration guidance | Endpoint / API compatibility | Parallel cutover / zero-downtime migration | Routing / automatic failover | Backup / redundancy option | Direct sources | Evidence status / freshness |
|---|---|---|---|---|---|---|---|
| QuickNode | Not verified in monitored public evidence | Not verified in monitored public evidence | Not verified in monitored public evidence | Not verified in monitored public evidence | Not verified in monitored public evidence | pricing | 0/5; checked 2026-10-13. Pricing exposes dedicated infrastructure and uptime SLA language, but no criterion-specific migration/failover proof in the capture. |
| Alchemy | Not verified in monitored public evidence | Publicly evidenced: official docs describe standard JSON-RPC and chain-specific APIs. | Not verified in monitored public evidence | Not verified in monitored public evidence | Not verified in monitored public evidence | docs | 1/5; checked 2026-10-13. A customer quote saying “zero downtime” is operational evidence, not a migration procedure, so it is excluded from the cutover cell. |
| Infura | Not verified in monitored public evidence | Not verified in monitored public evidence | Not verified in monitored public evidence | Not verified in monitored public evidence | Not verified in monitored public evidence | docs | 0/5; checked 2026-10-13. Generic managed-API and high-availability wording is insufficient for these specific claims. |
| Chainstack | Publicly evidenced: documentation index exposes “Migrate to Chainstack,” “Migrate with AI,” and named provider paths; it describes swapping endpoints. | Publicly evidenced: the migration overview describes swapping provider endpoints. | Not verified in monitored public evidence | Publicly evidenced: Global Node routes to an available region; Self-Hosted pricing states automated failover. | Publicly evidenced: geo-balanced regions and Self-Hosted failover are described. | docs<br>home<br>pricing | 4/5; checked 2026-10-13. No explicit parallel-run, rollback, or zero-downtime migration procedure was captured. |
| Ankr | Not verified in monitored public evidence | Not verified in monitored public evidence | Not verified in monitored public evidence | Not verified in monitored public evidence | Not verified in monitored public evidence | docs | 0/5; checked 2026-10-13. |
| Moralis | Publicly evidenced: the documentation includes a Migration Guides section and the product surface prompts users migrating from the API. | Not verified in monitored public evidence | Not verified in monitored public evidence | Not verified in monitored public evidence | Not verified in monitored public evidence | docs<br>home | 1/5; checked 2026-10-13. The capture confirms guidance exists, but not a named Infura/Alchemy/QuickNode RPC cutover path. |
| NOWNodes | Not verified in monitored public evidence | Not verified in monitored public evidence | Not verified in monitored public evidence | Publicly evidenced: first-party FAQ says GEO-balanced infrastructure routes requests through the optimal region. | Not verified in monitored public evidence | home | 1/5; checked 2026-10-13. Geo-routing is evidenced; automatic failure detection/fallback is not explicit in the monitored text. |
| dRPC | Not verified in monitored public evidence | Publicly evidenced: NodeCore is stated to work across any chain, EVM-compatible or not. | Not verified in monitored public evidence | Publicly evidenced: NodeCore includes load balancing and auto-fallbacks; NodeCloud advertises AI-powered load balancing. | Publicly evidenced: NodeCloud says it is backed by 60+ RPC providers and eight geo clusters. | home<br>docs | 3/5; checked 2026-10-13. No direct migration/cutover playbook was captured. |
| Blast API | Publicly evidenced: the deprecation page explicitly directs customers to migrate traffic to Alchemy and offers an Alchemy-credit conversion or refund. | Not applicable — Blast products are no longer available. | Publicly evidenced as transition messaging only: the page says customers can continue development “without interruption”; no technical cutover steps are published in the capture. | Not applicable — service deprecated. | Not applicable — service deprecated. | deprecation notice | 2/2 applicable dimensions; checked 2026-10-13. Blast API is not an active procurement alternative. |
| Blockdaemon | Not verified in monitored public evidence | Not verified in monitored public evidence | Not verified in monitored public evidence | Not verified in monitored public evidence | Not verified in monitored public evidence | docs | 0/5; checked 2026-10-13. Generic “blockchain compatibility” navigation was not treated as provider migration compatibility. |
| Tatum | Not verified in monitored public evidence | Not verified in monitored public evidence | Not verified in monitored public evidence | Publicly evidenced: Tatum Gateway states failover, load balancing, priority failover, method routing, and support for adding provider endpoints. | Publicly evidenced: multiple provider endpoints can sit behind the routing gateway. | home | 2/5; checked 2026-10-13. Routing continuity is evidenced; a migration runbook and zero-downtime cutover are not. |
| Pocket Network / Grove | Not verified in monitored public evidence | Not verified in monitored public evidence | Not verified in monitored public evidence | Not verified in monitored public evidence | Not verified in monitored public evidence | Grove farewell<br>Pocket Network | 0/5; checked 2026-10-13. Grove is winding down and its docs hostname did not resolve; Pocket Network continues with a changed product surface. |
| LlamaRPC | Not verified in monitored public evidence | Not verified in monitored public evidence | Not verified in monitored public evidence | Not verified in monitored public evidence | Not verified in monitored public evidence | — | 0/5; checked 2026-10-13. Main pages returned HTTP 526 and docs/status hostnames did not resolve, so capability claims could not be verified. |
| Allnodes | Not verified in monitored public evidence | Not verified in monitored public evidence | Not verified in monitored public evidence | Publicly evidenced: a paid “Failover Node” add-on is listed. | Publicly evidenced: failover node add-on starts at $160/month on Advanced and $320/month on Enterprise in the captured pricing text. | pricing | 2/5; checked 2026-10-13. Volatile price; verify before sales use. |
| Lava Network | Not verified in monitored public evidence | Not verified in monitored public evidence | Not verified in monitored public evidence | Publicly evidenced: requests are scored and routed to reliable nodes with automatic failover across providers and chains. | Publicly evidenced: an open network of independent providers and geographically distributed access are positioned as removing a single point of failure. | home | 2/5; checked 2026-10-13. This is architectural redundancy evidence, not a customer migration procedure. |
Cross-provider readout
- Breadth: 9/15 providers have evidence in at least one dimension. Six have no criterion-specific evidence in the monitored surface: QuickNode, Infura, Ankr, Blockdaemon, Pocket Network / Grove, and LlamaRPC.
- Completeness: no active provider publicly evidences all five dimensions. Chainstack is the broadest captured public story at 4/5, but still lacks a captured parallel-run/rollback/zero-downtime cutover procedure.
- Most evidenced dimension: routing/failover is directly stated by Chainstack, NOWNodes, dRPC, Tatum, Allnodes, and Lava Network.
- Largest gap: no active provider in this capture publishes an explicit, criterion-complete zero-downtime migration procedure with parallel traffic, acceptance checks, rollback, and ownership boundaries.
- Important lifecycle signal: Blast API is deprecated and routes users to Alchemy; Grove is winding down while Pocket Network continues under a different product direction. These are migration triggers, not normal feature comparisons.
Buyer guidance
- Ask vendors to separate drop-in API compatibility from chain compatibility and to enumerate unsupported methods, WebSocket behavior, archive depth, batch limits, and authentication changes.
- Require a written cutover plan: dual-write or shadow traffic, data/head consistency checks, DNS/endpoint switch, rollback threshold, connection draining, and named incident owner.
- Test failover under stale-head, method-specific error, regional outage, rate-limit, and provider-wide outage conditions; “load balancing” alone does not prove safe fallback.
- Price backup capacity separately. Confirm whether standby requests, duplicate traffic, dedicated failover nodes, egress, and retained archive capacity are billable.
- Verify all volatile prices, SLA language, and availability with sales before procurement or external GetBlock sales use.
Direct sources
- QuickNode: pricing — checked 2026-10-13.
- Alchemy: documentation — checked 2026-10-13.
- Infura: documentation — checked 2026-10-13.
- Chainstack: platform documentation, home / Global Node, pricing / Self-Hosted — checked 2026-10-13.
- Ankr: documentation — checked 2026-10-13.
- Moralis: documentation, home — checked 2026-10-13.
- NOWNodes: home / FAQ — checked 2026-10-13.
- dRPC: home / product FAQ, load-balancing docs index — checked 2026-10-13.
- Blast API: deprecation and Alchemy migration notice — checked 2026-10-13.
- Blockdaemon: documentation — checked 2026-10-13.
- Tatum: home / Gateway — checked 2026-10-13.
- Pocket Network / Grove: Grove farewell, Pocket Network — checked 2026-10-13.
- Allnodes: pricing — checked 2026-10-13.
- Lava Network: home — checked 2026-10-13.
Research priorities
- Obtain direct migration runbooks for QuickNode, Alchemy, Infura, Ankr, Blockdaemon, Pocket Network, and LlamaRPC, especially named Infura/Alchemy/QuickNode source-provider paths.
- Verify Chainstack’s provider-specific guides at their direct leaf URLs and capture whether they prescribe parallel run, acceptance tests, and rollback.
- Validate whether NOWNodes GEO routing includes health-based automatic failover and whether it spans independent backends or only regions.
- Capture contractual details for Allnodes failover-node activation, Tatum priority failover, dRPC provider diversity, and Lava provider selection.
- Build a reproducible migration test: method parity, WebSocket reconnects, archive/debug results, stale-head detection, transaction broadcast behavior, and forced upstream outage.