Kraken’s scheduled WebSocket, FIX, and REST API maintenance is in progress. It is a seven-hour plumbing window, not a halt of the venue.
The Kraken status incident flipped to “in progress” at . The window is 07:00 UTC to 14:00 UTC on 10 November 2026. Kraken’s own notice says clients may see brief disconnections. It also says some WebSocket sessions can stay open and go quiet: no new messages, or sequence numbers restarting without a new snapshot. The fix Kraken names is disconnect, reconnect, and resubscribe. That is bot hygiene, not a cash-market close.
Our CoinGecko snapshot at showed bitcoin at $74,616 (24-hour change +0.80%), ether at $2,115 (+0.45%), and solana at $85.94 (+0.07%). Global crypto market cap sat near $2.507 trillion, with bitcoin dominance about 59.60%. Coinbase BTC-USD last print at was $74,661.80. Kraken’s public XBTUSD ticker, fetched at , still returned HTTP 200 with a last trade of $74,614.60. The tape is live. The API window is live too. Those are not the same fact.
What happened
Kraken posted the November 10 window on 9 November at 18:57 UTC. A 60-minute warning went up at 06:01 UTC. At 07:00:08 UTC the same incident moved to in progress with a one-line update: scheduled maintenance is underway, more if needed. The named components are FIX, REST, and WebSocket. Statuspage still listed those three as operational at the start of the window. Impact class is maintenance, not a major outage banner.
What Kraken actually warned about is narrow. Brief disconnects. Stale sockets that look connected. Sequence numbers that jump without a snapshot. If a trading stack treats a silent socket as a healthy book, that stack will lie to itself. Kraken told operators to tear the socket down and subscribe again. That sentence is the story for anyone routing orders through those APIs.
A second, shorter slot is still only scheduled. The order-entry maintenance is booked for approximately 10:00 UTC to 11:00 UTC on the same day. That notice, posted 6 November at 14:48 UTC, is more specific about rejects. Kraken Pro web, mobile, and desktop “may experience a very small number of rejected order submissions or order modifications.” WebSocket API clients may see a small number of rejects plus extra latency. FIX clients may see several seconds where submissions and modifications are rejected, again with extra latency. Kraken says no action is required. That is true for humans clicking a button. It is not true for a retry loop that assumes every reject is a risk-limit event.
Public REST was not a black hole at the open of the 07:00 window. A GET of Kraken’s public Time endpoint at 07:07:15 UTC returned unixtime 1794294435. The public Ticker for XBTUSD showed ask $74,614.20, bid $74,614.10, last $74,614.60, 24-hour high $75,473.90, and 24-hour low $73,601.80. Those prints sit next to Coinbase, not in a void. Anyone who tweets “Kraken is down” because a private bot disconnected is mixing a socket event with a venue halt. We did not see a halt on the public ticker.
Context
Bitcoin is still inside the Coinbase range we already named after the weekend shelf broke. Coinbase 24-hour stats at the 07:06 UTC fetch showed open $73,770.92, high $75,476.98, low $73,636, last $74,661.80, and spot volume of about 8,796 bitcoin. The level-2 book at had a one-cent spread: best bid $74,618.55, best ask $74,618.56. Top-of-book depth in the first ten levels was about $96,200 on the bid and $42,500 on the ask. That is uneven, not empty. The high of the session is still under the old $75.5k shelf. The low is still the $73,636 area, not a new breakdown from this API window.
Coinbase’s status page is on a different tape. The indicator there is still “minor” / partially degraded service, leftover from delayed DASH sends and other funding nits, plus a scheduled system window on 14 November. Coinbase is not running a matching seven-hour WebSocket/FIX/REST maintenance this morning. Venue risk is local until it isn’t. Today the local print is Kraken’s API calendar, not a joint outage.
This window also sits on a recent pattern. Kraken completed a similar WS, FIX, and REST maintenance on 9 November after an 08:00–14:00 UTC slot, and it ran another 07:00–14:00 UTC slot on 6 November. Repeating a scheduled API window is how a venue patches pipes. It is not, by itself, evidence that spot matching stopped. Traders who only watch candle closes will miss it. Traders who keep a socket open for seven hours without a reconnect path will not.
Read this against what an exchange actually is: matching, custody rails, and the interfaces that talk to both. A REST ticker can keep printing while a FIX session drops. A WebSocket can look “connected” and still starve a strategy of trades. That is why market depth on one venue is not a substitute for a heartbeat on the venue you actually use. If the book you trade is Kraken Pro via API, the heartbeat is this incident page plus your own reconnect logs. If the book you trade is Coinbase, this morning’s Kraken window is context, not your fill risk.
The bitcoin tape still belongs in the same file as Bitcoin’s recorded cycles and the live snapshot habit in how to read a crypto market snapshot. Price at $74.6k is not a new regime. It is the same post-shelf zone we mapped when Bitcoin’s $75.5k weekend shelf broke on Coinbase. An API maintenance window does not rewrite that range. It can, for some accounts, rewrite whether an order you thought you sent is actually working.
For more of the same-day bitcoin tape, the Bitcoin news category is the running log. Use it. Do not treat a status-page emoji as a candle.
Our read
I am treating 10 November’s 07:00–14:00 UTC Kraken window as scheduled API risk for bots, not as a Kraken halt and not as a bitcoin range break. Narrative is cheap here. Exit liquidity is not. The public ticker still prints. Coinbase still has a one-cent spread around $74,619. Kraken told API clients the failure mode in advance: brief disconnects and zombie sockets. Believe that notice until the incident page says something harsher.
Falsifiable claim: by 14:00 UTC on 2026-11-10, Kraken marks incident 59l3k633dq26 completed (or a later update on that same incident says the window ended), and a public GET of Kraken’s XBTUSD ticker still returns HTTP 200 with a non-empty result object. If before 14:00 UTC Kraken posts that REST, FIX, and WebSocket are fully unavailable, or if that public ticker returns HTTP 5xx or an empty/error result for 15 consecutive minutes, this read is wrong. An unplanned halt of Kraken Pro web and mobile order entry before the 10:00 UTC scheduled slot would also kill the read.
What to watch next
First, the 14:00 UTC end of incident 59l3k633dq26. Completed on time, with REST still printing, keeps this in the “plumbing” bucket. A silent extension past 14:00 UTC, or a jump from maintenance to a major incident, is the upgrade that would change the desk’s stance.
Second, the 10:00–11:00 UTC order-entry window. Watch for a status flip to in progress, then for rejects on Kraken Pro and FIX as described. A handful of rejects is inside the notice. A multi-minute freeze of web and mobile order entry is not.
Third, your own logs if you trade Kraken over sockets. A reconnect-and-resubscribe that restores sequences is the advertised path. A book that stops updating while the socket stays “open” is the failure mode Kraken already named. Do not wait for Twitter to translate that for you.
Fourth, bitcoin’s Coinbase range. A last print back above $75,476.98, or a last print through $73,636, would be a tape event. This API window, by itself, is not that event.