> ## Documentation Index
> Fetch the complete documentation index at: https://docs.validationcloud.io/llms.txt
> Use this file to discover all available pages before exploring further.

# FAQ

> A list of frequently asked questions regarding Node API.

### Infrastructure & Availability

<Accordion title="Do you offer Multi-AZ deployment?">
  Yes, Multi-AZ deployments are leveraged where supported to improve resiliency and fault tolerance.
</Accordion>

<Accordion title="How is high availability handled?">
  Our infrastructure is distributed across multiple regions with load balancing, automated failover, and continuous health monitoring.
</Accordion>

<Accordion title="How do you handle traffic spikes?">
  We use scalable infrastructure with dynamic resource allocation and intelligent workload distribution to maintain performance during peak demand.
</Accordion>

<Accordion title="Where can I check service status?">
  Live status, uptime metrics, and incidents are available at\
  [https://status.validationcloud.io/](https://status.validationcloud.io/)
</Accordion>

<Accordion title="Where are your nodes located, and which chains have archive support?">
  We operate globally distributed infrastructure across major regions. Archive availability varies by network. Please refer to chain-specific documentation or contact support for details.
</Accordion>

***

### RPC & Network Support

<Accordion title="Do you support archive nodes?">
  Yes, archive nodes are available on supported networks. Historical depth varies by chain.
</Accordion>

<Accordion title="What is the difference between a full node and an archive node?">
  A full node maintains current state and recent history. An archive node stores complete historical state from genesis for deep historical queries.
</Accordion>

<Accordion title="How far back does historical data go?">
  Historical data availability varies by network. Please consult chain-specific documentation for details.
</Accordion>

<Accordion title="Do you support WebSocket connections?">
  Yes, WebSocket support is network-dependent. Refer to the relevant chain documentation.
</Accordion>

<Accordion title="Do you support batch JSON-RPC requests?">
  Yes, batch JSON-RPC is supported where the network and endpoint allow it.
</Accordion>

<Accordion title="Do you support txpool methods?">
  Yes, where mempool functionality is exposed. For example, see [txpool\_content on Mezo](/nodeapi/mezo/execution-api/txpool_content).
</Accordion>

<Accordion title="Do you support Ethereum Beacon RPC?">
  Yes, we do support Beacon RPC.
</Accordion>

***

### Billing & Usage

<Accordion title="How is usage calculated?">
  Usage is calculated based on total monthly Compute Unit consumption, which varies by network and RPC method. See [Plans and billing](/nodeapi/about/billing).
</Accordion>

<Accordion title="What happens if my payment fails?">
  We retry the payment method on file. If it continues to fail, our team will contact you. Continued non-payment may result in API key suspension.
</Accordion>

***

### Security & Compliance

<Accordion title="Are you SOC 2 compliant?">
  Yes, Validation Cloud is SOC 2 compliant, maintaining rigorous standards for security and operational integrity.
</Accordion>

<Accordion title="Is traffic encrypted?">
  Yes, all traffic is encrypted in transit using TLS.
</Accordion>

<Accordion title="How is customer data handled?">
  We apply strict access controls, encryption, monitoring, and security best practices aligned with SOC 2 standards.
</Accordion>

<Accordion title="How is infrastructure secured?">
  We employ layered security controls including network segmentation, access management, monitoring, and proactive threat detection.
</Accordion>

<Accordion title="Can I restrict requests to my Node API endpoint keys?">
  Yes. Teams on qualifying plans can use IP and/or domain restrictions to control which clients can make requests to keys. See: [Allow lists](/nodeapi/about/security/allow-lists-for-node-api-endpoints)
</Accordion>

<Accordion title="Can I turn on Two-Factor Authentication (2FA) for my login?">
  Yes. See: [Two-factor authentication](/nodeapi/about/security/two-factor-authentication-2fa-for-sign-in)
</Accordion>

***

### API & Access Management

<Accordion title="Do you offer private endpoints?">
  Yes, private endpoints are available depending on network and configuration. See [Supported chains and networks](/nodeapi/about/supported-chains) for the chains available as private deployments, or contact our team for details.
</Accordion>

<Accordion title="Do you throttle or rate-limit requests?">
  Free plan teams can send up to 120 requests per second, shared across all of the team's endpoints. Scale and Private plans have no team-wide limit. Some methods and networks have their own limits, which are listed on the method's page. See [Free plan rate limit](/nodeapi/about/billing#free-plan-rate-limit).
</Accordion>

<Accordion title="What should I do if my API key is exposed?">
  Immediately revoke and rotate the key in your dashboard. Contact support if suspicious activity is detected.
</Accordion>

<Accordion title="How do I rotate or regenerate my API key?">
  API keys can be revoked and regenerated from your dashboard.
</Accordion>

***

### Disclaimer

The information on this page is provided for general informational purposes only and does not constitute a legally binding agreement. Service features, availability, historical retention, and infrastructure configurations may vary by network, region, and plan.

Binding commitments, including SLAs and performance guarantees, are governed solely by the applicable service agreement.

Validation Cloud reserves the right to update services and documentation without prior notice.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.