▌tickfoundry
capture livesign inget the data →

Hyperliquid. Pull any coin, any days.

A coin is one perp, spot pair or HIP-3 market, named as the venue names it (BTC, HYPE/USDC, xyz:CL). Pick one, pick a range, get L1 / 25-level L2 / trades parquet, rebuilt from the chain's order stream since 2025-01-25. Included with a Hyperliquid plan (its own subscription, adding up with any other venue's); one free sample day.

Building this yourself — pulling the chain's order-event archive out of requester-pays S3 and replaying it into books — runs to around $10,000 in egress and compute.

Pull several coins in one bundle641 days 2025-01-25 → 2026-10-27 · gapless · 895 coins · 6.8 TB on disk
Coinsnone yet — use “+ pull with others” on the rows below, or search a symbol
→
Tables
Create a free account to download≈ 1 kB · 0 coins · 3 tables
A free account pulls 2026-08-12, any coins, up to 1.0 GB, at no cost; every other day needs a plan bought for Hyperliquid (or for perps, which covers the perpetuals) — see plans.

1–50 of 895 coins · most data

2025-01-25 → 2026-10-27641 days~158 MB/day · 99 GB on diskperpetuals
2025-01-25 → 2026-10-27641 days~153 MB/day · 96 GB on diskperpetuals
2025-01-25 → 2026-10-27641 days~146 MB/day · 92 GB on diskperpetuals
2025-01-25 → 2026-10-27641 days~123 MB/day · 77 GB on diskperpetuals
2025-01-25 → 2026-10-27641 days~121 MB/day · 76 GB on diskperpetuals
2025-01-25 → 2026-10-27641 days~112 MB/day · 70 GB on diskperpetuals
2025-01-25 → 2026-10-27641 days~108 MB/day · 67 GB on diskspot
2025-01-25 → 2026-10-27641 days~98 MB/day · 62 GB on diskperpetuals
2025-01-25 → 2026-10-27641 days~95 MB/day · 59 GB on diskperpetuals
2025-01-25 → 2026-10-27641 days~94 MB/day · 59 GB on diskperpetuals
2025-01-25 → 2026-10-27641 days~92 MB/day · 57 GB on diskperpetuals
2025-01-25 → 2026-10-27641 days~89 MB/day · 56 GB on diskperpetuals
2025-01-25 → 2026-10-27641 days~89 MB/day · 55 GB on diskperpetuals
2025-01-25 → 2026-10-27641 days~84 MB/day · 53 GB on diskperpetuals
2025-01-25 → 2026-10-27641 days~84 MB/day · 53 GB on diskperpetuals
2025-01-25 → 2026-10-27641 days~82 MB/day · 51 GB on diskperpetuals
2025-10-02 → 2026-10-27391 days~132 MB/day · 50 GB on diskperpetuals
2025-01-25 → 2026-10-27641 days~80 MB/day · 50 GB on diskperpetuals
2025-01-25 → 2026-10-27641 days~80 MB/day · 50 GB on diskperpetuals
2025-01-25 → 2026-10-27641 days~78 MB/day · 49 GB on diskperpetuals
2025-01-25 → 2026-10-27641 days~78 MB/day · 49 GB on diskperpetuals
2025-01-25 → 2026-10-27641 days~77 MB/day · 48 GB on diskperpetuals
2025-01-25 → 2026-10-27641 days~77 MB/day · 48 GB on diskperpetuals
2025-01-28 → 2026-10-27636 days~77 MB/day · 48 GB on diskspot
2025-01-25 → 2026-10-27641 days~76 MB/day · 48 GB on diskperpetuals
2025-01-25 → 2026-10-27641 days~75 MB/day · 47 GB on diskperpetuals
2025-01-25 → 2026-10-27641 days~74 MB/day · 47 GB on diskperpetuals
2025-01-25 → 2026-10-27641 days~74 MB/day · 46 GB on diskperpetuals
2025-03-24 → 2026-10-27583 days~81 MB/day · 46 GB on diskspot
2025-01-25 → 2026-10-27641 days~72 MB/day · 45 GB on diskperpetuals
2025-01-25 → 2026-10-27641 days~72 MB/day · 45 GB on diskperpetuals
2025-01-25 → 2026-10-27641 days~71 MB/day · 45 GB on diskperpetuals
2025-01-25 → 2026-10-27641 days~70 MB/day · 44 GB on diskperpetuals
2025-01-25 → 2026-10-27641 days~68 MB/day · 43 GB on diskperpetuals
2025-01-25 → 2026-10-27641 days~68 MB/day · 43 GB on diskperpetuals
2025-01-25 → 2026-10-27641 days~68 MB/day · 43 GB on diskperpetuals
2025-04-11 → 2026-10-27559 days~77 MB/day · 42 GB on diskspot
2025-01-25 → 2026-10-27641 days~67 MB/day · 42 GB on diskperpetuals
2025-01-25 → 2026-10-27641 days~66 MB/day · 41 GB on diskperpetuals
2025-01-25 → 2026-10-27641 days~64 MB/day · 40 GB on diskperpetuals
2025-01-25 → 2026-10-27641 days~64 MB/day · 40 GB on diskperpetuals
2025-01-25 → 2026-10-27641 days~64 MB/day · 40 GB on diskperpetuals
2025-01-25 → 2026-10-27641 days~64 MB/day · 40 GB on diskperpetuals
2025-01-25 → 2026-10-27641 days~63 MB/day · 40 GB on diskperpetuals
2025-01-25 → 2026-10-27641 days~63 MB/day · 40 GB on diskperpetuals
2025-01-25 → 2026-10-27641 days~63 MB/day · 40 GB on diskperpetuals
2025-01-25 → 2026-10-27641 days~63 MB/day · 39 GB on diskperpetuals
2025-01-25 → 2026-10-27641 days~62 MB/day · 39 GB on diskperpetuals
2025-01-25 → 2026-10-27641 days~61 MB/day · 38 GB on diskperpetuals
2025-01-25 → 2026-10-27641 days~60 MB/day · 37 GB on diskperpetuals
page 1 of 18next →

What is on disk

Top of book (every change)hl_l1

Best bid and ask with sizes and the spread, one row per block in which the top of book changed, replayed from the chain's own order events — not sampled from a websocket. No consecutive duplicates.

2025-01-25 → 2026-10-27 · 641 days · 437 GB · 284,987 files
Order book — 25 levels, every changehl_l2

The 25-level book on both sides — price, size and the number of resting orders at each level — one row per block in which any of it changed. Wide columns (bid_px_1 … ask_n_25), unused levels null. This is the table the venue's own websocket cannot give you: Hyperliquid pushes l2Book snapshots only, throttled to seconds.

2025-01-25 → 2026-10-27 · 641 days · 6.2 TB · 284,987 files
Trades (fills)hl_trades

Every fill the chain executed: price, size, taker side, order id, the taker's wallet, fee and fee token, closed PnL and start position, and the settlement transaction hash. From 2025-03-22 straight from the node's fills tape; before that synthesized from the taker's own fill status (see caveats).

2025-01-25 → 2026-10-27 · 640 days · 122 GB · 284,591 files
Read before you pull
  • One row per block, not per message. Blocks land about every 70 ms; l1 has a row for every block in which the top of book changed, l2 for every block in which any of the 25 levels changed, trades one row per fill. msg_seq is the block height.
  • A day is block-aligned, not midnight-aligned. Filter on ts_src_ms for strict UTC days.
  • The book is wide. bid_px_1 … ask_n_25 — price, size and resting-order count per level, best first, unused levels null. Full 25 levels on every plan.
  • Fills before 2025-03-22 are synthesized. No fills tape exists upstream before 2025-03-22, so taker fills in that era are derived from each taker order's own filled size and average price against the resting book (source_event_type = l3_taker_status). price, size, side, oid and user are set; transaction_hash, tid, dir, fee, fee_token, closed_pnl and start_position are null. Resting orders that expired or were cancelled without an event can linger in the book until the order-id-gap inference catches them.
  • Spot books start unseeded. The archive has no snapshot before its first day, so resting spot depth is thinner than steady state for the first day or two.
  • A 2,419-block hole on 2025-06-21 (about 09:21–09:31 UTC). Heights 636551018–636553439 are absent from Hyperliquid's own archive (a truncated source object), during a period when the chain was also producing blocks slowly. Every coin is affected for that interval; nothing else that day.
  • A 3,655-block hole on 2025-06-28 (about 03:39–03:44 UTC). Heights 644034549–644038203 are absent from Hyperliquid's own archive (a truncated source object). Every coin is affected for that interval; nothing else that day.
  • A 924-block hole on 2025-07-19 (about 23:06–23:07 UTC). Heights 668379075 onward, the last minutes of one source object: the object is truncated in Hyperliquid's own bucket. Every coin is affected for that interval; nothing else that day.
  • Book frozen for ~13 minutes on 2025-09-26 and again on 2025-09-27. Heights 743030000–743039999 (2025-09-26 07:19–07:32 UTC) and 743800000–743809999 (2025-09-27 00:20–00:33 UTC): one source object each contributed no order events to our replay although every block is present and the fills tape shows trading throughout. hl_l1 and hl_l2 carry a stale book for those windows on every coin, and the book after each window is reconciled from the venue's next snapshot. hl_trades is complete. Under investigation; the days will be rebuilt if the source objects can be recovered.
  • One block missing on 2026-07-25. A single block near height 1085381400 (about 07:36 UTC) is absent from the source archive. No visible effect on the top of book.
  • Every bundle ships a per-coin quality scorecard and a README with the schemas and these caveats for your exact range. Schema reference: /docs/hyperliquid.