Monday, November 16, 2026

No, Hyperliquid is producing blocks

Its newest block, number 51,380,639, was made 1 s before our check at 02:14 UTC, by the chain's own clock. It normally makes one every 984 ms.

Read from the chain 50 s ago

Each mark is a minute of blocks; a shorter mark means fewer than normal. Hatched stretches are halts we confirmed. Point at the rail or use the arrow keys to read it.

984 msnormal time between blocks
984 msaverage over the last hour
InstantfinalityHyperBFT
Nonehalts on record
100%uptime we measured, last 3 days
100%on one client, single implementation

Halts over time

Every halt and finality stall on record for Hyperliquid since 2024: from postmortems, status pages and news reports, plus the ones we measured ourselves. Point at a dot, or focus the rail and use the arrow keys; Enter opens the incident.

No halt or finality stall on record for Hyperliquid since 1 January 2024.

We have measured Hyperliquid ourselves since 12 Nov 2026; anything earlier is from the public record.

Block production, hour by hour

Average time between blocks for each hour over the last 7 days, or since we started measuring on 12 Nov 2026. The dashed line is the normal pace. Red hours contain a halt; empty hours are gaps in our sampling.

0 ms984 ms2 s12 Nov 21:00 UTC: 985 ms per block12 Nov 22:00 UTC: 984 ms per block12 Nov 23:00 UTC: 983 ms per blockFri 1313 Nov 00:00 UTC: 983 ms per block13 Nov 01:00 UTC: 983 ms per block13 Nov 02:00 UTC: 984 ms per block13 Nov 03:00 UTC: 984 ms per block13 Nov 04:00 UTC: 984 ms per block13 Nov 05:00 UTC: 984 ms per block13 Nov 06:00 UTC: 984 ms per block13 Nov 07:00 UTC: 984 ms per block13 Nov 08:00 UTC: 984 ms per block13 Nov 09:00 UTC: 984 ms per block13 Nov 10:00 UTC: 983 ms per block13 Nov 11:00 UTC: 984 ms per block13 Nov 12:00 UTC: 984 ms per block13 Nov 13:00 UTC: 984 ms per block13 Nov 14:00 UTC: 984 ms per block13 Nov 15:00 UTC: 984 ms per block13 Nov 16:00 UTC: 984 ms per block13 Nov 17:00 UTC: 984 ms per block13 Nov 18:00 UTC: 984 ms per block13 Nov 19:00 UTC: 983 ms per block13 Nov 20:00 UTC: 984 ms per block13 Nov 21:00 UTC: 984 ms per block13 Nov 22:00 UTC: 984 ms per block13 Nov 23:00 UTC: 984 ms per blockSat 1414 Nov 00:00 UTC: 984 ms per block14 Nov 01:00 UTC: 984 ms per block14 Nov 02:00 UTC: 983 ms per block14 Nov 03:00 UTC: 984 ms per block14 Nov 04:00 UTC: 984 ms per block14 Nov 05:00 UTC: 984 ms per block14 Nov 06:00 UTC: 984 ms per block14 Nov 07:00 UTC: 984 ms per block14 Nov 08:00 UTC: 1 s per block14 Nov 09:00 UTC: 984 ms per block14 Nov 10:00 UTC: 984 ms per block14 Nov 11:00 UTC: 984 ms per block14 Nov 12:00 UTC: 984 ms per block14 Nov 13:00 UTC: 984 ms per block14 Nov 14:00 UTC: 984 ms per block14 Nov 15:00 UTC: 984 ms per block14 Nov 16:00 UTC: 984 ms per block14 Nov 17:00 UTC: 984 ms per block14 Nov 18:00 UTC: 984 ms per block14 Nov 19:00 UTC: 983 ms per block14 Nov 20:00 UTC: 984 ms per block14 Nov 21:00 UTC: 983 ms per block14 Nov 22:00 UTC: 984 ms per block14 Nov 23:00 UTC: 984 ms per blockSun 1515 Nov 00:00 UTC: 984 ms per block15 Nov 01:00 UTC: 984 ms per block15 Nov 02:00 UTC: 984 ms per block15 Nov 03:00 UTC: 984 ms per block15 Nov 04:00 UTC: 984 ms per block15 Nov 05:00 UTC: 983 ms per block15 Nov 06:00 UTC: 984 ms per block15 Nov 07:00 UTC: 984 ms per block15 Nov 08:00 UTC: 984 ms per block15 Nov 09:00 UTC: 984 ms per block15 Nov 10:00 UTC: 984 ms per block15 Nov 11:00 UTC: 984 ms per block15 Nov 12:00 UTC: 984 ms per block15 Nov 13:00 UTC: 984 ms per block15 Nov 14:00 UTC: 984 ms per block15 Nov 15:00 UTC: 984 ms per block15 Nov 16:00 UTC: 984 ms per block15 Nov 17:00 UTC: 984 ms per block15 Nov 18:00 UTC: 984 ms per block15 Nov 19:00 UTC: 984 ms per block15 Nov 20:00 UTC: 984 ms per block15 Nov 21:00 UTC: 984 ms per block15 Nov 22:00 UTC: 984 ms per block15 Nov 23:00 UTC: 984 ms per blockMon 1616 Nov 00:00 UTC: 984 ms per block16 Nov 01:00 UTC: 984 ms per block16 Nov 02:00 UTC: 984 ms per blocknormal 984 ms

Halts we detected

None so far. We have been measuring since 12 Nov 2026.

The public record since 2024

From postmortems, status pages and news reports.

No halts, finality stalls or major degradations on record since January 2024.

Before 2024: No confirmed HyperCore/HyperEVM chain halt. QuickNode (via isdown.app, 403 when opened) reportedly logged a HyperEVM network-wide stall at block 8,816,123 on 2025-07-19 (~2 h, tied to a scheduled network upgrade). The Jul 29 2025 outage was API/order execution only (status showed L1 fine), and the Apr 2 2026 PeckShield 'HyperEVM failure' appears to have been explorer data lag. Source

Client software

hl-node Single implementation

Validators run Hyperliquid's own node software, which is not open source.

ChainReport review of official repositories and docs, 12 Nov 2026. Compare all chains

Compare

Embed this status

Show the live Hyperliquid status in your docs, dashboard or README.

Is Hyperliquid down? Live status by ChainReport

The badge updates about once a minute and links back to this page. Feed for Hyperliquid incidents: Atom.

Links

We read Hyperliquid from two places: first source PublicNode and second source Hyperliquid public RPC.

Other chains

Also on the Network Desk for Hyperliquid

How this works and where the data comes from

What we measure. Every minute a server job asks each chain for its newest block and reads the timestamp the chain itself put in that block. "Last block" is now minus that timestamp, so it is accurate even if our own checks run late. "Last hour" is the average spacing between blocks over the past hour, also from block timestamps.

When we call a halt. A chain counts as halted when no new block has appeared for much longer than normal. The limit is set per chain: 2 minutes for most fast chains, 5–7 minutes for Scroll, ZKsync and Cardano, 14 minutes for Dogecoin, 30 minutes for Litecoin and 2 hours for Bitcoin, where long gaps happen by chance. Before declaring a halt we ask a second, independent data provider. If one provider is stale and the other is fresh, the chain is fine and we log the provider as lagging. For Solana, Sui and Cardano we have only one free source, so we wait for three stale checks in a row. Start time is the last block before the stop; end time is the first new block, within about a minute.

Finality. For Ethereum we read the last finalized checkpoint from the beacon chain (normally 2 epochs, about 13–19 minutes behind). For other EVM chains and Polkadot we read the newest "finalized" block from the node. On rollups (Base, Arbitrum, OP, ZKsync, Scroll), "finalized" means settled on Ethereum, which takes longer by design: hours on ZKsync. Free Solana endpoints do not report commitment levels reliably, so we do not show Solana finality.

Limits. We have been measuring since 12 Nov 2026; uptime figures cover only that period and say so. If our job misses minutes, a halt that started and ended entirely inside that gap would show up only as a slow hour in the chart. The historical record before our measurements comes from postmortems and news reports, with approximate times marked "≈". Hyperliquid is measured through HyperEVM, which stops whenever the HyperCore L1 stops.

Sources: PublicNode; Hyperliquid public RPC; Historical record: project postmortems, status pages, The Block, CoinDesk, Cointelegraph, Decrypt (linked per row)

Information only, not financial advice. Data comes from public sources and can be delayed or wrong; check the primary source before acting.

Scroll to Top
Chain Report
Privacy Overview

This website uses cookies so that we can provide you with the best user experience possible. Cookie information is stored in your browser and performs functions such as recognising you when you return to our website and helping our team to understand which sections of the website you find most interesting and useful.