Hyperliquid node peering in Tokyo
An allowlisted upstream gossip peer for your non-validating node, mempool included. Pin your node to a fixed address in Tokyo instead of rotating public seeds.
$200 per node address per month
- Card checkout through Stripe
- No 0xArchive account needed
- Cancel by email
An allowlisted upstream for the node you already run
A node pinned to public seeds periodically loses its upstream and falls back to whichever address accepts it next. That shows up as a rising tail on block arrival rather than a clean outage.
Allowlisted nodes only
Public seed nodes are shared and refuse connections once they reach capacity. The peer accepts connections only from allowlisted customer addresses.
A fixed address
Public seed lists change without notice. The peer uses a fixed address, issued when your node is allowlisted.
In Tokyo
The peer runs in Tokyo, where Hyperliquid recommends running a node for the lowest latency.
One flat rate
One monthly price per node address, with no usage metering and no egress charges.
Test the round trip from your own server first
Enter your node's address in the latency test. Our Tokyo site runs on the same machine as the peer, so the round trip it measures to your server is the round trip your node would have to the peer. No account or API key needed.
Mempool included at no extra cost
With split_client_blocks set to true, your node receives most orders before the block that commits them and writes them under ~/hl/data/mempool_txs/. Omit split_client_blocks to receive committed blocks only.
The mempool adds roughly 0.4 to 0.5 TB of disk writes per day, so prune those files on a schedule.
{
"root_node_ips": [{ "Ip": "<peer address>" }],
"reserved_peer_ips": ["<peer address>"],
"try_new_peers": false,
"split_client_blocks": true,
"chain": "Mainnet"
}How it works from checkout to the chain tip
Subscribe
Choose how many node addresses to connect, then enter each node's static public IPv4 egress address at checkout.
Get allowlisted
Each address is reviewed and allowlisted on the peer. The peer address is emailed to you once it is live.
Pin your node
Add the peer address to override_gossip_config.json, set try_new_peers to false, and restart the node.
- Node
- Hyperliquid non-validating node
- Address
- Static public IPv4 egress address
- Ports
- Inbound TCP 4000 to 4010 reachable
- Machine
- Ubuntu 24.04, 16+ cores, 128 GB RAM, NVMe
Questions before you subscribe
Anything else: support@0xarchive.io
Do I need a 0xArchive account or data plan?
No 0xArchive account or data plan is required. Peering is billed separately through Stripe Checkout and can run alongside any data plan.
Does 0xArchive claim rights over the data my node receives?
No. Data your node receives through the peer is not 0xArchive Data. 0xArchive claims no rights over it and places no limits on how you use it, and the Data License does not apply to it.
Does every customer get the same service?
Yes. Every customer gets the same peer at the same price on the same terms. There are no preferential slots or priority tiers.
How many nodes can I connect?
Up to five node addresses per order, each billed at $200 per month. For more, email support@0xarchive.io.
Can I use an IPv6 address?
No. The peer allowlists static public IPv4 addresses only.
What if an address cannot be allowlisted?
We ask you for a replacement address. If you have none, the subscription is reduced to the addresses that can be allowlisted and the difference is refunded.
How do I change an address or cancel?
Email support@0xarchive.io. After you cancel, peering stays on until the end of the period you paid for.
Do you run or monitor my node?
No. You operate your node. 0xArchive operates the peer it connects to.