Observability and analytics: request logs, endpoint analytics, alerts, health dashboards, incident history and SLA transparency

Last consolidated: 2026-10-14 Comparison date: 2026-10-14 Coverage: 12/15 providers have at least one directly evidenced dimension; 0/15 have public evidence across all five dimensions. Blast API is deprecated; Pocket Network/Grove and LlamaRPC have unresolved current-product evidence gaps.

> Evidence semantics: “Publicly evidenced” means a direct vendor page explicitly supports the cell. “Not verified in monitored public evidence” means the monitored/direct sources are insufficient; it is not a claim that the capability is absent. “Not applicable” is used only for Blast API because the vendor says the service is deprecated. Availability, retention, SLA remedies and plan eligibility must be verified before sales use.

Comparison schema

  • Request logs / visibility: per-request history or request-level visibility, including published retention.
  • Endpoint analytics / statistics: usage, traffic or endpoint statistics surfaced to the customer.
  • Alerts / notifications: operational or usage notifications; blockchain-event notifications are identified as such and are not treated as infrastructure-health alerts.
  • Health / status dashboards: public status, performance or customer-facing monitoring surfaces.
  • Incident history / SLA transparency: published uptime or contractual-SLA wording. A marketing uptime claim is not treated as a contractual remedy or incident history.
ProviderRequest logs / visibilityEndpoint analytics / statisticsAlerts / notificationsHealth / status dashboardsIncident history / SLA transparencyDirect sourcesCoverage
QuickNodeNot verified in monitored public evidenceNot verified in monitored public evidenceNot verified in monitored public evidencePublicly evidenced: vendor navigation exposes a Status destinationPublicly evidenced: Enterprise states 99.99% uptime and contractual uptime SLAs; service credits and incident-history detail were not verifiedhome · enterprise · pricing2/5
AlchemyNot verified in monitored public evidenceNot verified in monitored public evidenceNot verified in monitored public evidencePublicly evidenced: vendor navigation exposes “Status — Check our systems' status”Not verified in monitored public evidencehome1/5
InfuraPublicly evidenced: “Request Visibility” is listed with up to 24 hours on Core and up to 30 days on paid tiersNot verified in monitored public evidencePublicly evidenced: “Usage Notifications” is listed in the plan comparisonNot verified in monitored public evidencePartially evidenced: Enterprise lists an “Enhanced Support SLA”; uptime target, incident history and service credits were not verifiedpricing3/5
ChainstackNot verified in monitored public evidencePublicly evidenced: docs index lists Statistics and Node usagePublicly evidenced: docs index lists Dedicated Node monitoringPublicly evidenced: vendor links a Performance Dashboard and Status PageNot verified in monitored public evidencehome · docs3/5
AnkrNot verified in monitored public evidencePublicly evidenced: Premium advertises a multi-project statistics dashboardNot verified in monitored public evidencePublicly evidenced: RPC product navigation exposes StatusPartially evidenced: homepage claims 99.99% uptime; contractual SLA, credits and incident history were not verifiedrpc · home3/5
MoralisNot verified in monitored public evidenceNot verified in monitored public evidencePublicly evidenced for blockchain events only: Streams monitors real-time blockchain events; this is not verified as infrastructure-health alertingPublicly evidenced: documentation exposes a Status destinationPartially evidenced: enterprise material references enterprise SLAs; target, credits and incident history were not verifiedhome · enterprise · docs3/5
NOWNodesNot verified in monitored public evidencePublicly evidenced: pricing lists API StatisticsNot verified in monitored public evidenceNot verified in monitored public evidencePartially evidenced: homepage claims 99.95% API uptime; contractual remedies and incident history were not verifiedpricing · home2/5
dRPCNot verified in monitored public evidencePublicly evidenced: NodeHaus is described as RPC management and monitoring for chainsNot verified in monitored public evidencePublicly evidenced: vendor navigation exposes StatusNot verified in monitored public evidencehome · docs2/5
Blast APINot applicable — service deprecatedNot applicable — service deprecatedNot applicable — service deprecatedNot applicable — service deprecatedNot applicable — service deprecateddeprecation noticeN/A
BlockdaemonNot verified in monitored public evidenceNot verified in monitored public evidencePublicly evidenced for on-chain events only: docs offer real-time notifications for transactions/events; not verified as infrastructure-health alertingPublicly evidenced: docs expose a Status destinationNot verified in monitored public evidencedocs2/5
TatumNot verified in monitored public evidenceNot verified in monitored public evidencePublicly evidenced for blockchain events only: Notifications provides real-time blockchain event trackingPublicly evidenced: docs expose a Status destinationNot verified in monitored public evidencehome · docs2/5
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 evidence; Grove says it is winding down, while Pocket Network continues with a changed product focusGrove notice · Pocket Network0/5
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; monitored web, docs and status surfaces were inaccessible—0/5
AllnodesNot verified in monitored public evidenceNot verified in monitored public evidencePublicly evidenced: platform presents node monitoring as a servicePublicly evidenced: site navigation exposes Status CheckerNot verified in monitored public evidencehome · help2/5
Lava NetworkNot verified in monitored public evidencePublicly evidenced: provider performance is described as benchmarked and auditableNot verified in monitored public evidencePublicly evidenced: real-time provider scoring/routing and automatic failover are describedPartially evidenced: homepage claims 99.99% uptime; contractual SLA, credits and incident history were not verifiedhome3/5

Cross-provider readout

  • Breadth: 12 of 15 providers have at least one current, directly evidenced observability/SLA dimension. Blast API is excluded from the denominator for capability completeness because it is explicitly deprecated, but remains in the monitored universe.
  • Completeness: no provider has public evidence for all five dimensions. Request-level visibility is the least evidenced area: only Infura’s monitored pricing page states a retention window.
  • Most common surface: status/health destinations or monitoring claims are publicly visible for QuickNode, Alchemy, Chainstack, Ankr, Moralis, dRPC, Blockdaemon, Tatum, Allnodes and Lava Network.
  • SLA caveat: QuickNode explicitly states contractual uptime SLAs. Infura mentions an Enhanced Support SLA, while Ankr, NOWNodes and Lava publish uptime claims; none of today’s monitored pages disclosed service-credit mechanics or a normalized incident-history comparison.
  • Open evidence gaps: Pocket Network/Grove and LlamaRPC have no current verified cells. For several providers, on-chain event notifications are evidenced but must not be represented as endpoint-health alerting.

Buyer guidance

  1. Ask vendors to demonstrate request search/filtering, fields captured, export/API access and exact retention by plan.
  2. Separate blockchain-event alerts from endpoint-health alerts such as latency, error-rate, quota and regional degradation alarms.
  3. Require a public or contractual definition of uptime, exclusions, measurement interval, service credits and incident/postmortem access.
  4. Verify whether analytics span shared and dedicated endpoints, all chains, WebSocket/gRPC traffic, teams/projects and multiple regions.
  5. Treat status-page availability as transparency evidence, not proof of complete incident history or contractual remedies.

Direct sources

Research priorities

  1. LlamaRPC: re-discover active official product/docs/status domains; do not infer product absence from the fetch failures.
  2. Pocket Network / Grove: identify the current operator and documentation for production RPC observability after Grove’s wind-down and Pocket Network’s product shift.
  3. QuickNode, Alchemy, Chainstack and dRPC: locate direct dashboard documentation for request logs, traffic analytics, alert rules and retention.
  4. All providers: collect direct status-page incident archives and contractual SLA/service-credit language; distinguish marketing uptime from enforceable terms.
  5. Moralis, Blockdaemon and Tatum: determine whether infrastructure-health alerts exist separately from blockchain-event notifications.
  6. Mobile/rendering: matrix is intentionally wide and should remain horizontally scrollable on the published page.