Deposits and withdrawals keep moving on crypto exchange RPC that holds at peak volume
A crypto exchange loses money every minute deposits or withdrawals stall. When the market moves hard, your RPC Endpoints cannot be the bottleneck. Instanodes runs Dedicated Clusters and Dedicated Nodes for hot-wallet RPC, withdrawal broadcasting and deposit indexing on isolated capacity.
- Cluster uptime
- 99.99%
- Contracted, with credits on breach
- Dedicated p99
- <80ms
- Per method, to the regional edge
- Failover
- <500ms
- Automatic cross-region cutover
- Compliance
- SOC 2 Type II
- Report released under NDA
Isolated capacity for hot wallets and deposits
Hot-wallet RPC, withdrawal broadcasting and deposit indexing run on Dedicated Clusters and Dedicated Nodes, run and paged by our infrastructure engineers.
Deposit indexed
Deposit indexing on single-tenant clusters, sized to your peak request rate.
Balance read
Hot-wallet balance reads at <80ms p99 on dedicated capacity.
Withdrawal broadcast
Withdrawals broadcast on single-tenant capacity, so another customer's traffic never touches your withdrawal path.
Volume spikes land on the withdrawal path
Airdrops, listings and liquidation runs hit deposits and withdrawals at the same time. This is what we put there.
| Where it breaks | What we run instead |
|---|---|
| Downtime during high-volume events like airdrops, listings or liquidations. | Auto-scaling nodes absorb traffic spikes. Failover reroutes in under 500ms. |
| Per-request pricing that spikes during market volatility. | Dedicated Cluster capacity is priced in your contract, so a volume spike doesn't change the invoice. |
| Shared RPC Endpoints that put hot-wallet traffic next to other tenants. | Single-tenant clusters with mTLS, IP allowlists and SSO on the access path, and a SOC 2 Type II report under NDA. |
| Rate limits on public endpoints that throttle active traders. | Dedicated capacity with rate limits set to your traffic. |
Downtime during high-volume events like airdrops, listings or liquidations.
- What we run instead
- Auto-scaling nodes absorb traffic spikes. Failover reroutes in under 500ms.
Per-request pricing that spikes during market volatility.
- What we run instead
- Dedicated Cluster capacity is priced in your contract, so a volume spike doesn't change the invoice.
Shared RPC Endpoints that put hot-wallet traffic next to other tenants.
- What we run instead
- Single-tenant clusters with mTLS, IP allowlists and SSO on the access path, and a SOC 2 Type II report under NDA.
Rate limits on public endpoints that throttle active traders.
- What we run instead
- Dedicated capacity with rate limits set to your traffic.
Around the withdrawal path
Multi-region RPC Endpoints
Requests route to the nearest healthy node, with automatic cross-region failover.
Rollups for settlement
Move high-frequency settlement to your own L2 rollup for lower gas and faster confirmation.
Security and compliance
Encrypted API key management, DDoS mitigation and SOC 2 Type II certified infrastructure for institutional onboarding.
Scope a cluster with our infrastructure team
Bring your chain list and peak request rates. Regions, SLA credits and terms for a Dedicated Cluster are set in your contract.