Altcoins
Kraken completes maintenance on its WebSocket, FIX and REST APIs
Kraken declared its API maintenance complete at 13:34 UTC on November 10. During the announced window, some WebSocket feeds could stop sending data while the connection remained open.

One maintenance window for all three interfaces
Kraken marked its API maintenance as complete on its status page at 13:34 UTC on November 10. The exchange had marked it in progress at 07:00 UTC and initially scheduled work until 14:00 UTC. The maintenance covered its WebSocket, FIX and REST interfaces. The notice warned of possible brief disconnections, but the completion update gives neither a quantified account of disruptions nor the number of clients actually affected.
The three interfaces serve different purposes. REST handles individual requests, while WebSocket lets the client receive updates over a persistent connection. FIX also serves integrations that exchange messages with the platform. The notice concerns these software access points. On its own, it does not establish the state of every Kraken service or the effects on all its users. These differences explain why a client may have to check the responses to its requests separately from the continuity of the messages it receives.
An open connection can stop delivering data
In its notice, Kraken describes two possible WebSocket symptoms. Messages may stop even though the connection still appears active. Sequence numbering may also restart without a new snapshot. An application that monitors only dropped connections could therefore keep displaying the last information it received even when its feed is no longer updating it. On a screen displaying an order book, that distinction separates the state of the connection from the state of the data shown.
Kraken asks users who encounter these symptoms to disconnect, reconnect and then resubscribe to all their channels. Its documentation for the WebSocket v2 order book channel provides for a snapshot on subscription by default. The snapshot gives the client the state of the book from which to apply updates. It lets the client rebuild its local view when the previous sequence no longer provides a continuous baseline.
Checking the order book after reconnecting
On the WebSocket v2 order book channel, Kraken includes a CRC32 checksum with each update. Its documentation explains how to compare the top ten price levels on each side of the book with the data held by the client. The check is optional and covers those levels even if the subscription supplies more. It gives integrators a way to detect a mismatch in that part of the book after they resume receiving messages.
Kraken’s update confirms that the work ended. For an application that consumes these feeds, the platform’s status and the quality of the data received remain two separate pieces of information. Receiving a new snapshot followed by consistent updates allows the application to check whether its own connection has recovered a usable feed. This check is performed separately for each order book being tracked.
