Exchanges
Bitget suspended HIVE/USDT spot trading for maintenance
Bitget’s notice scheduled the suspension of HIVE trading for November 8 at 13:30 UTC. At 14:20 UTC its public API listed the HIVE/USDT pair as suspended.

A suspension announced for November 8
On November 8, 2026, Bitget announced maintenance affecting HIVE spot trading. The work was scheduled to start at 21:30 UTC+8, or 13:30 UTC and 14:30 in Paris. The notice says trading in the pair is suspended during the work and that service is to resume once it is complete. The platform did not specify a resumption time in the announcement.
At 14:20 UTC, a timestamped response from Bitget’s public API identified HIVE as the base asset and USDT as the quote currency for HIVE/USDT. The status field returned the value halt. In the documentation for the endpoint used, that value means trading is suspended. The observation therefore establishes that Bitget showed the suspension after the announced time for that pair at that particular moment.
The status describes the spot market
A spot pair allows the base asset to be traded against the quote currency. Here, the observation concerns trades between HIVE and USDT on Bitget. The documentation distinguishes a pair operating normally from one whose trading has been suspended. The pair can still appear in public data with its identifiers even when its status shows that trading is interrupted. Its presence in the catalog alone does not establish that it can be traded.
Deposits and withdrawals are separate operations from spot trading. The notice concerns the HIVE market and gives no information about the availability of transfers. The status reported in the pair catalog describes neither transfer conditions in Bitget wallets nor how the Hive network is operating. The notice and the snapshot also do not specify what happens to orders open before maintenance.
Trading resumes after maintenance
Bitget says trading will resume when the work is complete. The platform plans a new notice if the schedule changes, including in the event of market volatility. The time in the original announcement therefore refers to the planned start of the work. The duration of the interruption must be determined from a resumption notice or a change in status observed after the snapshot.
To track the restoration of service, the point of comparison is the same HIVE/USDT pair in Bitget’s spot data. A normal status on another pair or another platform says nothing about the end of this maintenance. At the time of the snapshot, the value reported for HIVE/USDT still indicated a suspension. Resumption is a separate step to verify in later information from the platform.
