Welcome to the next crypto level
← Nexorena

Altcoins

Quicknode closes incident that blocked transaction submissions on the HyperEVM testnet

The provider declared the incident resolved at 15:26 UTC on November 8. It put the upstream testnet’s recovery at about 12:00 UTC, after submission failures that began at approximately 03:00 UTC.

Nexorena Editorial Team

Quicknode closes incident that blocked transaction submissions on the HyperEVM testnet

The provider separates the disruption from the service recovery

Quicknode closed a performance incident affecting its endpoints for Hyperliquid’s HyperEVM testnet on November 8. In the report published at 14:36 UTC, the provider attributed transaction submission failures to an upstream testnet stall beginning at approximately 03:00 UTC. It put the upstream recovery at about 12:00 UTC and said transaction submissions subsequently operated normally through its affected endpoints. It published the formal closure at 15:26 UTC.

These times mark different stages. At 05:42 UTC, Quicknode said it was investigating and that customers might see a high transaction drop rate. The 12:00 UTC time is the approximate recovery time the provider gave later. The 14:36 UTC update moved the incident to monitoring, and the 15:26 UTC update declared it resolved. The report gives neither the number of affected transactions nor the technical details of the upstream cause.

The endpoints served the test network

HyperEVM is Hyperliquid’s environment for contracts compatible with the Ethereum Virtual Machine. According to Hyperliquid’s documentation, its testnet and mainnet have separate endpoints. An RPC endpoint lets an application or wallet send a request to the network, for example to read a block or submit a signed transaction. Quicknode lists the HyperEVM testnet component in this incident. The published times apply to the scope the provider identified.

The report says submissions could fail as applications tried to reach the testnet. It does not describe the effects on every read method or on transactions submitted by each customer. An application can observe several states between submitting a transaction and seeing it included in a block. A missing confirmation alone therefore cannot identify the stage at which a transaction stopped. Client logs and the transaction identifier, where available, help with that diagnosis.

The observed recovery came before the incident closed

The monitoring phase opened at 14:36 UTC followed the recovery Quicknode placed at about 12:00 UTC. It was the period when the provider said it was still observing the stability of transaction submissions after service had returned to normal. The final notice at 15:26 UTC marked the end of tracking on its public status page. The times answer two distinct questions, when service returned and when public monitoring ended.

To reconstruct a test run that day, developers have the timeline Quicknode published and the logs from their own integration. The report establishes that transaction submissions recovered on the affected endpoints. The outcome of an individual attempt depends on what was recorded for that operation. The resolution notice does not provide an individual account of the transactions submitted earlier.

Written with love byOlivia ParkerMeet this editorial pen name ↗

Explorer Nexorena