Private network access
Japan // Tokyo
Active
Germany // Frankfurt
Active
Direct Sentry Peering for Hyperliquid
Connect privately to Hyperdash sentry nodes for consistent sync and dependable connectivity. Built for market makers, builders, and infrastructure teams that need reliable, real-time sync via private sentry peering.
- 99.99%
- Validator SLA-backed uptime
- 24/7
- Monitoring and alerting
With Direct Sentry Peering, benefit from improved performance, reliability, and connection directly to our Hyperliquid validator node.
Faster data retrieval
Reduced hops mean lower tail latency to fills, blocks, and state updates. Get the data you need faster.
Higher reliability
Stable peer with monitored, SLA-backed infrastructure. No more congestion or disconnecting from public peers.
Bespoke Integration
Work directly with our engineering team to integrate into your systems, optimizing for speed and uptime.
Performance that speaks for itself.
One hop. No middle layers.
Public routes bounce through shared, capacity-constrained peers. Direct Sentry Peering connects your node straight to our validator-colocated infrastructure.
Direct connection to validator node
Private, whitelisted peering
Held through congestion and upgrades
Infrastructure, monitoring, and support.
Comprehensive coverage for direct connectivity to Hyperliquid, ran with the same standard as our validator node.
99.99% Uptime
Reliable infrastructure, backed by a 99.99% uptime commitment.
Your dedicated team
Hands-on onboarding and ongoing support channel whenever you need it.
24/7 monitoring and alerting
Continuous monitoring with real-time alerts and signals.
| Block | Txs | Validator |
|---|---|---|
| 1,114,870,316 | 4,284 | 0x8A53...A5D6 |
| 1,114,870,283 | 2,983 | HYPERDASH |
| 1,114,870,252 | 4,074 | 0xE6CC...3599 |
| 1,114,870,221 | 4,163 | 0x9978...72BE |
Onboarding made simple
Upgrade your system same day with sentry node access
Step 1
Whitelist
Send us the static IP of your node. We whitelist it to our validator sentry node.
Step 2
Configure
Set our sentry IP as the root entry in your override gossip config.
Step 3
Activate
You're live. Your node receives blocks over a fast, stable, always-on connection, one hop from the validator set and held through congestion and upgrades.
Frequently asked questions
How does this differ from consuming a WebSocket data feed or API?
Sentry peering removes the distribution layer entirely. Any hosted feed must receive, process, and rebroadcast data before it reaches you; with direct peering, your node receives blocks over Hyperliquid's native gossip protocol and you decode locally. For latency-sensitive systems this is the recommended architecture.
What latency improvement should we expect?
Results depend on each firm's infrastructure, region, and processing pipeline, and gossip-layer latency is set by the network. The evaluation period exists so you can benchmark against your current setup from your own machines.
How does the sentry compare to public foundation peers?
Public foundation peers are capacity-constrained and disconnect without notice, particularly around network upgrades. The sentry provides deterministic connectivity with the same latency.
Is mempool data included?
Yes. Our infrastructure runs split_client_blocks end to end, so mempool_txs populate on your node.
Are you in our execution path, and is our activity private?
No. Order submission goes directly to Hyperliquid's API; we are never in the execution path. We do not record or retain data that could expose your activity.
What is the uptime commitment?
The sentry shares our validator's uptime of 99.99%, maintained to Hyperliquid Foundation standards with continuous monitoring. Realistic downtime scenarios are network-wide events rather than issues specific to our infrastructure.
Can we change or add whitelisted IPs?
Yes. IPs can be swapped as you move from staging to production, and additional IPs or regions can be added at a reduced rate per IP.
Who can get access?
Access is gated to Hyperliquid-aligned teams committed to sound operational practice. No client code runs on our validators; peering terminates at the sentry only, and we reserve the right to prioritize or decline requests to maintain fairness, reliability, and alignment with network best practices.