Binance futures $90B market went offline last night before 25 minute recovery
The post Binance futures $90B market went offline last night before 25 minute recovery appeared on BitcoinEthereumNews.com. Binance restored futures trading on Aug. 29 following a suspension tied to an issue in its USD-margined contracts. Per Reuters, the exchange first said all of its $90 billion futures trading was “temporarily unavailable,” then about 24 minutes later said the problem affecting Futures UM, the stack that settles contracts in USDT or USDC, had been resolved and that all futures trading was fully operational. In the follow-up note, Binance wrote, “The issue affecting Futures UM trading on Binance has been resolved,” adding that “all futures trading is now fully operational,” as reported by Reuters. The company did not disclose the root cause or provide additional technical details. The sequence matters for derivatives participants who route hedges through USD-margined instruments. UM contracts use stablecoins for margin and settlement, while coin-margined contracts rely on the underlying asset, a design split that can confine faults to one margining domain when they arise. Binance named UM in its restoration message, and did not mention coin-margined contracts in either alert, which frames the scope of the disruption without confirming whether other stacks were unaffected. Basic product distinctions are laid out in Binance’s USDⓈ-M and COIN-M contracts documentation. Timestamps on the two Binance Futures X updates, 06:35 UTC for the suspension and 07:00 UTC for the all-clear, establish a concise public window for the incident. That interval does not necessarily capture the precise start or internal detection time, yet it sets a useful external marker for traders that monitor funding, order book depth, and liquidity across venues during service interruptions. Binance’s public materials emphasize reliability. A recent engineering blog cited 99.98% overall API uptime for the first half of 2025, including a previously disclosed 45-minute episode affecting UM APIs during peak activity. Today’s communication did not reference that report, and the firm has not published…
The post Binance futures $90B market went offline last night before 25 minute recovery appeared on BitcoinEthereumNews.com.
Binance restored futures trading on Aug. 29 following a suspension tied to an issue in its USD-margined contracts. Per Reuters, the exchange first said all of its $90 billion futures trading was “temporarily unavailable,” then about 24 minutes later said the problem affecting Futures UM, the stack that settles contracts in USDT or USDC, had been resolved and that all futures trading was fully operational. In the follow-up note, Binance wrote, “The issue affecting Futures UM trading on Binance has been resolved,” adding that “all futures trading is now fully operational,” as reported by Reuters. The company did not disclose the root cause or provide additional technical details. The sequence matters for derivatives participants who route hedges through USD-margined instruments. UM contracts use stablecoins for margin and settlement, while coin-margined contracts rely on the underlying asset, a design split that can confine faults to one margining domain when they arise. Binance named UM in its restoration message, and did not mention coin-margined contracts in either alert, which frames the scope of the disruption without confirming whether other stacks were unaffected. Basic product distinctions are laid out in Binance’s USDⓈ-M and COIN-M contracts documentation. Timestamps on the two Binance Futures X updates, 06:35 UTC for the suspension and 07:00 UTC for the all-clear, establish a concise public window for the incident. That interval does not necessarily capture the precise start or internal detection time, yet it sets a useful external marker for traders that monitor funding, order book depth, and liquidity across venues during service interruptions. Binance’s public materials emphasize reliability. A recent engineering blog cited 99.98% overall API uptime for the first half of 2025, including a previously disclosed 45-minute episode affecting UM APIs during peak activity. Today’s communication did not reference that report, and the firm has not published…
What's Your Reaction?
