Crypto.com and Gemini resolved two separate service disruptions on November 3, 2026, affecting prediction-market trading and cryptocurrency deposits. In today’s crypto exchange roundup, Crypto.com restored prediction trading, including strike options, after an incident lasting approximately two hours and 18 minutes, while Gemini closed an Arbitrum deposit-processing incident that had remained open for more than 23 hours.
Both exchanges confirmed restoration through their official status pages. Neither disclosed the technical cause, the number of affected customers or the volume of disrupted transactions. The incidents involved different services, and there is no evidence connecting them.
Crypto.com prediction trading disrupted for over two hours
Crypto.com reported a disruption affecting prediction trading for customers using its main application on November 3, including its strike options products.
The company opened its incident report at 07:01 Hong Kong time (23:01 UTC on November 2), acknowledging problems with prediction trading and stating that its technical team was investigating.
At 07:22 HKT, Crypto.com reported that the investigation was continuing. It subsequently marked the incident resolved at 09:19 HKT, giving the publicly recorded incident a duration of two hours and 18 minutes.
The status notice did not explain whether customers were unable to open new contracts, close existing positions, cancel pending orders or perform some combination of those activities. It also did not establish whether trading functionality remained unavailable throughout the entire incident window.
Crypto.com’s prediction trading business operates through Crypto.com Derivatives North America (CDNA). The CFTC’s registration record identifies NADEX, doing business as Crypto.com Derivatives North America, as a registered derivatives clearing organisation authorised for specified futures, options and swaps activities.
The affected products include strike options, which allow traders to take positions on whether the price of an underlying asset will exceed a specified level at expiration. Crypto.com’s available contract durations include five minutes, 20 minutes, two hours and longer periods.
Some of these contracts could have expired within the recorded disruption window. Five-minute and 20-minute contracts, in particular, have little room for an extended interruption. But that is a product-level observation, not confirmation that any particular contract expired while its holder was unable to trade.
The new incident follows an earlier Crypto.com prediction-order outage lasting 43 minutes on October 2. During that event, the exchange specifically reported a backend failure preventing users from placing prediction orders.
The November 3 disruption lasted more than three times as long as the October incident, based on the respective status timestamps. The latest disclosure does not identify the same backend component or provide evidence of a recurring technical fault.
And the unresolved trading questions are much the same. Crypto.com has not disclosed whether previously submitted orders continued executing, whether customers could manage existing positions or whether any contracts encountered settlement delays.
The company also did not report customer losses, failed-order totals or a compensation programme associated with the latest incident. Its conventional cryptocurrency exchange trading, deposits and withdrawals were not identified as affected in the incident notice.
Gemini resolves Arbitrum deposit delays after 23 hours
Gemini separately confirmed the resolution of an Arbitrum deposit-processing incident that remained open for approximately 23 hours and 19 minutes.
The exchange first acknowledged the problem at 04:43 Eastern Standard Time (09:43 UTC) on November 2, reporting delays in processing cryptocurrency deposits over the Arbitrum network.
Gemini said its team was investigating and assured customers that all accounts and funds remained secure.
The next recorded update marked the issue resolved at 04:02 EST (09:02 UTC) on November 3. There was no intermediate public notice identifying the cause, announcing a deployed fix or indicating when deposit processing began returning to normal.
That leaves a gap of almost a full day between the opening and closing updates. The 23-hour duration is confirmed for the incident record, but it does not independently establish that every affected deposit remained delayed throughout that period.
Arbitrum is an Ethereum Layer 2 network used for transferring digital assets and interacting with decentralised applications. Deposits to a centralised exchange generally require the exchange to detect the blockchain transaction, process its required confirmations and credit the customer’s account.
Gemini has not identified which part of that process was delayed. Its notice does not establish that the Arbitrum blockchain itself stopped operating or that the exchange experienced a failure of its broader wallet infrastructure.
The issue resembles earlier network-specific funding disruptions at Kraken, where cryptocurrency deposits and withdrawals were delayed on particular networks while unrelated funding methods continued functioning.
Gemini did not disclose the number of deposits awaiting credit, their total value or whether transactions were automatically reconciled after restoration. There is also no public evidence in the incident notice of lost customer assets or a broader withdrawal suspension.
Two outages expose different operational questions
The two disruptions affected different stages of cryptocurrency trading activity.
Crypto.com’s incident concerned access to time-sensitive derivatives trading. The significance of an interruption depends partly on whether existing positions could be managed while the prices or underlying events continued changing.
Gemini’s problem concerned the processing of incoming blockchain deposits. A customer could have completed an on-chain transfer but still been unable to use the assets on the exchange until they were credited. No specific customer outcome has been established in the public record.
A recent DaveFinances roundup covering Coinbase’s DEX, Borrow and Lend disruptions documented another case of product-specific service degradation. Coinbase’s incident remained open for more than nine hours on November 2, without its notice identifying a corresponding failure of centralised trading.
These incidents do not establish a common infrastructure problem across exchanges. They do illustrate how different products can become unavailable even when wider platform operations are not reported as affected.
For Crypto.com, the missing evidence concerns order handling, position management and contract settlement during the disruption. For Gemini, it concerns deposit-crediting delays and the number of transactions still pending when service was restored.
Both services were marked resolved on November 3. The status records confirm the restoration announcements, but the full customer impact remains unquantified. There is no published transaction-level breakdown from either exchange, and no independant evidence connecting the two failures.
Johan Shamshad is a financial markets writer at Dave Finances covering cryptocurrencies, trading platforms, brokers, fintech, financial regulation, and developments across global markets. He previously worked at Gulf News, adding newsroom experience to his coverage of fast-moving financial and digital-asset markets.
His work focuses on identifying market-moving events, company developments, regulatory changes, product launches, and shifts in trading and financial infrastructure.
Johan contributes news and analysis designed to help readers understand not only what happened, but why a development matters and how it may affect the wider financial landscape. You can reach out to him via his social media accounts:
Linkedin: https://www.linkedin.com/in/johan-shamshad-742851262/
X: https://x.com/Yasmine_FX
Investing: https://www.investing.com/members/contributors/279781574