GetBlock RPC competitor monitor — 2026-10-30
Criterion of the day: Compliance geofencing, sanctions and data residency: regional restrictions, data location, compliance controls and jurisdictional posture (compliance-geofencing-data-residency).
Executive summary
Today’s consolidation found little public evidence for the core criterion. Across 15 tracked providers, the monitored pages did not directly establish a provider-level sanctions/geofencing policy plus a contractual data-residency commitment. The usable findings are adjacent enterprise controls and material procurement-status changes:
- QuickNode: direct enterprise wording supports QuickNode compliance reports on request (SOC 1 Type 2, SOC 2 Type 2, ISO 27001), RBAC, contractual 99.99% uptime, service credits, a named solutions architect and 24/7 on-call engineering. It does not establish geofencing, sanctions controls or data residency.
- NOWNodes and Ankr: NOWNodes advertises “Select regions” in a custom package plus 24/7 priority support/dedicated account management; Ankr advertises geo-distribution across 24 metros plus dedicated Slack/Telegram engineering support. Neither source establishes a legal residency commitment.
- Procurement caveats: Blast API is deprecated and redirects customers to Alchemy; Grove is winding down while Pocket Network continues separately. These are operating-status findings, not compliance-capability claims.
The cumulative topic brief was rebuilt rather than merely appending this report. The prior Blockdaemon sanctions/jurisdiction positives were removed because generic “built for compliance” language did not directly support those dimensions.
Evidence model
- Positive classification: only when a direct vendor source explicitly supports the narrowly worded claim.
- Not verified in monitored public evidence: insufficient evidence; not a claim that the capability is absent.
- Independent reference: CompareNodes is used to nominate certificate verification targets, not as a substitute for first-party certificate/report scope.
- Location semantics: geo-distribution, selectable deployment region, customer-controlled storage destination and binding data residency are not interchangeable.
Decision-relevant findings by provider
QuickNode
- Confirmed: enterprise states contractual 99.99% uptime, service credits, named solutions architect, 24/7 on-call engineering and RBAC. Pricing says SOC 1 Type 2, SOC 2 Type 2 and ISO 27001 reports are available on request.
- Not confirmed: certificate legal-entity/service scope, geofencing, restricted-country policy, sanctions screening, processing/storage residency and cross-border transfer controls.
- Change assessment: pricing-page hash changed, but the market signal recorded here is the visible enterprise/compliance wording—not the hash itself. No unsupported claim is made about when that wording first appeared.
- Matrix update: standards/security and contractual/support cells moved to publicly evidenced; four core geography/legal cells remain unverified.
Alchemy
- The monitored home, pricing, enterprise and blog pages did not expose criterion-specific controls in the supplied extracts.
- CompareNodes lists Alchemy SOC attestations, but direct Alchemy trust-center/report scope was not captured; the standards cell remains unverified.
- Two monitored URLs returned 404: the old chains reference and customer-stories path. These are collection/navigation gaps, not product negatives.
Infura
- Pricing advertises enterprise enhanced support/SLA, but the supplied text does not expose measurement, service credits or escalation details.
- No direct sanctions, geofencing, residency or jurisdiction control was captured.
- Blog routing to MetaMask is a navigation change/context issue, not a compliance signal.
Chainstack
- Managed dedicated nodes advertise flexible deployment, but no customer-selectable processing region or contractual residency term was established.
- CompareNodes lists Chainstack SOC/ISO attestations; first-party owner/scope corroboration remains open.
- No page-level change was detected; no market change is claimed.
Ankr
- Enterprise states geo-distribution across 24 metros and dedicated Slack/Telegram engineering support.
- Geo-distribution was retained as context only, not converted into residency evidence. Enterprise escalation was added as a positive support-control cell.
- Docs exposes a “Trust & compliance” navigation item, but the landing extract does not establish a specific control. CompareNodes’ SOC 2 Type 2 listing remains a verification lead, not a first-party-confirmed matrix claim.
Moralis
- Moralis advertises delivery into customer destinations such as Postgres, ClickHouse, MySQL, Kafka, Snowflake, BigQuery and S3. That may help customer-controlled storage architecture, but does not establish where Moralis processes or temporarily stores data.
- The enterprise page title mentions SLAs; contractual terms and remedies were not visible, so no positive SLA cell was assigned.
NOWNodes
- Pricing directly advertises “Select regions” for custom packages, plus 24/7 priority support and a dedicated account manager; its plan table publishes support-response targets.
- “Select regions” is classified as limited location-choice evidence, explicitly not as a legal residency commitment.
- The legacy Postman documentation URL returned 404, an extraction/navigation gap rather than evidence about the service.
dRPC
- Home copy changed and now advertises eight geo-distributed clusters; pricing/chainlist also changed. The supplied captures do not prove whether all textual changes are new market commitments versus site refresh.
- Geo-distributed infrastructure and priority support do not establish selectable region, sanctions controls or residency terms; no positive criterion cell was assigned.
Blast API
- Blast API explicitly says products are deprecated and users should migrate to Alchemy.
- The matrix records service deprecation as a procurement-status fact. Alchemy capabilities are not inherited into the Blast row.
Blockdaemon
- Home, blog and docs changed, while old blockchain-api and pricing URLs returned 404. The current home advertises institutional compliance positioning, “inside your perimeter” wallet deployment and dedicated nodes.
- These statements do not directly evidence sanctions posture, geofencing or RPC data residency.
- Correction to accumulated brief: prior sanctions and jurisdiction positives were removed as unsupported by narrowly matched direct evidence. This is a classification correction, not evidence that Blockdaemon lacks the capabilities.
- CompareNodes lists Blockdaemon SOC/ISO attestations; direct certificate owner/scope remains a priority.
Tatum
- Site navigation markets “Compliance” as a use case for taxes/accounting. That is not evidence of Tatum’s own sanctions, geofencing or residency controls.
- The supported-blockchains URL returned 404; docs remained available. Blog change was not criterion-relevant.
Pocket Network / Grove
- Grove states it is winding down; Pocket Network continues separately.
- Pocket’s Agentic Portal lists a counterparty-screening service based on public watchlists including OFAC SDN. This is a third-party/marketplace service, not evidence of Pocket/Grove’s own customer sanctions posture.
- Grove docs failed DNS resolution. Commercial contracting, support ownership and gateway availability require re-qualification.
LlamaRPC
- Home and chains returned HTTP 526; docs and status failed DNS resolution.
- All criterion cells remain “Not verified in monitored public evidence.” The failures are extraction/access limitations, not inferred product absence.
Allnodes
- All five monitored surfaces returned HTTP 403 protection pages.
- No positive or negative capability classification was made; all cells remain unverified.
Lava Network
- Home supports an open network of independent providers and real-time routing/failover. It does not expose node geography, customer region selection or residency commitments in the captured evidence.
- Audit links appear in navigation, but organizational compliance scope was not validated. Developer/network paths returning 404 are navigation gaps, not market changes.
Independent reference check
CompareNodes — AICPA SOC & ISO Compliance in Web3 Data API Infrastructure was available and checked on 2026-10-30. It reports 36 providers with announced SOC or ISO standards and includes monitored vendors such as Alchemy, Ankr, Blockdaemon and Chainstack, as well as GetBlock.
Use limitations:
- CompareNodes is an editorial/reference directory, not an RPC-provider row in this comparison.
- Its listing does not replace the underlying report/certificate, exact legal entity, service scope, validity period or bridge letter.
- The relevant topic rows therefore remain conservative until first-party trust-center or report evidence is obtained.
Real changes versus collection noise
Decision-relevant
- Blast API remains explicitly deprecated and migration is directed to Alchemy.
- Grove explicitly states it is winding down while Pocket Network continues.
- QuickNode’s current public enterprise surface gives unusually specific contractual SLA/service-credit and escalation wording.
- NOWNodes publicly exposes selectable regions in custom packaging, though not a legal residency guarantee.
Not treated as market changes
- Page hash changes alone for QuickNode, dRPC, Blockdaemon and Tatum.
- Navigation/menu refreshes, new blog listings or broad institutional/compliance marketing.
- HTTP 403/404/526 and DNS errors; these are access or stale-URL limitations.
- Pocket Agentic Portal’s third-party OFAC screening tool as evidence of the network operator’s own sanctions program.
Topic brief modifications
Updated /monitoring/topics/compliance-geofencing-data-residency.md with:
- a six-dimension schema and all 15 provider rows;
- QuickNode standards/RBAC and contractual SLA/service-credit/escalation evidence;
- NOWNodes limited region-selection and support evidence;
- Ankr enterprise escalation evidence with 24-metro context kept outside residency classification;
- Blast deprecation and Grove/Pocket operating-status caveats;
- explicit access limitations for LlamaRPC and Allnodes;
- removal and explanation of unsupported prior Blockdaemon sanctions/jurisdiction positives;
- CompareNodes reference semantics, direct-source dates and provider-specific research priorities.
GetBlock implications
Sales
- Lead discovery with a precise RFP question: “Can you contractually pin processing, logs, backups and failover to named regions?” Competitor “global,” “24 metros,” or “select regions” language does not answer it.
- If GetBlock can document sanctions/geofencing policy, residency scope and cross-border transfer controls, that is a clearer enterprise proof point than generic compliance badges.
Product marketing
- Publish a precise deployment/data-flow statement separating endpoint routing region, node location, logs/telemetry, backups and legal residency. Competitor public evidence is weakest on this distinction.
- Pair compliance reports with exact legal-entity and product scope; QuickNode’s reports-on-request language is a useful procurement benchmark, but buyers still need scope.
Content
- Create a buyer guide: “Geo-distributed RPC vs selectable region vs contractual data residency.” Use conservative examples and a checklist rather than unsupported provider rankings.
- Add a sanctions/geofencing and subprocessor questionnaire template to enterprise procurement content.
Publication and paper status
- The encyclopedia pre-run publisher reported success with 144 published URLs, but publication must be rerun after this consolidation so this report and matrix reach HTML.
- Agentic routing paper update reported
ok=true,paper_updated=true, with 57 evidence items. The generated update references QuickNode latency/uptime/SLA evidence and flags cost/SLA constraints, enterprise metrics, method-specific routing and incident simulation for review. The living paper URL ishttps://rpc.run.beinginfuture.com/papers/agentic-routing-rpc.html.
Sources and limitations
Direct vendor links are attached to each positive claim in the topic matrix. Volatile prices, SLAs, support promises, standards and operating status must be rechecked before external sales use. The source extracts did not include full legal/privacy/trust-center documents, so absence of evidence was not converted into a “No.”