Hyperliquid (API order delays) other on 2025-07-29

Other on Hyperliquid, 29 Jul 2025. Last verified 4 Nov 2026.

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

Summary

On 2025-07-29 a traffic spike on Hyperliquid's API servers delayed orders from about 14:10 to 14:47 UTC and returned errors for transactions that were still executed. Hyperliquid said there was no hack or exploit and later distributed refunds to affected users.

Protocol
Hyperliquid (API order delays)
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
Date14:10-14:47 UTC on July 29t.me ↗
Causeno hack or exploitt.me ↗
Statusrefunds distributedt.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 6sOperationalHyperliquid positions & whales 4sOperationalLiquidation heatmap & levels 11sOperationalLighter markets & liquidations 16sOperationalLighter positions & heatmap 5sOperationalLighter RH positions & heatmap 6sOperationalBinance markets 3sOperationalBybit markets 25sOperationalBinance liquidations 16sOperationalBybit liquidations 16sOperationaldYdX positions & heatmap 4sOperationalGMX positions & heatmap 16sOperationalLong/short & open interest history 48sOperationalOrder books & trade flow 6sOperationalOn-chain transfers 4sOperationalSecurity monitor 53sOperationalBlockmetric Sentiment 8mOperationalOfficial news 1mOperationalAlert delivery 5sOperational10:20:06 UTCData: Blockmetric Research · Binance · Bybit