Compliance geofencing, sanctions and data residency: regional restrictions, data location, compliance controls and jurisdictional posture
Last consolidated: 2026-10-30 Comparison date: 2026-10-30 Coverage: 4/15 providers have at least one directly evidenced dimension; 0/15 have public evidence across all six dimensions. Core criterion coverage remains sparse: no monitored provider publicly evidenced both sanctions/geofencing controls and a contractual data-residency commitment in the pages checked.
> Evidence semantics: “Publicly evidenced” means the linked first-party source explicitly supports the narrowly worded cell. “Not verified in monitored public evidence” means the checked public surface was insufficient; it does not mean the capability is absent. Regional infrastructure, a selectable deployment region, and contractual data residency are different claims.
Comparison dimensions
- Geofencing / regional restrictions: documented location-based access or service restrictions.
- Sanctions posture: public sanctions screening, restricted-party or embargo policy applicable to the provider/customer relationship.
- Data location / residency: buyer-selectable or contractually committed processing/storage location.
- Jurisdiction / privacy posture: explicit governing jurisdiction, cross-border transfer or privacy-location controls relevant to procurement.
- Standards / security controls: first-party compliance standards or relevant deployment/access controls, with certificate ownership attributed precisely.
- Contractual / support controls: contractual SLA/service credits or escalation terms that help enforce enterprise commitments; these are adjacent controls, not substitutes for geofencing or residency.
| Provider | Geofencing / regional restrictions | Sanctions posture | Data location / residency | Jurisdiction / privacy posture | Standards / security controls | Contractual / support controls | Direct sources | Evidence status / freshness |
|---|---|---|---|---|---|---|---|---|
| QuickNode | Not verified in monitored public evidence | Not verified in monitored public evidence | Not verified in monitored public evidence | Not verified in monitored public evidence | Publicly evidenced: QuickNode says SOC 1 Type 2, SOC 2 Type 2 and ISO 27001 reports are available on request. This is a vendor claim about QuickNode reports; certificate scope was not inspected. Enterprise page also states RBAC. | Publicly evidenced: contractual 99.99% uptime SLA, service credits, named solutions architect and 24/7 on-call engineering. These do not establish residency. | Enterprise<br>Pricing | 2/6 dimensions; checked 2026-10-30 |
| Alchemy | Not verified in monitored public evidence | Not verified in monitored public evidence | Not verified in monitored public evidence | Not verified in monitored public evidence | Not verified in monitored first-party evidence. CompareNodes lists Alchemy SOC attestations, but this pass did not corroborate scope on a direct Alchemy trust source. | Not verified in monitored public evidence | Home<br>Enterprise | 0/6; checked 2026-10-30; first-party evidence gap |
| Infura | Not verified in monitored public evidence | Not verified in monitored public evidence | Not verified in monitored public evidence | Not verified in monitored public evidence | Not verified in monitored public evidence | Enterprise pricing says enhanced support/SLA, but terms, service credits and escalation were not visible in the monitored extract; not classified as evidenced. | Pricing<br>Docs | 0/6; checked 2026-10-30 |
| Chainstack | Not verified in monitored public evidence | Not verified in monitored public evidence | “Flexible deployment” is advertised for managed dedicated nodes, but selectable region and contractual residency were not established; not classified as residency evidence. | Not verified in monitored public evidence | Not verified in monitored first-party evidence. CompareNodes lists Chainstack SOC/ISO attestations, but direct certificate owner/scope was not corroborated in this pass. | Not verified in monitored public evidence | Home<br>Enterprise<br>Docs | 0/6; checked 2026-10-30; first-party evidence gap |
| Ankr | Not verified in monitored public evidence | Not verified in monitored public evidence | Enterprise page states geo-distribution across 24 metros, but does not promise customer-selected storage/processing residency; not classified as residency evidence. | Not verified in monitored public evidence | Docs expose a “Trust & compliance” section, but the monitored landing-page extract did not establish a specific control. CompareNodes lists Ankr SOC 2 Type 2; direct owner/scope corroboration remains required. | Publicly evidenced: enterprise page offers dedicated Slack/Telegram engineering support and bespoke infrastructure by request; no contractual SLA/service-credit wording was captured. | Enterprise<br>Docs | 1/6; checked 2026-10-30 |
| Moralis | Not verified in monitored public evidence | Not verified in monitored public evidence | Data can be delivered to customer-controlled Postgres, ClickHouse, MySQL, Kafka, Snowflake, BigQuery or S3, but the monitored pages do not establish Moralis processing residency; not classified as residency evidence. | Not verified in monitored public evidence | Not verified in monitored public evidence | Enterprise page title references SLAs, but the monitored extract did not expose contractual terms or service credits; not classified as evidenced. | Home<br>Enterprise<br>Docs | 0/6; checked 2026-10-30 |
| NOWNodes | Not verified in monitored public evidence | Not verified in monitored public evidence | Publicly evidenced, limited: custom package advertises “Select regions.” This is deployment-region choice, not a verified legal data-residency commitment. | Not verified in monitored public evidence | Not verified in monitored public evidence | Publicly evidenced: custom package advertises 24/7 priority support and a dedicated account manager; published plan table shows support response targets. Contractual SLA/service credits were not found. | Pricing | 2/6; checked 2026-10-30 |
| dRPC | Not verified in monitored public evidence | Not verified in monitored public evidence | Eight geo-distributed clusters are advertised, but customer region selection and contractual residency were not established; not classified as residency evidence. | Not verified in monitored public evidence | Not verified in monitored public evidence | Priority support is advertised for paid access, but contractual SLA/service credits were not established in monitored evidence. | Home<br>Pricing<br>Docs | 0/6; checked 2026-10-30 |
| Blast API | Not applicable to active procurement: service is deprecated | Not applicable to active procurement: service is deprecated | Not applicable to active procurement: service is deprecated | Not applicable to active procurement: service is deprecated | Publicly evidenced status: Blast says its products are no longer available and directs users to Alchemy. No capability should be inherited from Alchemy without separate evidence. | Not applicable to active procurement | Deprecation notice | Service-status evidence only; checked 2026-10-30 |
| Blockdaemon | Not verified in monitored public evidence | Not verified in monitored public evidence | “Wallet stack inside your perimeter” and dedicated nodes are advertised, but neither proves RPC data residency; not classified as residency evidence. | Not verified in monitored public evidence | Not verified in monitored first-party evidence for this criterion. CompareNodes lists Blockdaemon SOC/ISO attestations, but direct certificate owner/scope was not corroborated in the monitored pages. | Not verified in monitored public evidence | Home<br>Docs | 0/6; checked 2026-10-30; prior sanctions/jurisdiction classifications removed as unsupported |
| Tatum | Not verified in monitored public evidence | Not verified in monitored public evidence | Not verified in monitored public evidence | Not verified in monitored public evidence | The site describes compliance-use-case tooling for taxes/accounting, which is not evidence of Tatum’s own sanctions or residency controls; not classified as evidenced. | Not verified in monitored public evidence | Home<br>Docs | 0/6; checked 2026-10-30 |
| Pocket Network / Grove | Not verified in monitored public evidence | Pocket Network lists a third-party Agentic Portal counterparty-screening service using OFAC SDN data; this is marketplace service evidence, not Grove/Pocket’s own sanctions posture, so the provider cell remains unverified. | Not verified in monitored public evidence | Not verified in monitored public evidence | Not verified in monitored public evidence | Grove states it is winding down; Pocket Network continues separately. Procurement and contractual support ownership require re-qualification. | Grove farewell<br>Pocket Network | 0/6 plus material operating-status caveat; checked 2026-10-30 |
| LlamaRPC | Not verified in monitored public evidence | Not verified in monitored public evidence | Not verified in monitored public evidence | Not verified in monitored public evidence | Not verified in monitored public evidence | Not verified in monitored public evidence | Home | 0/6; inaccessible in this pass (HTTP 526/DNS gaps), checked 2026-10-30 |
| Allnodes | Not verified in monitored public evidence | Not verified in monitored public evidence | Not verified in monitored public evidence | Not verified in monitored public evidence | Not verified in monitored public evidence | Not verified in monitored public evidence | Home | 0/6; monitored pages blocked by HTTP 403, checked 2026-10-30 |
| Lava Network | Not verified in monitored public evidence | Not verified in monitored public evidence | An open network of independent providers and real-time routing are evidenced, but node geography, customer selection and residency commitments are not; not classified as residency evidence. | Not verified in monitored public evidence | Public audit links appear in site navigation, but this pass did not validate their scope as organizational compliance controls; not classified as evidenced. | Not verified in monitored public evidence | Home<br>Docs | 0/6; checked 2026-10-30 |
Cross-provider readout
- Breadth: 4/15 providers have at least one directly evidenced dimension under the conservative schema: QuickNode, Ankr, NOWNodes and Blast API (service status only).
- Completeness: 0/15 have public evidence across all six dimensions. No provider in the monitored surface publicly combined sanctions/geofencing evidence with a contractual data-residency commitment.
- Most evidenced adjacent controls: enterprise support and SLA language. QuickNode has the strongest monitored contractual wording: 99.99% uptime, service credits and 24/7 escalation.
- Least evidenced controls: sanctions posture, legal geofencing, cross-border transfer controls and binding data-residency terms.
- Important distinction: “geo-distributed,” “select regions,” “inside your perimeter,” and “customer-controlled destination” are materially different. Only NOWNodes’ “Select regions” is recorded as limited location-choice evidence; none is treated as a legal residency guarantee.
- Independent reference: CompareNodes reports SOC/ISO attestations for several monitored vendors, including Alchemy, Ankr, Blockdaemon and Chainstack, and GetBlock. It is an editorial directory—not a certificate owner or RPC-provider row—and is used only to prioritize direct trust-center verification. QuickNode’s standards claim was independently found on its own enterprise/pricing pages.
- Buyer guidance: require the legal entity, certificate/report scope, subprocessors and processing locations, restricted-country policy, cross-border transfer mechanism, region failover behavior, support escalation, SLA measurement and service-credit schedule in the RFP. Do not infer these from global PoP counts.
Changes consolidated on 2026-10-30
- Added directly sourced QuickNode compliance-report, RBAC, contractual SLA, service-credit and escalation wording while leaving geofencing, sanctions and residency unverified.
- Added limited NOWNodes “Select regions” evidence and published support/escalation terms; explicitly did not convert this into a contractual residency claim.
- Added Ankr’s 24-metro context and enterprise escalation evidence, while keeping data residency unverified.
- Removed the previous Blockdaemon sanctions and jurisdiction positive cells: the earlier monitored home/blog wording (“built for compliance”) did not directly evidence either dimension. This is an evidence-quality correction, not a claim that Blockdaemon lacks those controls.
- Recorded Blast API deprecation, Grove wind-down/Pocket continuation, and access limitations for LlamaRPC and Allnodes as procurement caveats rather than product-capability claims.
Direct sources
All volatile claims should be rechecked before sales use.
- QuickNode: Enterprise, Pricing — checked 2026-10-30.
- Alchemy: Home, Enterprise — checked 2026-10-30.
- Infura: Pricing, Docs — checked 2026-10-30.
- Chainstack: Home, Enterprise, Docs — checked 2026-10-30.
- Ankr: Enterprise, Docs — checked 2026-10-30.
- Moralis: Home, Enterprise, Docs — checked 2026-10-30.
- NOWNodes: Pricing — checked 2026-10-30.
- dRPC: Home, Pricing, Docs — checked 2026-10-30.
- Blast API: Deprecation notice — checked 2026-10-30.
- Blockdaemon: Home, Docs — checked 2026-10-30.
- Tatum: Home, Docs — checked 2026-10-30.
- Pocket Network / Grove: Grove farewell, Pocket Network — checked 2026-10-30.
- LlamaRPC: Home — attempted 2026-10-30; HTTP 526. Docs/status DNS resolution failed.
- Allnodes: Home — attempted 2026-10-30; monitored pages returned HTTP 403.
- Lava Network: Home, Docs — checked 2026-10-30.
- Independent editorial reference: CompareNodes — AICPA SOC & ISO Compliance in Web3 Data API Infrastructure — checked 2026-10-30. Use as a discovery/reference source; verify certificate owner, scope and current validity with first-party reports.
Research priorities
- Obtain direct trust-center/legal evidence for Alchemy, Ankr, Blockdaemon and Chainstack to corroborate CompareNodes entries and attribute each certificate to the exact legal entity and service scope.
- Ask all active providers for restricted-country/geofencing policy, sanctions-screening obligations and customer eligibility language; public marketing pages do not answer this.
- Request a data-processing map: primary/backup region, logs and telemetry location, subprocessors, cross-border transfer mechanism, failover behavior and deletion/retention commitments.
- Verify whether NOWNodes “Select regions,” Ankr’s 24 metros, Chainstack flexible deployment and Blockdaemon perimeter deployment can become contractually pinned regions with no cross-region failover.
- Capture direct contractual SLA/service-credit and support-escalation terms for every provider; do not equate generic “SLA” or “priority support” labels with enforceable remedies.
- Re-check LlamaRPC through an alternate network/browser and Allnodes through accessible first-party trust/help pages; preserve their cells as unverified until direct evidence is available.
- Re-qualify Pocket Network’s commercial gateway/support entity after Grove’s wind-down; do not attribute marketplace compliance tools to the network operator.
Research log
Dated reports are the audit trail and do not replace this matrix. See the closed Research log section on the published topic page for daily links.