← Monitoring index

GetBlock RPC competitor monitor — 2026-07-21

Source: /root/getblock-rpc-competitive-research/monitoring/daily/2026-07-21.md

GetBlock RPC competitor monitor — 2026-07-21

Criterion of the day: Solana / trading latency claims and low-latency infrastructure proof (solana-trading-latency; query hint: "Solana trading latency low latency RPC").

Summary

What really changed / new signals

  1. QuickNode changed many monitored pages (home, pricing, enterprise, blog, chains). The visible additions are mostly navigation/campaign modules, but they include latency/performance proof: homepage module says Core RPC benchmarked 2.5x faster and shows Quicknode 83ms vs Others 1200ms; a case-study module says Supermission: 2s to 50ms average latency across 4 chains, zero failed RPC calls. Source: [QuickNode home](https://www.quicknode.com/), [enterprise](https://www.quicknode.com/enterprise).
  2. Alchemy added/rotated latency-focused content on the blog. Blog now lists [How we fine tune our RPC for speed and reliability](https://www.alchemy.com/blog/how-we-fine-tune-our-rpc-for-speed-and-reliability) dated July 20, 2026 and already had [How we built low-latency RPC infrastructure](https://www.alchemy.com/blog/how-we-built-low-latency-rpc-infrastructure) dated July 6, 2026. Source: [Alchemy blog](https://www.alchemy.com/blog).
  3. Alchemy has the strongest Solana-specific latency page found today. [Alchemy Solana](https://www.alchemy.com/solana) claims fastest data across RPC/heavy methods/gRPC/archival, 10x faster on heavy calls, 20x faster on archival data, ultra-fast gRPC, staked connections for max speed/landing rate, 2x higher throughput, and 99.99% reliability. Treat as vendor claim unless independently benchmarked.
  4. Chainstack added/rotated fresh content: blog now lists Cut RPC costs with a hybrid self-hosted and cloud setup dated July 20, 2026 and Chainstack introduces Robinhood Chain support. For this criterion, its [Trader Nodes](https://chainstack.com/trader-nodes/) page is the strongest proof asset: "for traders, snipers, HFTs", custom region/cloud, and explicit "Latency matters" positioning.
  5. Ankr remains the most numeric broad-performance claimant in monitored pages: homepage says "Avg. response time 56 ms", 99.99% uptime and 70+ blockchains; enterprise claims geo-distribution across 24 metros and custom throughput over 25,000 RPS. Source: [Ankr home](https://www.ankr.com/), [enterprise](https://www.ankr.com/enterprise/).
  6. Moralis is lower-intensity on Solana/trading RPC latency in the monitored pages. Its competitive wedge is real-time/enriched data: Streams, Datashare, Data Feeds, Price API and enterprise SLAs, not explicit HFT/RPC latency proof.

Unchanged / no strong change

Blocked / limited

Competitor notes

QuickNode

Sources: [home](https://www.quicknode.com/), [pricing](https://www.quicknode.com/pricing), [enterprise](https://www.quicknode.com/enterprise), [blog](https://www.quicknode.com/blog), [chains](https://www.quicknode.com/chains), [Solana docs](https://www.quicknode.com/docs/solana), [latency blog URL checked](https://www.quicknode.com/blog/solana-rpc-node-provider-latency).

Alchemy

Sources: [home](https://www.alchemy.com/), [pricing](https://www.alchemy.com/pricing), [enterprise](https://www.alchemy.com/enterprise), [blog](https://www.alchemy.com/blog), [Solana page](https://www.alchemy.com/solana), [low-latency RPC blog](https://www.alchemy.com/blog/how-we-built-low-latency-rpc-infrastructure), [RPC speed/reliability blog](https://www.alchemy.com/blog/how-we-fine-tune-our-rpc-for-speed-and-reliability).

Infura

Sources: [home](https://www.infura.io/), [pricing](https://www.infura.io/pricing), [networks](https://www.infura.io/networks), [blog](https://www.infura.io/blog), [docs](https://docs.infura.io/), [Solana network URL checked](https://www.infura.io/networks/solana).

Chainstack

Sources: [home](https://chainstack.com/), [pricing](https://chainstack.com/pricing/), [protocols](https://chainstack.com/protocols/), [enterprise](https://chainstack.com/enterprise/), [blog](https://chainstack.com/blog/), [docs](https://docs.chainstack.com/docs/platform-introduction), [Trader Nodes](https://chainstack.com/trader-nodes/).

Ankr

Sources: [home](https://www.ankr.com/), [RPC](https://www.ankr.com/rpc/), [enterprise](https://www.ankr.com/enterprise/), [blog](https://www.ankr.com/blog/), [docs](https://www.ankr.com/docs/), [Solana RPC](https://www.ankr.com/rpc/solana/), [Solana docs](https://www.ankr.com/docs/rpc-service/chains/chains-api/solana/).

Moralis

Sources: [home](https://moralis.com/), [pricing](https://moralis.com/pricing/), [chains](https://moralis.com/chains/), [enterprise](https://moralis.com/enterprise/), [blog](https://moralis.com/blog/), [docs](https://docs.moralis.com/).

GetBlock implications

Sales

  1. Prepare a Solana latency objection card against vendor claims: QuickNode 83ms vs 1200ms, 2.5x faster, Supermission 2s to 50ms; Alchemy sub-50ms, 10x heavy calls, 20x archival, 2x throughput; Ankr 56ms and 24 metros.
  2. For trading/MEV prospects, ask discovery questions that expose requirements beyond raw RPC: region, dedicated vs shared endpoints, Jito bundles/priority fees, gRPC/Yellowstone, archival/heavy methods, landing rate, and support SLA.
  3. Mark competitor numbers as vendor claims unless benchmarked; do not let reps repeat them as facts without context.

Product marketing

  1. Create a GetBlock Solana performance page with verifiable methodology: regions tested, methods (getLatestBlockhash, getProgramAccounts, sendTransaction, archival calls), p50/p95, dedicated vs shared, and date of benchmark.
  2. Package existing Solana features into trading language if supported: dedicated nodes, geo-routing, Yellowstone/gRPC, priority fees/Jito bundles, WebSocket stability, archive/heavy-call performance.
  3. Add concise enterprise proof: uptime/SLA, support response, dedicated infra, monitoring/logging, security/compliance.

Content

  1. Publish Best Solana RPC for trading latency: benchmark methodology instead of only vendor comparison copy.
  2. Create comparison pages: GetBlock vs QuickNode Solana RPC latency, GetBlock vs Alchemy Solana RPC, Dedicated Solana RPC for trading bots.
  3. Produce an engineering explainer: Why Solana RPC latency is hard: heavy methods, archival data, gRPC streams, transaction landing.

Opportunities

Tomorrow seed

state.json shows used criteria ai-agent-tooling and solana-trading-latency, but no upcoming criterion queue. Next criterion is not inferable from current state; tomorrow's pre-run JSON should supply it.