- Kraken resolved a one-hour trading outage on October 30 that affected its spot and derivatives markets.
- The disruption impacted its website, mobile apps, REST, WebSocket and FIX API connections.
- Kraken has not disclosed the cause of the outage or the number of affected customers.
Prominent cryptocurrency exchange Kraken successfully fixed a trading disruption on October 30 that impacted its spot and derivatives markets after users encountered difficulties connecting to the platform and placing orders across various trading interfaces.
Based on the official status page of the exchange, the technical incident started at 02:42 UTC (8:12 AM IST) and concluded at 03:42 UTC (9:12 AM IST), spanning roughly one hour in total duration.
The service interruption impacted individuals utilizing the website and mobile applications of Kraken, as well as participants connecting via REST, WebSocket, and FIX APIs. These connectivity tools are utilized to retrieve market data, link external trading systems, and submit orders directly to the exchange.

At the outset, Kraken stated it was actively examining connectivity and order routing issues impacting spot and derivatives clients alike. A subsequent update was issued by the exchange at 02:55 UTC indicating that the investigation remained underway, before the event was officially designated as resolved shortly thereafter.
Kraken Provides No Details on What Caused the Trading Disruption
The service failure extended beyond individuals accessing the platform via the Kraken website or mobile app. Automated trading systems and API users likewise encountered challenges gaining platform access and executing trades.
REST and WebSocket APIs see frequent deployment by trading bots and alternative automated systems to interface with digital asset exchanges. Meanwhile, institutional clients rely on FIX connections to interact with trading venues and administer their order management.
Nonetheless, Kraken has omitted any mention regarding the underlying trigger of the incident or whether it stemmed from a systemic malfunction within its exchange infrastructure. Furthermore, the platform withheld figures concerning the total user count impacted, the volume of rejected orders, or potential financial damages stemming from the event.
The status tracking records of Kraken verified that operations normalized at 03:42 UTC on October 30. Additional insights regarding the situation or an in-depth technical analysis have not been published by the exchange.
This incident unfolds while digital currency platforms endure ongoing scrutiny to deliver dependable trading operations, particularly during active market phases where execution lags can directly impact traders.
Frequently Asked Questions
When did the Kraken outage occur?
The trading disruption began on October 30 at 02:42 UTC (8:12 AM IST) and was fully resolved by 03:42 UTC (9:12 AM IST), lasting approximately one hour.
Which Kraken services were impacted by the disruption?
The incident affected both spot and derivatives markets, impacting website users, mobile applications, and clients connecting via REST, WebSocket, and FIX APIs.
Has Kraken explained the cause of the outage?
No, Kraken has not disclosed the root cause of the technical disruption, nor has it released information regarding the number of affected users, rejected orders, or potential financial losses.
