Post #406

Yesterday, the API servers experienced a significant spike in traffic, leading to order delays from approximately 14:10-14:47 UTC. The past weeks have seen back-to-back-to-back all-time highs in open interest as well as record highs in protocol revenue. While growing pains are challenging, they are a testament to Hyperliquid's momentum. To be clear, there was no hack or exploit. The blockchain, consensus, and HyperEVM were unaffected. Blocks were produced at the usual rate despite congestion on the API servers. The API returned error responses despite transactions being sent to the mempool and later included in blocks. This confused many users, and improvements are being rolled out to address this. An update will be shared in the coming days once an appropriate refund methodology has been determined for users impacted by this particular issue. Refunds will be determined in an automated fashion; impacted users do not need to open a ticket at this time. Thank you to the community for their understanding as Hyperliquid continues to scale.