Kraken’s scheduled order-entry maintenance window opened on October 27, 2026, with some traders facing the risk of rejected orders or slower API responses. The exchange announced a maintenance period of up to 60 minutes and identified Kraken Pro, WebSocket and FIX API users as potentially affected.
The work was announced on October 26, a day before the planned window. Kraken described the event as scheduled maintenance. Its notice did not report a cyberattack, a security breach or a shutdown of all trading markets.
Which Kraken Pro and API requests may be affected
The official maintenance notice sets out different effects for each trading channel. Kraken Pro users on the web, mobile and desktop platforms may encounter a very small number of rejected requests when placing or modifying orders.
For clients trading through the WebSocket API, Kraken warned of a small number of rejected order submissions and changes, along with higher latency. FIX API clients could encounter several seconds during which new orders and modifications are rejected. They may also see slower responses.
These are possible effects, rather than confirmed failures for every customer. Kraken has not published figures showing how many traders or orders were affected by the October 27 work. Its warning also does not establish that previously accepted orders were canceled.
Order-entry maintenance is not a confirmed trading halt
An order-entry system accepts new trade instructions and requests to modify existing orders. A temporary failure at this stage can matter to a trader trying to enter, adjust or exit a position, particularly when prices are moving quickly.
That does not mean every market has stopped matching orders. Kraken’s trading-mode guide distinguishes normal trading from full maintenance, cancel-only, post-only and limit-only modes. Each mode has its own rules for placing, canceling and matching orders.
The October 27 notice concerns possible order submission and modification issues. It does not say that all markets entered the exchange’s full maintenance mode. There is also no basis in the notice to link the scheduled work to a hack or an unauthorized withdrawal.
A second order-entry window follows October 26 work
Kraken carried out another scheduled order-entry maintenance session on October 26. Its status history records that session as starting at 10:00 and being marked complete at 11:05. The separate October 27 window was scheduled to begin at 10:00 and run for up to an hour.
The previous session provides context for the current work, but its completion does not confirm that October 27 maintenance has finished. The exchange has said it will post an update after the latest work is complete.
How traders can verify a delayed order
Traders who encounter an error should distinguish a rejected request from an order that may have been accepted but returned a delayed response. In Kraken’s WebSocket order documentation, an order acknowledgment includes a success field and, for accepted requests, an exchange order identifier. An unsuccessful request includes error information.
Checking open orders, recent executions and the relevant API acknowledgment before submitting the same instruction again can reduce the risk of duplicate orders. API users can also consult Kraken’s documented trading-status indicators when confirming whether order entry is available.
Kraken told users that no action was required solely because of the scheduled maintenance. Anyone experiencing an unexpected rejection should check the official Kraken status page for the latest completion notice before assuming that normal order entry has resumed.
Disclaimer: This report covers an exchange service notice and is not investment advice. Trading and service availability can change without notice.
