> For the complete documentation index, see [llms.txt](https://docs.coinmarketman.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.coinmarketman.com/hyperliquid-node-peering.md).

# Hyperliquid Node Peering

Planned SLA-backed peer connectivity for teams operating their own Hyperliquid nodes.

## Hyperliquid Node Peering

Open, SLA-backed peer connectivity for teams operating their own Hyperliquid non-validating nodes.

To register interest, contact <support@coinmarketman.com> with the subject “Hyperliquid Node Peering.” or reach out to us in our [telegram group](https://t.me/HyperTrackerio)

### Service at a glance

<table><thead><tr><th width="204.32421875">Item</th><th>Details</th></tr></thead><tbody><tr><td>Designed for</td><td>Teams operating their own Hyperliquid Mainnet non-validating node</td></tr><tr><td>HyperTracker provides</td><td>Allowlisted peer connectivity, monitoring and onboarding support</td></tr><tr><td>Customer provides</td><td>A correctly configured node with a static public IP</td></tr><tr><td>Availability commitment</td><td>99.9% monthly peering uptime</td></tr><tr><td>Price</td><td>$500 per month per allowlisted connecting-node IP</td></tr><tr><td>Access policy</td><td>Open, standardized and non-discriminatory</td></tr><tr><td>Activation</td><td>Manual onboarding following service launch</td></tr></tbody></table>

### What the service provides

HyperTracker Node Peering will give node operators a stable peer path for native block and gossip data available through the Hyperliquid node protocol.

The service includes:

* Allowlisting for one static connecting-node IP per subscription.
* HyperTracker peer details and configuration guidance.
* Production monitoring, alerting, onboarding support, and incident support.
* Capacity that automatically expands with connected-peer count and utilization.
* The same service configuration and priority for every customer.

Customers continue to operate and maintain their own Hyperliquid node. HyperTracker does not take custody of customer systems, private keys, or funds.

### Service level and equal access

HyperTracker commits to 99.9% peering availability per calendar month.

Availability will use gossip reachability on applicable Hyperliquid peer ports. Scheduled maintenance is communicated 48 hours in advance. It is excluded from measurement.

Access is provided on uniform terms:

* No customer receives preferential routing, bandwidth, or connection priority.
* Market makers, trading firms, builders, and node operators receive the same service.
* Capacity expands as connected-peer count grows.
* Pricing is public and applied consistently.
* No faster or higher-priority tier is available to selected customers.
* Access remains subject to technical onboarding, infrastructure protection, applicable law, and published service terms.

Peering improves connection stability. It does not guarantee latency, data completeness, or trading outcomes. Customers should maintain monitoring and redundancy. No single peer should be treated as a sole or authoritative source.

### Pricing

#### Standard peering — $500/month

The price is **$500 per month** for each allowlisted connecting-node IP.

The subscription covers:

* The peering connection.
* Associated network traffic, compute, and egress.
* Peering-health monitoring, technical onboarding, and operational support.

There are no priority peering tiers. No customer may purchase preferential treatment.

HyperTracker API subscriptions are separate data products. They are not required for node peering. They are not included in the peering price.

### Customer requirements

Before onboarding, the customer must:

1. Operate a supported [Hyperliquid Mainnet non-validating node](https://github.com/hyperliquid-dex/node).
2. Have a static public IP for the connecting node.
3. Make required Hyperliquid peer ports publicly reachable. These are currently ports `4001` and `4002`.
4. Maintain its own node, server, storage, security, and monitoring.
5. Comply with applicable laws, sanctions, and service policies.

The official [Hyperliquid node documentation](https://github.com/hyperliquid-dex/node) remains authoritative if technical requirements change.

### Onboarding

1. Email <support@coinmarketman.com> with the organization name, technical contact, connecting-node public IP, and hosting region.
2. HyperTracker reviews the request and confirms technical readiness.
3. HyperTracker allowlists the connecting-node IP and privately supplies peer connection details.
4. Both teams verify block progression and connection stability.
5. Monthly service begins after successful activation.

Access is manually provisioned. Peer IPs and other sensitive infrastructure details are supplied privately to approved customers only.

### What peering does not include

Node peering is not:

* A managed Hyperliquid node.
* A REST, WebSocket, or webhook data subscription.
* Historical or proprietary HyperTracker cohort data.
* Transaction signing or order execution.
* A substitute for operating and monitoring the customer’s infrastructure.

Teams needing managed, normalized, proprietary, or historical Hyperliquid data should use the separate [HyperTracker API](https://docs.coinmarketman.com/hypertracker-api-documentation).

### About HyperTracker

HyperTracker has operated production Hyperliquid data infrastructure since 2025. Its infrastructure powers freely accessible public analytics and commercial data services for retail users, researchers, quantitative analysts, and third-party builders.

Node peering is a separate infrastructure service for teams operating their own Hyperliquid non-validating nodes. It is designed for teams needing a more dependable peer connection.

### Related resources

* [Public HyperTracker platform](https://app.coinmarketman.com/hypertracker/)
* [HyperTracker API documentation](https://docs.coinmarketman.com/hypertracker-api-documentation)
* [Hyperliquid node repository](https://github.com/hyperliquid-dex/node)
* [Hyper Foundation peering information](https://hyperliquid.gitbook.io/hyperliquid-docs/for-developers/nodes/foundation-non-validating-node-for-infra-providers)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.coinmarketman.com/hyperliquid-node-peering.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.