Help & contact

From real positions: each tracked position reports its own liquidation price, and a heatmap cell is the USD of tracked positions that would be liquidated there. It is not a model built from open interest and assumed leverage. Full heatmap method.

Positions of wallets we do not track and every venue that does not publish positions, such as the centralised exchanges; the daily snapshot of every Hyperliquid position is the exception. What each layer covers.

Every plan shows every coin. Free: the heatmap of the last 24 hours with 15m and 1h columns; live snapshots start on 2026-11-03 14:15 UTC. Pro and Desk reach further back: history per plan.

Positions are polled: the largest wallets every few minutes, smaller ones less often, so a position can be minutes to hours old; markets are sampled every 30 to 60 seconds. The dot in each panel header shows the age of its data. Every feed with its last update: status; the measured age of every dataset right now: data freshness; the schedule: sources and cadence.

Every data panel names its sources in a small "Source:" line. Each source, what it is used for and whether it is on: data sources.

Exchange totals are the liquidation orders Binance and Bybit publish on their public streams, summed by us, so they are lower bounds. Hyperliquid liquidations of every wallet come from Hyperliquid's official archive, imported hour by hour; for the newest hours, before the archive covers them, only tracked wallets whose own fills confirm a liquidation count. Limits and gaps: known gaps.

You choose a Hyperliquid address and a threshold (0.5–25%). When a position of that address comes within the threshold of its liquidation price, you get an alert. It is re-armed once the distance is back above the threshold plus 25%, so a price hovering at the line does not spam you. Opens, closes, flips and liquidations of the address are reported too. Free accounts watch 1 live wallet (Guard and wallet alerts together) and get 5 market alert rules on top (whale, cluster, funding, RSI …). Open Liquidation Guard.

Telegram and e-mail on every plan, plus alert webhooks and Telegram groups (Pro, Desk, API Dev and API Pro). On Telegram every guarded position has one message that is edited in place as the distance changes; a new message is sent only when the threshold is crossed or the position is liquidated. E-mail, alert webhooks and Telegram groups get threshold crossings and liquidations only.

After connecting the chat (Connect Telegram):/guard <address> [percent], /unguard <address>, /watch <address>, /unwatch <address>, /positions, /alerts, /mute 1h|8h|24h|off, /status, /help and /unlink to disconnect. Without an account: /price, /liq, /heatmap, /funding, /whales and /sentiment. Blocking the bot pauses Telegram alerts; unblock it and press Start to resume.

Yes, in notification settings: mute everything for 1, 8 or 24 hours or until you switch it on again, set quiet hours in your time zone, or bundle non-critical alerts per channel into an hourly digest. Alert e-mails contain a one-click unsubscribe link.

No. Alerts state facts (wallet, coin, size, price, distance). Nothing here is investment advice.

Every plan, its limits and the billing questions (free trial, refunds, switching, cancelling) are on Pricing; the answers are under its questions. To cancel right now, without logging in: cancel contract.

A payment provider / merchant of record. You enter payment details on their page; we only receive plan, status, term and a customer id. Invoices are issued there.

What the API is and the first request: API. Limits, the data licence and the plans: API pricing. Keys are managed under Account › API keys & usage, event webhooks under Account › Event webhooks; alerts to your own server are alert webhooks, set up under Account › Notifications. Stored history in bulk: Historical data.

What RPC is, what is open and the waitlist: RPC; chains and features we do not offer yet can be requested there too (request one). Plans and billing: RPC pricing. Endpoint tokens and usage are under Account › RPC endpoints & usage.

No tracking cookies and no third-party analytics. We count page views on our own server in aggregated form (page, day, referring site, campaign tag, device class) without IP address, cookie or identifier; browsers with Do Not Track or Global Privacy Control are not counted. Details: privacy policy.

Yes, both on account → privacy & data: a JSON export of your account, rules, guarded wallets, API key metadata and recent deliveries, and self-service deletion of the account.

Turn on two-factor authentication (any authenticator app) and review your logged-in devices under Account › Security.