The exchange confirmed the resolution of the incident at 03:42 UTC, though it provided no technical explanation for the failure. During the hour of downtime, traders reported receiving persistent error messages and an inability to manage positions, while some users noted the platform appeared to be operating in a restricted post-only mode. Kraken Support acknowledged the issues in real-time on social media, directing affected customers to an official incident page while engineering teams investigated the connectivity bottlenecks affecting REST, WebSocket, and FIX protocols.
The timing of the outage sparked speculation regarding the exchange’s stability, specifically regarding unverified claims of $130 million in exposure to the Aave lending protocol. While market participants drew connections between the platform’s technical difficulties and wider volatility in the crypto sector, no evidence links the connectivity failure to liquidity pressures or the recent maintenance performed on October 29. Kraken has not disclosed the volume of rejected transactions or confirmed whether any customer assets require further verification following the system recovery.

Comments (0)
No comments yet. Be the first!