GetBlock RPC competitor monitor — 2026-10-14

Criterion of the day: Observability and analytics: request logs, endpoint analytics, alerts, health dashboards, incident history and SLA transparency (observability-analytics).

Executive summary

Today’s consolidation replaced the prior overly broad 4-column classification with five buyer-specific dimensions and revalidated all 15 monitored providers against direct vendor pages. The strongest specific public signal is Infura’s published Request Visibility retention (up to 24 hours on Core and up to 30 days on paid tiers). QuickNode explicitly publishes 99.99% uptime and contractual uptime SLAs for Enterprise. Chainstack exposes Statistics, Node usage, Dedicated Node monitoring, a Performance Dashboard and Status Page.

No provider is publicly evidenced across every dimension. In particular, status-page links and marketing uptime percentages do not establish incident-history completeness, contractual measurement terms or service-credit remedies.

Decision-relevant findings

  1. Infura request visibility is now normalized precisely. The pricing comparison lists Request Visibility with up to 24 hours on Core and up to 30 days on Developer, Team and Enterprise, plus Usage Notifications. This updates Infura’s cells for request logs, alerts and SLA wording. Direct source.
  2. QuickNode’s SLA evidence is explicit but incomplete for remedies. Enterprise states 99.99% uptime and contractual uptime SLAs; today’s monitored public pages did not verify service-credit mechanics or a comparable incident archive. Enterprise and pricing.
  3. Chainstack has the broadest directly named monitoring surface in today’s capture. Its docs index lists Statistics, Node usage and Dedicated Node monitoring, while the main site links a Performance Dashboard and Status Page. The monitored pages do not establish request-log retention or contractual SLA remedies. Docs and home.

Matrix changes made

Change assessment: market signal vs noise

Confirmed decision-relevant signals

Page changes not treated as market changes

Provider evidence and limitations

QuickNode

Alchemy

Infura

Chainstack

Ankr

Moralis

NOWNodes

dRPC

Blast API

Blockdaemon

Tatum

Pocket Network / Grove

LlamaRPC

Allnodes

Lava Network

Cross-provider implications for GetBlock

Research gaps / next pass

  1. Recover active official LlamaRPC domains and current Pocket Network production-RPC documentation.
  2. Collect direct dashboard docs for QuickNode, Alchemy, Chainstack and dRPC.
  3. Verify service-credit and uptime-calculation language for every SLA claim.
  4. Inspect direct status pages for historical incident depth without mistaking page availability for incident transparency.
  5. Verify whether Moralis, Blockdaemon and Tatum provide infrastructure-health alerts in addition to on-chain event notifications.

Publishing and pipeline status