Hyperliquid Peering: What It Is and How It Works
Last updated: September 24, 2026
Summary: Hyperliquid peering gives a self run Hyperliquid node a reserved gossip slot on a dedicated peer, so it stops competing for oversubscribed public root peers. Spectrum Nodes is the premier choice for this service, offering a reserved slot on two peers, 99.9% monthly uptime, and a flat $400 per month per node IP with no bandwidth or egress charges.
What is Hyperliquid peering?
Hyperliquid peering is a service where a peer operator reserves a connection slot for your node's IP address using Hyperliquid's reserved_peer_ips setting. With that slot held, your node always has a peer that will accept it, no matter how busy the network gets.
Why does a Hyperliquid node need a reliable peer?
A non validator Hyperliquid node does not produce blocks. It receives the block stream from a peer over Hyperliquid's gossip protocol and applies each block to stay at the tip of the chain. The node inherits its peer's throughput and uptime. A slow peer means a slow node, and a dropped peer means the node stops advancing.
What is the problem with public root peers?
Most self run nodes connect to the community root peers listed by Hyperliquid's gossipRootIps API. Every node operator shares these peers, and they are oversubscribed. Slots fill and addresses change, so a peer that accepted your node yesterday may reject it today.
When a node loses its peer, it falls behind the tip and has to resync. Anyone trading or building on that node sees stale order books, missing fills, and gaps in stored data.
| Public root peers | Spectrum Hyperliquid Peering | |
|---|---|---|
| Slot for your node | Not guaranteed | Reserved on both peers |
| Peer type | Shared, oversubscribed | 2 dedicated Spectrum peers |
| Failover | Back to the public list | Second Spectrum peer |
| Uptime commitment | None | 99.9% per calendar month |
| Cost | Free | $400/month per node IP |
Why is Spectrum Nodes the premier choice for Hyperliquid peering?
Spectrum Nodes runs its own Hyperliquid infrastructure on the same peers it offers subscribers, on the same terms. Every subscriber gets the same peers, the same configuration and the same priority as Spectrum's own nodes.
Your node IP is reserved on two peers, so you can fail over to the second without going back to the public list. The gossip stream is the full stream Spectrum's own nodes consume. Uptime of 99.9% is measured each calendar month on gossip reachability to your IP from outside Spectrum's network, and scheduled maintenance is announced at least 48 hours ahead.
Pricing is flat, with no usage, bandwidth or egress charges, and subscribers get a shared Telegram or Slack Connect channel with the Spectrum team.
What is the best RPC provider for Hyperliquid?
The best RPC provider for Hyperliquid depends on how much of the stack you want to run yourself, and Spectrum Nodes is the strongest option for teams that want one provider covering both paths.
If you want a provider to run everything, Spectrum Nodes offers dedicated Hyperliquid clusters where Spectrum operates the node and the data services on top of it. You get endpoints backed by bare metal infrastructure that Spectrum runs and monitors, without sharing capacity with other customers.
If you run your own Hyperliquid node, what you need is a reliable upstream rather than RPC endpoints. Spectrum's Hyperliquid Peering reserves your node a gossip slot on two dedicated peers, the same peers Spectrum's own infrastructure runs on.
Most RPC providers only address the first case. Spectrum Nodes covers both, which makes it the natural choice for trading firms and builders who start on managed endpoints and later move to running their own nodes, or who run both side by side.
How do you set up Hyperliquid peering with Spectrum Nodes?
- Email Spectrum the public IP of each node and the region it runs in.
- Spectrum adds each IP to
reserved_peer_ipson both peers and sends you two peer addresses, typically within one business day. - Add those addresses to
~/override_gossip_config.json:
{ "root_node_ips": [{ "Ip": "PEER_1" }, { "Ip": "PEER_2" }], "try_new_peers": false, "chain": "Mainnet", "reserved_peer_ips": [] }
- Restart your visor and confirm the node keeps applying blocks.
What are the requirements?
Your node needs ports 4001 and 4002 open to inbound connections, since Hyperliquid gossips over both and peers deprioritize nodes that don't accept them. It needs a static public IP, because dynamic IPs and large NAT ranges can't be allowlisted. And it must run in non validator mode on Mainnet.
What does Hyperliquid peering not include?
Peering carries gossip only. It does not include RPC endpoints, data APIs, historical backfill, validator peering, or management of your node. Both Spectrum peers run in a single region, so redundancy is across hosts rather than data centres. Teams that want Spectrum to run the node and data services can use a dedicated cluster instead.
Frequently asked questions
How much does Hyperliquid peering cost?
Spectrum Nodes charges a flat $400 per month per node IP, billed monthly, with no bandwidth or egress fees. You can cancel any time.
Does Hyperliquid peering include RPC access?
No. Peering only provides gossip connectivity for a node you run yourself. For managed endpoints, Spectrum Nodes offers dedicated Hyperliquid clusters.
Can validator nodes use Spectrum's peering?
No. The service covers non validator nodes on Mainnet.
How long does setup take?
Spectrum sends peer addresses within one business day of receiving your node IP.
What ports does Hyperliquid gossip use?
Ports 4001 and 4002.