Fri. Nov 20th, 2026

Kraken futures dead man’s switch fails to cancel orders

ByJohan Shamshad

November 20, 2026
Crypto Exchange KrakenCrypto Exchange Kraken

Kraken warned futures traders on November 19 that requests to activate its automatic order-cancellation safeguard were being rejected, leaving outstanding orders exposed to execution after their configured timeouts expired. The incident affected the exchange’s Unified WebSocket API, and Kraken had not announced a confirmed fix in its latest public update at 20:26 UTC.

The faulty feature, known as cancel-after-timeout or a dead man’s switch, is intended to remove working orders automatically when the client fails to refresh its cancellation timer. Kraken said users relying on it should monitor and manage open orders directly until the function returns. Not a platform-wide shutdown.

Kraken identifies a failure in the futures safety control

Kraken first acknowledged the cancel-after-timeout incident at 20:06 UTC on November 19. Its status notice said the exchange had identified the cause and was working on a fix. Twenty minutes later, at 20:26 UTC, the operator said that work was continuing, without giving a restoration time or technical explanation.

The component identified in the incident was Kraken API (Unified WebSocket). That narrows the confirmed scope: the official report concerns rejection of one futures risk-control request, not a verified exchange-wide breakdown in order entry, account access, withdrawals or market pricing. The number of affected clients and contracts was not disclosed.

The response also leaves a key question unanswered. Kraken did not publicly say when the rejecting behavior began, how long the function might have been failing before the first notice, or whether all clients using that interface were affected in precisely the same way. Those details are missing.

Why an expired timeout can leave traders with live orders

Automated futures market makers commonly maintain bids and offers through software rather than monitoring each order by hand. A dead man’s switch adds protection if the software crashes, loses its connection or stops sending expected renewal messages. Instead of waiting for an operator to return, the exchange is meant to cancel orders after the set delay.

During this incident, Kraken warned that outstanding futures orders would not be cancelled automatically when their configured timeout expired. A trader could therefore assume a safety timer would clear resting bids or offers while those instructions remained in the order book. Orders could stay there.

That matters because a resting order may execute against another trader even when its owner is offline or has stopped updating prices. A market maker relying on stale quotations could acquire an unwanted position, lose an intended hedge or take on greater exposure during a rapid move. These are possible consequences of the failed control, not losses that Kraken has reported as having occured.

Kraken advised direct order monitoring and management. The notice did not say manual cancellation through other availble interfaces had failed, nor did it establish that a rejected safety request would prevent a trader from submitting an ordinary cancellation. The absence of automatic protection and the unavailability of every way to manage orders are seperate claims.

Earlier Kraken interruptions carried different risks

Kraken has reported other derivatives-related service problems this year, though none has been linked to the November 19 fault. During a November 3 incident covered by DaveFinances, the platform displayed incorrect estimated liquidation prices for some perpetual futures positions. Kraken corrected that problem and did not report actual liquidations at incorrect levels.

In September, scheduled NinjaTrader futures maintenance prevented customers from placing or managing futures orders for around two and a half hours. That was an announced infrastructure interruption, unlike the latest unexpected rejection of a specific automatic safety function.

Another Kraken US futures maintenance record spanning October 30–31 lasted more than 14 hours against an initially announced period of up to two hours, although the status history did not prove that trading functions remained unavailable for every recorded minute. The earlier events underline the importance of independent risk controls, without providing evidence of a shared root cause.

No confirmed executions or customer losses disclosed

The new incident raises an audit question for algorithmic firms: which orders were live at each point in time, which dead man’s switch requests were rejected and whether any orders were subsequently executed after a trader expected a timeout cancellation. The answers would require client request logs, server acknowledgments and exchange execution records. Kraken has not published such a breakdown.

Kraken Prime also had distinct API maintenance scheduled for 21:00 UTC on November 19. That notice concerned another service and should not be treated as the cause of the earlier Unified WebSocket fault without evidence connecting them.

As of the reviewed status record, there was no confirmed fix, no customer-loss total and no published evidence that the failure triggered unintended fills. For trading clients, a rejected cancel-after-timeout request is itself a reason to check open-order state rather than rely on a timer acknowledgment they did not recieve. The fix was still pending.

Editor-in-Chief at  | More Posts

Johan Shamshad is Editor-in-Chief at Dave Finances, covering financial markets, digital assets, trading platforms, brokers, fintech, payments and regulation. Since 2023, he has also worked as an editor at Gulf News, the UAE English-language newspaper published by Al Nisr Publishing LLC. His work focuses on market-moving developments, company disclosures, regulatory changes and trading infrastructure, with an emphasis on primary-source verification and practical context for traders and investors.

Disclaimer: This content is for informational purposes only and does not constitute financial, investment, legal, or trading advice. Trading and investing involve risk. Read our full Disclaimer.