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
- 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.
- 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.
- 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
- QuickNode: retained only directly supported status/SLA cells; removed unsupported request-log and alert implications from the old matrix.
- Alchemy: retained status visibility; request logs, endpoint analytics, alerts and SLA history are now explicitly unverified in monitored evidence.
- Infura: upgraded Request logs/visibility, Usage Notifications and SLA wording with exact plan retention.
- Chainstack: normalized Statistics/Node usage, Dedicated Node monitoring, Performance Dashboard and Status Page.
- Ankr: normalized multi-project statistics dashboard, Status and 99.99% uptime as separate claims.
- Moralis, Blockdaemon and Tatum: reclassified real-time notifications as blockchain-event alerts only, not endpoint-health alerting.
- NOWNodes: added API Statistics and separated its 99.95% marketing uptime claim from contractual SLA evidence.
- dRPC: added NodeHaus monitoring and Status; no request-log retention was inferred.
- Blast API: marked observability dimensions not applicable because the vendor explicitly says the service is deprecated.
- Pocket Network / Grove: reset unsupported observability cells to unverified and recorded Grove’s wind-down/current-product transition as a research gap.
- LlamaRPC: retained all cells as unverified because website, docs and status surfaces were inaccessible.
- Allnodes: normalized node monitoring and Status Checker; no SLA claim inferred.
- Lava Network: separated auditable provider benchmarking/real-time routing from its 99.99% marketing uptime claim.
Change assessment: market signal vs noise
Confirmed decision-relevant signals
- QuickNode’s current Enterprise page directly states 99.99% uptime and contractual uptime SLAs.
- Infura’s current pricing page directly specifies request-visibility retention and Usage Notifications.
- Blast API remains deprecated and directs users to Alchemy.
- Grove states it is winding down; Pocket Network continues under a changed, agent/data-services-oriented surface.
Page changes not treated as market changes
- QuickNode pricing, enterprise, blog and chains hashes changed, but navigation and the AI Cookbook banner account for visible extraction differences; only explicit SLA/uptime wording was promoted into the matrix.
- Chainstack blog, Moralis home, NOWNodes blog, dRPC chainlist, Allnodes pages and Tatum docs/blog changed at page level, but no hash change was treated as a product claim by itself.
- New-chain banners, market-cap values, menu restructuring and generic “Loading content” text were excluded from the topic synthesis.
Provider evidence and limitations
QuickNode
- Verified: Status destination; Enterprise 99.99% uptime; contractual uptime SLA wording.
- Not verified: request-log retention, endpoint analytics, alert rules, service-credit mechanics or incident-history completeness.
- Fetch limitation:
/changelogreturned 404. This is a URL failure, not evidence that QuickNode has no changelog. - Sources: home, pricing, enterprise.
Alchemy
- Verified: vendor navigation exposes a Status destination.
- Not verified: request logs, endpoint analytics, alerting, uptime target, contractual SLA or incident-history coverage in today’s monitored page bodies.
- Fetch limitations: the monitored chains and customer-stories URLs returned 404; these stale paths were not converted into negative product claims.
- Source: home.
Infura
- Verified: Request Visibility up to 24 hours on Core and up to 30 days on paid tiers; Usage Notifications; Enterprise Enhanced Support SLA wording.
- Not verified: health-dashboard/status history, uptime target or service credits.
- Source: pricing.
Chainstack
- Verified: Statistics, Node usage, Dedicated Node monitoring, Performance Dashboard and Status Page references.
- Not verified: request-log retention, health-alert semantics, contractual SLA/remedies.
- Sources: home, docs.
Ankr
- Verified: multi-project statistics dashboard on Premium; Status destination; homepage 99.99% uptime claim.
- Not verified: request logs, endpoint-health alerts, contractual SLA, credits or incident-history completeness.
- Sources: RPC, home.
Moralis
- Verified: Streams for real-time blockchain-event monitoring; docs Status destination; enterprise-SLA wording.
- Boundary: blockchain-event delivery is not endpoint-health alerting.
- Not verified: request logs, endpoint analytics, uptime target, incident archive or SLA credits.
- Sources: home, enterprise, docs.
NOWNodes
- Verified: API Statistics; homepage 99.95% API uptime claim.
- Not verified: request logs, health alerts/dashboard, contractual SLA or incident history.
- Fetch limitation: legacy Postman documentation URL returned 404.
- Sources: pricing, home.
dRPC
- Verified: NodeHaus RPC management/monitoring; Status destination.
- Not verified: request logs, customer analytics detail, alerts, contractual SLA or incident history.
- Sources: home, docs.
Blast API
- Verified: service deprecation notice and migration direction to Alchemy.
- Classification: observability capability comparison is not applicable to the deprecated service; Alchemy capabilities were not attributed to Blast.
- Source: deprecation notice.
Blockdaemon
- Verified: real-time on-chain transaction/event notifications; Status destination.
- Boundary: event monitoring was not treated as infrastructure-health alerting.
- Fetch limitations: monitored RPC and pricing paths returned 404; current home/docs remained reachable.
- Sources: home, docs.
Tatum
- Verified: Notifications for real-time blockchain-event tracking; docs Status destination.
- Not verified: request logs, endpoint analytics, infrastructure-health alerts or SLA history.
- Fetch limitation: the monitored supported-blockchains URL returned 404.
- Sources: home, docs.
Pocket Network / Grove
- Verified: Grove wind-down notice; Pocket Network currently presents a changed data-services/agentic surface.
- Not verified: current production RPC request logs, analytics, alerts, status or SLA history.
- Fetch limitation: Grove docs DNS resolution failed.
- Sources: Grove, Pocket Network.
LlamaRPC
- Not verified: all topic dimensions.
- Fetch limitations: website and chains returned HTTP 526; docs and status DNS resolution failed. These failures are evidence gaps, not proof the product lacks observability features.
Allnodes
- Verified: node monitoring service and Status Checker surface.
- Not verified: request logs, endpoint analytics, alert configuration or SLA history.
- Fetch limitations: monitored
/nodesand/blogpaths returned 404; home/pricing/help were reachable. - Sources: home, help.
Lava Network
- Verified: provider performance described as benchmarked/auditable, real-time routing, automatic failover and a 99.99% uptime marketing claim.
- Not verified: customer request logs, customer-configurable alerts, contractual SLA/credits or incident archive.
- Fetch limitations: monitored developers and network paths returned 404; home/docs/blog remained reachable.
- Source: home.
Cross-provider implications for GetBlock
- Sales: ask prospects whether they need request-level forensic retention or only usage totals; Infura’s published 24-hour/30-day retention creates a concrete benchmark GetBlock can answer precisely.
- Product marketing: publish separate, evidence-backed pages for request logs, analytics, operational alerts, public status and contractual SLA terms. Avoid combining blockchain-event notifications with endpoint-health monitoring.
- Content: create a buyer guide to RPC observability procurement covering retention, exportability, WebSocket/gRPC visibility, incident archives, SLA measurement and service credits.
Research gaps / next pass
- Recover active official LlamaRPC domains and current Pocket Network production-RPC documentation.
- Collect direct dashboard docs for QuickNode, Alchemy, Chainstack and dRPC.
- Verify service-credit and uptime-calculation language for every SLA claim.
- Inspect direct status pages for historical incident depth without mistaking page availability for incident transparency.
- Verify whether Moralis, Blockdaemon and Tatum provide infrastructure-health alerts in addition to on-chain event notifications.
Publishing and pipeline status
- Pre-run encyclopedia publisher reported success with 136 published URLs, but that run preceded this manual consolidation; the publisher must be rerun after these Markdown updates.
- Agentic routing paper update reported
ok=true,paper_updated=true, with 61 routed evidence items. The published paper URL reported by the pipeline is Agentic routing for RPC.