Kraken's order entry maintenance on 10 and 11 November 2026 is complete. Some order submissions and modifications could be rejected.
Separate API work could also cause brief disconnections and stale WebSocket data. Order history, trading status, and live market data should be checked before an order is resubmitted.
Kraken Order Entry Maintenance left many traders with one question: was a failed order a system problem or a price problem? The two are different, and this article keeps them apart.
Order entry is the system that receives new orders and changes to open ones. Kraken Order Entry Maintenance is planned work on that system. While it runs, some requests can fail even though the market keeps moving.
That gap creates confusion. A trader may see a rejection and a moving price at the same time, then blame one for the other. Background on the platform is available in a detailed Kraken exchange review.
Kraken's status page shows two order entry windows of up to 60 minutes each, plus separate API maintenance on both days.
Date | Order entry maintenance | API maintenance |
10 November | 10:00–10:46 UTC | 07:00–14:00 UTC, completed 13:34 UTC |
11 November | 09:00–10:00 UTC | 07:00–14:00 UTC, completed 14:46 UTC |
Kraken said a small number of order submissions or modifications could be rejected. WebSocket and FIX API clients could also see higher latency.
Kraken Pro web, mobile, and desktop clients were expected to see a very small number of rejections. FIX clients could see several seconds of rejections.
Maintenance is not the only cause of a failed order. Low balances and minimum sizes also trigger errors, such as EOrder: Insufficient funds and EOrder: Order minimum not met.
Those are general errors, not confirmed causes of these rejections. Kraken lists them in its API error messages.
Kraken uses trading modes to control what the engine accepts:
Maintenance: New orders and cancellations are blocked, and no trades match.
Cancel Only: Open orders can be cancelled, but new orders cannot be placed.
Post Only: Only post-only limit orders are accepted, and no trades match.
Limit Only: Limit orders are accepted, market orders are rejected, and no trades match.
Order entry system maintenance should not be read as maintenance mode. Kraken's notices described possible rejections and latency, not a confirmed switch of all markets to maintenance mode.
Kraken may publish the current mode on its status page, the trading pages on Kraken.com, and the Kraken Pro mobile app. API users can also check REST SystemStatus and WebSocket status messages.
"Stale price" is a descriptive term in this article. It is not a Kraken error code, and Kraken did not tie stale prices to the order entry work.
The API notice is the relevant one. Kraken warned that connections could briefly disconnect and that some WebSocket connections could stay open but stop delivering messages.
Sequence numbers could restart without a new snapshot. Affected users were told to disconnect, reconnect, and resubscribe to all channels.
A quote is only as current as the order book behind it, and an order book model explainer shows how bids and asks stack up. For example, a frozen screen shows an ask of 100 while the live ask has moved to 103.
A market buy may execute against asks near the newer price, depending on liquidity. A limit buy at 100 would not execute against an ask at 103.
Issue | Meaning | First check |
Rejected order | The crypto exchange refused the request. | API response or order history |
Stale price | The displayed quote may be out of date. | Latest order book update |
Market Price Protection | Market order blocked or partly cancelled | Cancellation details |
Kraken says Market Price Protection can cancel market orders when spreads become unusually wide, typically 2.5% to 20% of the market price depending on the pair.
Market buys also carry a 5% spending limit. If the full order cannot be filled within it, the order can be partly filled and the rest cancelled. Wide spreads also raise market order slippage. None of this depends on Kraken Order Entry Maintenance.
A limit order fills only at the set price or better. It caps the worst price but does not promise a fill. An unfilled limit order is still open.
A rejected order was refused, and only the response or order history shows which one happened.
A post-only limit order is designed to add liquidity, not take it. On Kraken Pro, it is posted to the book or cancelled if it would execute against an existing order.
Kraken's derivatives documentation describes rejection and cancellation. Either way, this is an order-type rule, not necessarily a maintenance error.
Kraken's release notes dated 1 September 2026 added an upcoming_maintenance object to the WebSocket v2 status channel.
It appears when a trading-relevant event is within 72 hours. The same notes cover WebSocket v1 systemStatus, REST SystemStatus, and optional FIX News advisories.
Maker Protection is a different feature. It delays some orders on selected derivatives markets, not spot. The launch delay was 20 ms, with a 100 ms maximum.
The delay can change by market, so API users should read the makerProtectionMillis field instead of assuming a fixed value.
After a failed order, the first instinct is to hit the button again. That is the riskiest move. If the first order went through quietly, the second one doubles the position.
A calmer routine works better:
Find the original order. Search order history for its order ID or client order ID. Both identify the exact request.
Read its status. An order can be open, filled, cancelled, or rejected. Only one of those means a retry is needed.
Look at the balance. Funds held against an order often mean it was accepted, even before it filled.
Check the trading mode. Kraken's status page and mode notices show whether the engine is limiting orders at that moment.
Refresh the market view. Reload the order book. API users should reconnect the WebSocket if updates stop so the new price is a live one.
Kraken described the expected impact of Kraken Order Entry Maintenance as small, but some submissions and modifications could still fail.
Stale market data is a separate risk, tied to the API notice. Status, order history, and the API response should come first, and the retry last.
Disclaimer: This article is for information only and is not financial advice. Crypto trading carries high risk, and exchange conditions can change quickly. Traders should verify details on official Kraken pages before acting.