Hyperliquid (network congestion) other on 2024-02-28

Other on Hyperliquid, 28 Feb 2024. Last verified 4 Nov 2026.

info
Reported loss
Not stated
no amount published
Recovered
-
nothing reported
Status
Unknown
updated 26 Oct 2026
Date
Hyperliquid

Summary

On 2024-02-28 network congestion degraded Hyperliquid's service from 17:26 to 17:32 UTC. After reviewing more than five hundred support tickets the team distributed refunds to affected users who confirmed, and shipped throughput and mark price improvements.

Protocol
Hyperliquid (network congestion)
Type
Other
Reported loss
not stated
curated history · updated 2026-10-26 15:28 UTC

Facts and where they come from

Approved facts and their primary sources
FactValueSource
DateFeb 28 from 17:26-17:32 UTCt.me ↗
Tickets>500 ticketst.me ↗

Primary sources

Our own summary of facts published by the sources above. We do not attribute fault beyond them. Amounts are as the sources state them (no USD conversion by us); links and quoted figures last checked 2026-11-04.

Get the next one first

How we report incidents

LiveHyperliquid markets 18sOperationalHyperliquid positions & whales 4sOperationalLiquidation heatmap & levels 9sOperationalLighter markets & liquidations 8sOperationalLighter positions & heatmap 8sOperationalLighter RH positions & heatmap 8sOperationalBinance markets 15sOperationalBybit markets 36sOperationalBinance liquidations 28sOperationalBybit liquidations 28sOperationaldYdX positions & heatmap 16sOperationalGMX positions & heatmap 14sOperationalLong/short & open interest history 1mOperationalOrder books & trade flow 8sOperationalOn-chain transfers 7sOperationalSecurity monitor 8sOperationalBlockmetric Sentiment 8mOperationalOfficial news 1mOperationalAlert delivery 7sOperational10:20:18 UTCData: Blockmetric Research · Binance · Bybit