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.
ProviderMigration guidanceEndpoint / API compatibilityParallel cutover / zero-downtime migrationRouting / automatic failoverBackup / redundancy optionDirect sourcesEvidence status / freshness
QuickNodeNot verified in monitored public evidenceNot verified in monitored public evidenceNot verified in monitored public evidenceNot verified in monitored public evidenceNot verified in monitored public evidencepricing0/5; checked 2026-10-13. Pricing exposes dedicated infrastructure and uptime SLA language, but no criterion-specific migration/failover proof in the capture.
AlchemyNot verified in monitored public evidencePublicly evidenced: official docs describe standard JSON-RPC and chain-specific APIs.Not verified in monitored public evidenceNot verified in monitored public evidenceNot verified in monitored public evidencedocs1/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.
InfuraNot verified in monitored public evidenceNot verified in monitored public evidenceNot verified in monitored public evidenceNot verified in monitored public evidenceNot verified in monitored public evidencedocs0/5; checked 2026-10-13. Generic managed-API and high-availability wording is insufficient for these specific claims.
ChainstackPublicly 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 evidencePublicly 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>pricing4/5; checked 2026-10-13. No explicit parallel-run, rollback, or zero-downtime migration procedure was captured.
AnkrNot verified in monitored public evidenceNot verified in monitored public evidenceNot verified in monitored public evidenceNot verified in monitored public evidenceNot verified in monitored public evidencedocs0/5; checked 2026-10-13.
MoralisPublicly evidenced: the documentation includes a Migration Guides section and the product surface prompts users migrating from the API.Not verified in monitored public evidenceNot verified in monitored public evidenceNot verified in monitored public evidenceNot verified in monitored public evidencedocs<br>home1/5; checked 2026-10-13. The capture confirms guidance exists, but not a named Infura/Alchemy/QuickNode RPC cutover path.
NOWNodesNot verified in monitored public evidenceNot verified in monitored public evidenceNot verified in monitored public evidencePublicly evidenced: first-party FAQ says GEO-balanced infrastructure routes requests through the optimal region.Not verified in monitored public evidencehome1/5; checked 2026-10-13. Geo-routing is evidenced; automatic failure detection/fallback is not explicit in the monitored text.
dRPCNot verified in monitored public evidencePublicly evidenced: NodeCore is stated to work across any chain, EVM-compatible or not.Not verified in monitored public evidencePublicly 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>docs3/5; checked 2026-10-13. No direct migration/cutover playbook was captured.
Blast APIPublicly 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 notice2/2 applicable dimensions; checked 2026-10-13. Blast API is not an active procurement alternative.
BlockdaemonNot verified in monitored public evidenceNot verified in monitored public evidenceNot verified in monitored public evidenceNot verified in monitored public evidenceNot verified in monitored public evidencedocs0/5; checked 2026-10-13. Generic “blockchain compatibility” navigation was not treated as provider migration compatibility.
TatumNot verified in monitored public evidenceNot verified in monitored public evidenceNot verified in monitored public evidencePublicly 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.home2/5; checked 2026-10-13. Routing continuity is evidenced; a migration runbook and zero-downtime cutover are not.
Pocket Network / GroveNot verified in monitored public evidenceNot verified in monitored public evidenceNot verified in monitored public evidenceNot verified in monitored public evidenceNot verified in monitored public evidenceGrove farewell<br>Pocket Network0/5; checked 2026-10-13. Grove is winding down and its docs hostname did not resolve; Pocket Network continues with a changed product surface.
LlamaRPCNot verified in monitored public evidenceNot verified in monitored public evidenceNot verified in monitored public evidenceNot verified in monitored public evidenceNot 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.
AllnodesNot verified in monitored public evidenceNot verified in monitored public evidenceNot verified in monitored public evidencePublicly 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.pricing2/5; checked 2026-10-13. Volatile price; verify before sales use.
Lava NetworkNot verified in monitored public evidenceNot verified in monitored public evidenceNot verified in monitored public evidencePublicly 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.home2/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

  1. 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.
  2. 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.
  3. 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.
  4. Price backup capacity separately. Confirm whether standby requests, duplicate traffic, dedicated failover nodes, egress, and retained archive capacity are billable.
  5. Verify all volatile prices, SLA language, and availability with sales before procurement or external GetBlock sales use.

Direct sources

Research priorities

  1. Obtain direct migration runbooks for QuickNode, Alchemy, Infura, Ankr, Blockdaemon, Pocket Network, and LlamaRPC, especially named Infura/Alchemy/QuickNode source-provider paths.
  2. Verify Chainstack’s provider-specific guides at their direct leaf URLs and capture whether they prescribe parallel run, acceptance tests, and rollback.
  3. Validate whether NOWNodes GEO routing includes health-based automatic failover and whether it spans independent backends or only regions.
  4. Capture contractual details for Allnodes failover-node activation, Tatum priority failover, dRPC provider diversity, and Lava provider selection.
  5. Build a reproducible migration test: method parity, WebSocket reconnects, archive/debug results, stale-head detection, transaction broadcast behavior, and forced upstream outage.