Hyperliquid RPC infrastructure

Dedicated endpoints for HyperEVM and HyperCore with JSON-RPC, WebSocket, and gRPC — built for perps desks, validators, and latency-sensitive dApps.

Core

Features & SLOs

  • Sub-50ms latency

    Multi-region edges and co-located infra for time-sensitive execution.

  • DDoS & isolation

    Dedicated nodes with API key isolation and production-grade edge filtering.

  • Archive & retention

    Historical queries and indexed logs for debugging and compliance workflows.

  • Burst-ready throughput

    Unlimited RPS on dedicated plans with headroom for liquidation and arb bursts.

MetricValue
Latency<50ms
Uptime SLA99.99%
RPS (dedicated)Unlimited
p99 latency (24h)<50ms target
00:0012:0024:00

Performance

Optimized for trading & validators

Edges in multiple regions with private peering to local PoPs, auto-scaling clusters, and structured log indexing. Full compatibility with Chain ID 999 and clear tx submission paths for HyperEVM and HyperCore.

Global edge footprint

HighTower runs edge nodes in multiple regions. Traffic hits the nearest PoP over private peering — same APIs everywhere, lower RTT for bots, validators, and desks wherever you connect from.

Frankfurt · eu-central-1 · median 18–24 ms

EU

HighTower edge

Peering · TLS · JSON-RPC / WS / gRPC

Multi-region

Singapore · ap-southeast-1 · median 22–28 ms

SG

Edge latency

28ms

Throughput headroom

Requests / sec

Baseline load stays on a steady channel; reserved headroom absorbs liquidation and arb spikes without p99 degradation.

0 RPS25k50k+

Sustained baseline

Typical JSON-RPC & subscription volume

12.4k

Peak capacity

Liquidations, arb bursts, book snapshots

48.2k

Auto-scaling and burst buffers keep p99 stable when traffic spikes.

Security

Compliance & isolation

Dedicated access
Edge protection
KYB invoicing
  • Dedicated nodes — no noisy-neighbor risk on private tiers
  • KYB-ready invoices in KGS / USD
  • Logical isolation aligned with SOC2-style practices for enterprise IT
  • No hidden egress or surprise metering on published tiers

Integration

Connect in minutes

SDK-friendly HTTPS endpoints, dashboard for usage & logs, 14-day trial on eligible plans.

curl
curl -s https://rpc.hyperliquid.htw.tech/evm \
  -H "Content-Type: application/json" \
  -H "Authorization: Bearer YOUR_API_KEY" \
  -d '{"jsonrpc":"2.0","method":"eth_chainId","params":[],"id":1}'
viem / TypeScript
import { createPublicClient, http } from "viem";

const client = createPublicClient({
  chain: { id: 999, name: "HyperEVM", ... },
  transport: http("https://rpc.hyperliquid.htw.tech/evm", {
    fetchOptions: { headers: { Authorization: "Bearer YOUR_API_KEY" } },
  }),
});
Python / httpx
import httpx

response = httpx.post(
    "https://rpc.hyperliquid.htw.tech/evm",
    headers={
        "Authorization": "Bearer YOUR_API_KEY",
        "Content-Type": "application/json",
    },
    json={
        "jsonrpc": "2.0",
        "method": "eth_blockNumber",
        "params": [],
        "id": 1,
    },
    timeout=10.0,
)
print(response.json())
hl-rpc-prod · node console
syncing

RPS (1m)

12.4k

p99

31ms

WS conns

214

Err rate

1.80%

Mempool

842

Block

#48,291,032

gRPC qps

1840

CPU / RAM

34% / 62%

Requests per second · 1m window

/var/log/hl-rpc/jsonrpc.logtail -f
[18:10:51] INFO jsonrpc eth_blockNumber → 0x9be7ff
[18:10:51] WS newHeads subscriber +4 (total 219)
[18:10:51] WARN rate_bucket key_…w7rw 8633/10000
chainId 999hypercore+evmregion ap-southeast-1

FAQ

What latency can we expect by region?+
We target sub-50ms p99 to the nearest HighTower edge from major networks in each footprint; exact numbers depend on your hosting and peering. Live checks are available from the dashboard.
Do you support HyperCore and HyperEVM?+
Yes — dedicated paths for both stacks: JSON-RPC / WebSocket for EVM (Chain ID 999) and native APIs where applicable, plus gRPC for streaming workloads.
Is there a trial?+
We offer 14-day trial access on eligible plans after a quick KYB check — contact us on Discord with your use case.
How does scaling work under burst load?+
Dedicated clusters include auto-scaling and burst buffers; shared tiers have clear RPS ceilings with upgrade paths.
Regional compliance for Kyrgyzstan-based teams?+
Invoices and contracts can be issued for KG entities; isolation tiers are available for firms that require stricter data boundaries.