Kraken resumed trading after a two-hour upgrade stretched beyond two days

Kraken resumed trading on January 13, 2018, after production problems transformed a scheduled two-hour infrastructure upgrade into an interruption lasting more than two days. The restart restored access to a major cryptocurrency venue, but it was deliberately constrained: existing orders had been canceled, trading pairs reopened with empty order books, withdrawals remained disabled and new margin positions could not be created.

The episode mattered beyond one exchange’s engineering difficulties. Cryptocurrency markets operated continuously across competing venues, while Kraken customers had been unable to trade or withdraw through a period of active price movement. The restart therefore tested whether a centralized platform could return without disorderly executions, liquidations or stale orders.

A two-hour window became nearly 59 hours

Kraken’s status record scheduled maintenance for January 11, 2018, at 05:00 UTC. The company estimated that services would be unavailable for about two hours, while warning that the work could take longer. Updates over January 11 and January 12 described a late start, slower-than-expected installation, problems discovered during final testing and a production-only bug that Kraken said was difficult to reproduce.

The status page marked systems back online at 11:30 UTC on January 13. It then reported an order-book display problem and paused trading at 11:54 UTC. Kraken recorded trading as resumed at 15:47 UTC.

Measured from the scheduled 05:00 UTC start on January 11 to the 15:47 UTC trading resumption on January 13, the interruption lasted 58 hours and 47 minutes. That is a calculation from Kraken’s timestamps, not a duration independently supplied by the exchange. Website availability began earlier, at 11:30 UTC, after 54 hours and 30 minutes.

A controlled restart, not full restoration

Kraken said all preexisting orders were canceled and funds committed to those orders were returned to available balances. Trading pairs consequently began with no orders on their books. The company cautioned customers about market orders in that illiquid setting and asked them to verify limit prices carefully.

Margin positions remained open, but liquidations were paused for at least 48 hours and the creation of new margin positions was disabled for the same minimum period. Withdrawals were also suspended for at least 12 hours while the replacement trading engine was monitored. Deposits could require as many as two additional business days to be credited.

As compensation, Kraken announced zero fees for unleveraged trades through January 31, 2018, UTC. Margin opening and rollover fees were reduced to 0.005% over the same period. Those measures were company policy announcements, not evidence that every customer loss or access problem had been resolved.

Kraken attributed the delay to a condition detected by regression tests after its replacement engine entered the production environment. The exchange said its development tests had passed. It also said client funds remained safe throughout the interruption. The surviving records verify that Kraken made that assurance; they do not provide an independent audit of balances or custody during the outage.

Why the outage mattered

The incident exposed a fundamental difference between crypto assets and the platforms through which many customers accessed them. A blockchain could continue processing transactions while an exchange customer remained unable to submit orders, close a position or request a withdrawal. Operational availability, order-book integrity and custody were therefore separate risks even when discussed under the single label of an “exchange.”

The empty-book restart also illustrated why restoring a trading venue is not equivalent to restoring ordinary liquidity. Canceling stale orders reduced the risk of executions at prices submitted before the outage, but it also removed resting liquidity. Kraken’s temporary liquidation pause and warning against careless market orders acknowledged that trade-off.

Later context

Kraken’s status record subsequently reported that withdrawals were enabled at 23:59 UTC on January 14, 2018. That later update clarifies the restoration sequence but was not knowable when trading resumed on January 13. No price movement is attributed to the outage here because the cited records do not establish causation across fragmented cryptocurrency venues.